Author Topic: roster update hanging bot up (Read 8168 times)

clashbot · « **on:** November 03, 2009, 04:40:08 am »

as some of you know I run 11 bots, only one is causing an issue though. Roster update seems to hang the bot up for an insane amount of time, with a few errors:

Quote

[02-Nov-2009 22:31:30] PHP Warning: socket_connect(): unable to connect
: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

in C:\Documents and Settings\Administrator\Desktop\james\0.5.1\0.5.1\main\14_Tools.php on line 171

any ideas what I can do to fix this, or is the xml from funcom for the roster nerfed again?

Temar · « **Reply #1 on:** November 03, 2009, 06:42:32 am »

the sockets function doesnt seem to have a timeout in it
on my bots i changed the setting under !set tools
to use cURL which does have a timeout

clashbot · « **Reply #2 on:** November 03, 2009, 12:04:51 pm »

it was set to sockets. and by an insane amount of time, I mean 15+ minutes for a roster update. Plus standard errors such as "Loading of xml failed"

clashbot · « **Reply #3 on:** November 09, 2009, 01:21:48 pm »

well I did a quick and dirty fix, by emptying the whois tables and the online tables. It was still hanging up at the roster update. It is now working, with no other errors, so it appeared to be a bad connection to funcom's xml list. But will say the bot runs much faster with a smaller whois table..
As you can imagine, 11 bots worth of whois queries can add up over a years time.

clashbot · « **Reply #4 on:** November 09, 2009, 01:24:08 pm »

forgot to mention, one of the other things I did was remove all the buddies from the bot toon and the slave. Was wondering if there was a simple module that could be written to purge this list and maybe set a date limit on the whois, so that if a query is xx days old it is removed? I think this would be a good optimization/maintenance tool.

Dochere · « **Reply #5 on:** November 13, 2009, 11:28:05 am »

I'we had these errors for a while as well.

When this happens my console fills up with:

Code: [Select]

PHP Warning:  socket_connect(): unable to connect
Total Count: 4322
Total: 1

Counter is looping for about 15 minutes, there are even times where bot will hang for so long that it just crashes and restarts.

Shelly · « **Reply #6 on:** November 15, 2009, 07:24:11 am »

Quote from: Temar on November 03, 2009, 06:42:32 am

the sockets function doesnt seem to have a timeout in it
on my bots i changed the setting under !set tools
to use cURL which does have a timeout

I did this for my bots and it has helped them not hang also.

Snarfblatt · « **Reply #7 on:** November 20, 2009, 08:22:02 pm »

Glad I just found this topic.. I posted a thread on AO Forums because of this issue. Is there something wrong with FC's xml file that keeps causing this too happen? or is an issue with using sockets?

For reference, here is my post: http://forums.anarchy-online.com/showthread.php?t=565011

Khalem · « **Reply #8 on:** November 21, 2009, 01:37:16 am »

There is something wrong with Funcom servers.

This combined with a default socket timeout of 60 seconds in PHP 4.3+ wrecks havock.

I'm going to backport behaviour from BeBot 0.7 that makes curl used automatically if present, and I'll also be adding a socket timeout that should fix the issue for non curl users as well. *shakes fist at funcom for having borked servers*

Khalem · « **Reply #9 on:** November 21, 2009, 12:36:50 pm »

Please test http://bazaar.launchpad.net/~bebot-devel/bebot/stable-0.6/annotate/head%3A/main/14_Tools.php
It should default to curl if it is available, and should also timeout normal socket operations.

clashbot · « **Reply #10 on:** November 21, 2009, 02:26:49 pm »

Khalem it is installed on my bots now and seems to fix the lock-down issue that whois was having on my bots. Now it's just a matter of FC fixing their problems...

clashbot · « **Reply #11 on:** November 22, 2009, 04:09:06 pm »

khalem getting a lot of errors with your modified tools...

Quote

warning socket_read(): unable to connect
: a connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. In \main\14_tools.php on line 167.

It then repeats with line 206, exact same message.

plugz · « **Reply #12 on:** November 22, 2009, 04:29:23 pm »

Hey guys, I'm consistantly seeing the following error here lately, be it v 6.5 or 6.6

Code: [Select]

Warning: socket_connect(): unable to connect [0]: A connection attempt failed be
cause the connected party did not properly respond after a period of time, or es
tablished connection failed because connected host has failed to respond.       
 in *\main\14_Tools.php on line 171

Insight/Fix for this available?

clashbot · « **Reply #13 on:** November 22, 2009, 06:43:18 pm »

http://bebot.link/index.php/topic,2079.msg14148.html#msg14148

plugz, I think it is related to that topic there, but also check your php version as well.. I resolved a lot of my issues as far as that error message by upgrading the bot's php to the latest version.

plugz · « **Reply #14 on:** November 23, 2009, 12:14:59 am »

I've got php 5.1 loaded with my bot. so covered there
Thanks for the link with the other thread, my raidbot is still on bebot, so I'll try those fixes there

Author Topic: roster update hanging bot up (Read 8168 times)

clashbot

roster update hanging bot up

Temar

Re: roster update hanging bot up

clashbot

Re: roster update hanging bot up

clashbot

Re: roster update hanging bot up

clashbot

Re: roster update hanging bot up

Dochere

Re: roster update hanging bot up

Shelly

Re: roster update hanging bot up

Snarfblatt

Re: roster update hanging bot up

Khalem

Re: roster update hanging bot up

Khalem

Re: roster update hanging bot up

clashbot

Re: roster update hanging bot up

clashbot

Re: roster update hanging bot up

plugz

Re: roster update hanging bot up

clashbot

Re: roster update hanging bot up

plugz

Re: roster update hanging bot up