BeBot - An Anarchy Online and Age Of Conan chat automaton
Archive => Anarchy Online Archive => BeBot 0.3 support => Topic started by: Aesgaard on January 15, 2007, 05:56:06 am
-
Warning: socket_read(): unable to read from socket
- : En eksisterende tilkobling ble tvangslukket av den eksterne verten.
in C:\Bebot\AOChat.php on line 239
Read error: En eksisterende tilkobling ble tvangslukket av den eksterne verten.
Existing connection was forcefully? closed by external host?
What causes this ?
-
You're running 2 bots, and they are fighting each other.
Try closing all bots and run 1 again.
-
That error can also happen when a Bots connection times out and tries to reconnect before the AO chat servers register that character as logged out. Basically, the chat server is denying that character from logging in(via a forced disconnect) a 2nd time since it thinks it's already connected.
-
You're running 2 bots, and they are fighting each other.
Try closing all bots and run 1 again.
Nope, I am running 1 bot ;D BEBOT :D
-
That error can also happen when a Bots connection times out and tries to reconnect before the AO chat servers register that character as logged out. Basically, the chat server is denying that character from logging in(via a forced disconnect) a 2nd time since it thinks it's already connected.
Is there any way to prevent time out's ?
-
Only times ive ever seen that is when you have two simultanious connections on the same character, be it bot, ao client or chat client.
-
Hm, had the same disconnect at the approx same time again this evening, kinda weird since I am only running one bot :\ Could it be someone trying to log onto my botchar ?
-
That could be it.
I'd say change the pass on that account if you don't want anyone to use it.
-
Sounds like your provider may be resetting your connection around the same time everynight. That will time the bot out which also would give you that error. I know it gives me that error when my Cable router locks up.
As a test, inside bot.conf you could set $reconnect_time to something like 90 or greater seconds. I think 0.3 of Bebot is defaulted to 60 seconds. See if that helps any.
-
Sounds like your provider may be resetting your connection around the same time everynight. That will time the bot out which also would give you that error. I know it gives me that error when my Cable router locks up.
As a test, inside bot.conf you could set $reconnect_time to something like 90 or greater seconds. I think 0.3 of Bebot is defaulted to 60 seconds. See if that helps any.
o.0 timer
*wroom*