Author Topic: recurring error for AOCHAT (Read 3726 times)

plugz · « **on:** July 23, 2010, 04:41:21 am »

[22-Jul-2010 20:30:20] PHP Warning:  socket_read(): unable to read from socket [0]: An existing connection was forcibly closed by the remote host.
 in xxx\AOChat.php on line 311

I see the above in recurring increments, making LARGE php error logs.

anyone seeing a bunch of this on their bots since latest patches as well?
getting serious lag out of bebot, but my budabot on the side is responding with 0 issues.

Khalem · « **Reply #1 on:** July 23, 2010, 10:12:59 pm »

This is normally caused by the character being logged in from another (or the same) location and causes the server to forcibly disconnect you.
Make sure your bot is running twice for example.

I'm not seeing any issue on any of the 7 AO bots I'm operating.

plugz · « **Reply #2 on:** July 26, 2010, 06:10:51 am »

bot isn't logged anywhere else Khalem
got like 7 or 8 bots running on my pc as well and this one is the only one causing issues at the moment

seeing a lot of timeouts hitting FC's character site as well

changing things back to use Curl instead of sockets now,as I'm seeing all kinds of issues via the php error logs

Khalem · « **Reply #3 on:** July 26, 2010, 11:25:05 pm »

curl vs sockets won't affect this in any way. It only involves how the bot connects to the webservers for XML items using either the high speed curl library (native C code) or sockets (interpreted php).
If the connection times out using curl, it will time out using sockets and vice versa.

The thing to keep in mind would be that the firewall/antidos systems at Funcom does not distinguish between connections to the AO chatservers and the webserver afaik. But if this was the reason for the bot being booted from the chatserver, it should affect all the bots you run provided they are using the same IP.

Other than that, I don't know what to tell you as there is no sane reason for this to affect only the one bot unless someone is flooding it somehow or causing it to flood/output oversized blobs which shouldn't be possible for any shipped modules at least.