connection drops in a few hours

[ynaga]

Although my Iam stayed alive for days before the server update, it quits only in a few hours with these messages below after the server update.
Any suggestion will be appreciated.

ynaga

last few lines of avatar.log

Code: Select all

1063268 [Thread-2] INFO  com.avatar_reality.blue_mars.iam.framework.IamBot  - Kou is at (3032.0,1910.5,31.0)
1123288 [Thread-3] INFO  com.avatar_reality.blue_mars.iam.util.PerformanceMonitor  - Call stats for MessageRetriever: 135.779 ms. average for 1000 calls over a period of 205 sec.
1123316 [Thread-2] INFO  com.avatar_reality.blue_mars.iam.framework.IamBot  - Kou is at (3032.0,1910.5,31.0)
1126376 [Thread-2] INFO  com.avatar_reality.blue_mars.iam.util.PerformanceMonitor  - Call stats for BotUpdater: 38.699 ms. average for 1000 calls over a period of 205 sec.
1183501 [Thread-2] INFO  com.avatar_reality.blue_mars.iam.framework.IamBot  - Kou is at (3032.0,1910.5,31.0)
1243662 [Thread-2] INFO  com.avatar_reality.blue_mars.iam.framework.IamBot  - Kou is at (3032.0,1910.5,31.0)
1303879 [Thread-2] INFO  com.avatar_reality.blue_mars.iam.framework.IamBot  - Kou is at (3032.0,1910.5,31.0)
1328811 [Thread-3] INFO  com.avatar_reality.blue_mars.iam.util.PerformanceMonitor  - Call stats for MessageRetriever: 135.196 ms. average for 1000 calls over a period of 205 sec.
1331876 [Thread-2] INFO  com.avatar_reality.blue_mars.iam.util.PerformanceMonitor  - Call stats for BotUpdater: 38.085 ms. average for 1000 calls over a period of 205 sec.
1363885 [Thread-2] INFO  com.avatar_reality.blue_mars.iam.framework.IamBot  - Kou is at (3032.0,1910.5,31.0)
1381740 [Thread-2] ERROR com.avatar_reality.blue_mars.tkclient.TKClientAdapter  - Connection dropped for avt55997
1381880 [Thread-4] INFO  com.avatar_reality.blue_mars.iam.IamMain  - No more bots connected, going to quit.

[admin]

Does this happen all the time? Or only occasionally?

It can happen that the bot-server gets disconnected from the Blue Mars server. It tries to re-establish the connection but it doesn't always work. In that case you have to restart the bot. I've been thinking about a way to automate this, but haven't gotten around that yet.

[ynaga]

I started Iam several times after the server maintenance and that happened every time.
Ok I'll also try to make the start script to restart my Iam.