Posted by Justin Guerber on September 13, 2023 at 12:22:46:
In Reply to: Re: Comet lost connection and freeze posted by Robert G Laurin on September 13, 2023 at 11:14:08:
Hi Robert
The "Logout orphan" does indicate that the server is dropping those connections, but it may or may not be the cause of the comet freezes. It could just be the (correct) response to a client that is not longer communicating with the server.
Whatever the case, this does seem to point to a connection problem between the clients and the server.
If, as you said, this customer has been running fine for years on the same software/hardware, I would check for two things:
1. Check for any changes to the network/client/server infrastructure that could be causing the issue. Something like a network traffic monitor or firewall updates could in theory cause packets to get lost/dropped. A server update could also have affected how the comet server is running and whether it's performing properly.
2. Test any network cables/hubs/switches between the client and server to make sure that's not the failure point
Without the client-side logs it's hard to know what's happening.
Also, is the overnight process being run directly on the server? or is it run on one of the Windows 7/Windows 10 machines?
You could try rolling back to an older version of the security server/file server before the orphan logout was implemented. That could tell you if it's a time synch/server pinging problem or not. I believe you'd have to go back to version 15.2 or earlier. You can find them at the link attached.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.