My server has been on 24/7 for the past few years now. All of a sudden in the past couple of days, it began periodically stopping approximately every 2 hours (according to logs). There is nothing out of the ordinary in the logs, it just shows the usual startup messages.
Prior to checking the logs just now, I had not even connected to host machine since updating to the latest server release many months ago. I did nothing to provoke a change in behavior.
As of this morning, the server is no longer stopping. It’s unfortunate that I still have no idea what caused the problem. It must have been a problem with the host machine, so I’ll take it up with the provider next time.
I find myself with the same problem as you. Every hour client disconnect and server write 3 log file.
First log :
############
2024-09-14 09:45:22.106844|INFO |VirtualServerBase|1 |listening on 0.0.0.0:9987, [::]:9987
2024-09-14 10:37:39.310725|INFO |PktHandler |1 |Cleaning up connection because of 13 resends of COMMAND packet
2024-09-14 10:37:39.310725|INFO |PktHandler |1 |Dropping client 4 because of resend timeout
2024-09-14 10:37:39.754154|INFO |PktHandler |1 |Cleaning up connection because of 13 resends of COMMAND packet
2024-09-14 10:37:39.754154|INFO |PktHandler |1 |Dropping client 2 because of resend timeout
2024-09-14 10:37:40.856344|INFO |PktHandler |1 |Cleaning up connection because of 13 resends of COMMAND packet
2024-09-14 10:37:40.856344|INFO |PktHandler |1 |Dropping client 3 because of resend timeout
2024-09-14 10:37:42.307721|INFO |PktHandler |1 |Cleaning up connection because of 13 resends of COMMAND packet
2024-09-14 10:37:42.307721|INFO |PktHandler |1 |Dropping client 1 because of resend timeout
2024-09-14 10:37:43.308031|INFO |PktHandler |1 |Cleaning up connection because of 13 resends of COMMAND packet
2024-09-14 10:37:43.308031|INFO |PktHandler |1 |Dropping client 5 because of resend timeout
############
Second log :
############
2024-09-14 10:41:12.370701|INFO |VirtualServerBase|1 |listening on 0.0.0.0:9987, [::]:9987
############
Then server restart and write the third log file.
Did you find what was the cause of the problem ?
I don’t know did happened, I just know that my fritz box did an update, then this problem appeared, but don’t know if it is related with fritz or if it is just coincidence.