Author Topic: Disconnects (Read 13028 times)

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 ?

Naturalistic · « **Reply #1 on:** January 15, 2007, 07:02:42 am »

You're running 2 bots, and they are fighting each other.

Try closing all bots and run 1 again.

Xenixa · « **Reply #2 on:** January 15, 2007, 11:42:17 am »

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.

Aesgaard · « **Reply #3 on:** January 15, 2007, 02:31:19 pm »

Quote from: Naturalistic on January 15, 2007, 07:02:42 am

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

BEBOT

Aesgaard · « **Reply #4 on:** January 15, 2007, 02:31:54 pm »

Quote from: Xenixa on January 15, 2007, 11:42:17 am

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 ?

Khalem · « **Reply #5 on:** January 15, 2007, 04:08:25 pm »

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.

Aesgaard · « **Reply #6 on:** January 16, 2007, 06:35:25 am »

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 ?

Naturalistic · « **Reply #7 on:** January 16, 2007, 06:47:31 am »

That could be it.

I'd say change the pass on that account if you don't want anyone to use it.

Xenixa · « **Reply #8 on:** January 16, 2007, 06:52:54 am »

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.

Aesgaard · « **Reply #9 on:** January 16, 2007, 04:26:57 pm »

Quote from: Xenixa on January 16, 2007, 06:52:54 am

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*