Author Topic: Persistent Whois cache with out-of-bot upgrading (Read 56192 times)

Malosar · « **Reply #120 on:** December 27, 2006, 02:47:51 pm »

First check whether you do actually have a whois table in your database. Second, check the console for errors on startup when it is trying to create the table.

ilon · « **Reply #121 on:** December 27, 2006, 03:00:44 pm »

ok, i assumed that the script would create the tables for me, since most ppl know how to handle mysql (including me), and everything else was done by the script.. :/

so the script dosnt create the tables in the database, you have to do it manualy?

Malosar · « **Reply #122 on:** December 27, 2006, 03:13:08 pm »

The whois-update script doesn't create the table. The WhoisCache.php module creates the table.

ilon · « **Reply #123 on:** December 27, 2006, 03:33:13 pm »

AHHH, tyvm then, i'll try to get it running then :]

nebhyper · « **Reply #124 on:** December 27, 2006, 05:10:58 pm »

stupid question I know, but how do I run a php script outside the bot?

What program? Or as I assume I use php.exe via cmd prompt but how?

Thanks in advance

Malosar · « **Reply #125 on:** December 27, 2006, 05:14:17 pm »

php blahblah.php

It's as simple as that. What you would want to do however is make a batch file to run the updater and add that updater to a scheduler to run at a specific time every day.

Alreadythere · « **Reply #126 on:** December 27, 2006, 05:16:31 pm »

You need to call php with the script as parameter.

Should be similar to the following (replace PathToPhp with the correct path):

Code: [Select]

PathToPhp\php whois-update.php
It needs some entries in the database to work with though

nebhyper · « **Reply #127 on:** December 27, 2006, 07:40:48 pm »

ok I did what you said.

A dos prompt window appears and goes away in about 1 second. Is this correct?

Edit: Whois table is already in the db as I have been using the modififed whois and cache since I first switched to BeBot 3 weeks ago.

Malosar · « **Reply #128 on:** December 27, 2006, 08:12:51 pm »

Go to a command prompt first, don't run it via start -> run. That way if you get errors you'll be able to see them without the window just closing immediately. And make sure your running the update script in the command console, not the module itself

Also the update lakes a long time. I have my delay set at 1000ms and it takes about 3 hours to complete (but I also have 85k lines in my whois db).

nebhyper · « **Reply #129 on:** December 27, 2006, 08:16:53 pm »

Yes it appears that once I set it up in a batch fle with PAUSE I caught my errors.

I had to update my php.ini file and then it worked.

However, FC is having issues as a response from them timed out!! I went to the forums and it took forever to load and sometimes timed out.

It is running right now, so I guess it will just take the 3hours as you said and who knows since it seems FC is crashing.

Thanks!!!!

ilon · « **Reply #130 on:** January 07, 2007, 02:05:46 am »

i get a somewhat strange error:
"Warning: fopen(http://www.anarchy-online.com/org/stats/d/rk1/name/2232322/basicstats.xml): failed to open stream: HTTP request failed! HTTP/1.0 500 Internal Server Error
in /home/bebot/whois-update.php on line 10

Warning: fgets(): supplied argument is not a valid stream resource in /home/bebot/whois-update.php on line 13"
when i try to run the script...

Code: [Select]

/* Line */
/* 08 */ unction get_site($url)
/* 09 */ {
/* 10 */         $fp = fopen($url, "r");
/* 11 */        $content = ""; //11
/* 12 */ 
/* 13 */        while ($buffer = fgets($fp, 1024))
/* 14 */                $content .= $buffer;
/* 15 */
/* 16 */        return $content;
/* 17 */ }

the line notice isnt actually in the script, just for this post

pusikas · « **Reply #131 on:** January 07, 2007, 04:15:47 am »

I get a few of those as well. Like 10-50 when updating over 50K entries. Was guessing that FC site was slow to respond or something like that.

Alreadythere · « **Reply #132 on:** January 07, 2007, 11:39:09 am »

Those are just warnings, no errors.

There are two possible reasons for this behavior:
1) the character or org doesn't exist.
2) FCs server is slow.

I'm just ignoring those warnings as the cache and updating still works.

Malosar · « **Reply #133 on:** January 10, 2007, 04:59:48 pm »

================================================
739 http queries for org information done!
47138 total http queries done!
42216 entries in database associated with an org modified!
87207 entries in database modified!
88570 entries in the whois cache!
232min 51sec runtime for org updates!
638min 24sec total runtime!
================================================

lol, I think "the internet" was having issues

jjones666 · « **Reply #134 on:** January 10, 2007, 05:09:30 pm »

I run mine before work, done by the time I get home

-jj-

Author Topic: Persistent Whois cache with out-of-bot upgrading (Read 56192 times)

Malosar

Re: Persistent Whois cache with out-of-bot upgrading

ilon

Re: Persistent Whois cache with out-of-bot upgrading

Malosar

Re: Persistent Whois cache with out-of-bot upgrading

ilon

Re: Persistent Whois cache with out-of-bot upgrading

nebhyper

Re: Persistent Whois cache with out-of-bot upgrading

Malosar

Re: Persistent Whois cache with out-of-bot upgrading

Alreadythere

Re: Persistent Whois cache with out-of-bot upgrading

nebhyper

Re: Persistent Whois cache with out-of-bot upgrading

Malosar

Re: Persistent Whois cache with out-of-bot upgrading

nebhyper

Re: Persistent Whois cache with out-of-bot upgrading

ilon

Re: Persistent Whois cache with out-of-bot upgrading

pusikas

Re: Persistent Whois cache with out-of-bot upgrading

Alreadythere

Re: Persistent Whois cache with out-of-bot upgrading

Malosar

Re: Persistent Whois cache with out-of-bot upgrading

jjones666

Re: Persistent Whois cache with out-of-bot upgrading