session history
EvilOlaf opened this issue ยท 5 comments
[19:25:47] [Server thread/INFO]: Olaf lost connection: Timed out
[19:25:47] [Server thread/WARN]: [BanManager] Could not find Olaf session history, perhaps they disconnected too quickly?
Actully the player was online for about 30 seconds. Not sure if this is still all right.
Bm 5.10.1
It's done in memory, and saved when they leave the server. Definitely odd. Let me know if it happens again.
I crawled the log file from this day and found the sequence 9 (+1 next day) times. About once a hour.
2016-08-02-2.log.gz:[11:11:56] [Server thread/WARN]: [BanManager] Could not find Olaf session history, perhaps they disconnected too quickly?
2016-08-02-2.log.gz:[12:42:22] [Server thread/WARN]: [BanManager] Could not find Olaf session history, perhaps they disconnected too quickly?
2016-08-02-2.log.gz:[14:34:31] [Server thread/WARN]: [BanManager] Could not find Olaf session history, perhaps they disconnected too quickly?
2016-08-02-2.log.gz:[15:06:47] [Server thread/WARN]: [BanManager] Could not find Olaf session history, perhaps they disconnected too quickly?
2016-08-02-2.log.gz:[15:45:39] [Server thread/WARN]: [BanManager] Could not find Olaf session history, perhaps they disconnected too quickly?
2016-08-02-2.log.gz:[16:49:26] [Server thread/WARN]: [BanManager] Could not find Olaf session history, perhaps they disconnected too quickly?
2016-08-02-2.log.gz:[17:15:37] [Server thread/WARN]: [BanManager] Could not find Olaf session history, perhaps they disconnected too quickly?
2016-08-02-2.log.gz:[19:25:47] [Server thread/WARN]: [BanManager] Could not find Olaf session history, perhaps they disconnected too quickly?
2016-08-02-2.log.gz:[21:41:14] [Server thread/WARN]: [BanManager] Could not find Olaf session history, perhaps they disconnected too quickly?
2016-08-03-1.log.gz:[02:22:23] [Server thread/WARN]: [BanManager] Could not find Olaf session history, perhaps they disconnected too quickly?
For privacy reasons I replaced all player names. They were almost all different.
What I also noticed by scanning older log files was that it seems that this issue has been introducted in a version later than 5.9.x