Archive > BeBot 0.2 support

Error

(1/2) > >>

Aesgaard:
Doing an !items 34 nano controller unit causes the bot to crash completely (all bots, not just mine, had Mr. P test it for me since mine didnt reply first time cause a massive "retrieval error" and made the bot lock up completely (not responding to !online etc.) after, wtb a fix please

porter:
You can't say "all bots" but I did try that !items request on one of my 0.2.11 bots (running the standard items module that came with it) and it stopped responding completely for a minute and 11 seconds, then it sent a tell "Unable to query database". It also only responded to any other events that took place during that time and two further !items queries that could not query database after spending just about exactly two minutes timing out on each of those subsequent queries.

Log shows no other errors. Bot did not crash and restart, just was slow and continued just fine after these queries.

I don't think it mattered what the !items query was. Haven't yet looked at the code but the other queries sent to the bot while it was frozen with the first one were quite different. Maybe the Central Items DB was unresponsive or offline...

EDIT: looked at the simple module and here we see that if the bot does not get a result from trying to retrieve the URL (which is the items request) it returns the above mentioned error message:

--- Code: ---$result = file_get_contents($url);
if (!empty($result)) return $result;
else return "Unable to query database";

--- End code ---

Alreadythere:
Sounds like you have some trouble connecting to Vhab's server.

Khalem:
The cause of this is that 0.2.x still uses file_get_contents which basically will cause the bot to freeze until a response is received, or the request times out. In which case you could end up loosing connecting to the AO chatserver due to inactivity.

With 0.4 being slated for release this weekend or so i don't really plan on looking into backporting 0.3.x items.

Aesgaard:
Should I upgrade from 0.2.11 to 0.3 ? will that fix this ?

Navigation

[0] Message Index

[#] Next page