@@ -216,6 +216,7 @@ By default, each individual instance of LiteBans can create 10 concurrent databa
Socket timeouts are generated when the database server stops responding to requests for a given period of time. There are many possible causes for this type of error:
- Your database server may not have NTP (network time synchronization) set up correctly. If it is hosted in a virtual environment without NTP, the host could take a long time to update the system time of all guests, which would result in system time jumping backwards or forwards by 20-60 seconds on a regular basis, which can cause connection timeouts and various, otherwise undetected negative side effects.
- Your database server, or the machine running it, may have been temporarily shut down for maintenance purposes, or is in the process of rebooting.
- Your database server may be resource-starved (CPU or disk I/O bound), either due to a background process (such as a backup task) or due to an intensive database query from any source.
- There could be a hardware failure at any point between the client and the server causing a disrupted network connection (packet loss) or other type of fault. For example, a router may be rebooting once or twice per day under specific loads due to age-related electrical faults. To rule out network failure, one must run a long-term ping test from the client to the server or vice versa - the amount of packets lost should ideally be zero.
