Fix "Unable to connect to database: Too many connections" errors
This rare "Too many connections" error can be produced if the MySQL/MariaDB server hosting your MIDAS database is currently overloaded. A database server may become overloaded when there are more connections (or queries) to the server than it can concurrently handle at any given point in time.
In these instances, it's likely that the database server that your MIDAS scheduling system uses is "shared". A "shared" database server is one which is also used for other non-MIDAS related databases/applications within your organization.
Consequently, if the total number of connections/requests to the database server (not just those originating from MIDAS) reaches the maximum allowed by the server, it will begin rejecting requests and a "Too many connections" error returned instead.
A "Too many connections" error - whilst extremely rare - is usually only temporary and once the number of concurrent connections to the database server drops, you should be able to access your MIDAS system again.
However, if you continue to frequently experience this error, your server administrator will need to do one of the following:
Increase the maximum number of concurrent connections your database server can handle. This may be achieved by increasing the values of your database server's global "max_connections" and "max_user_connections" variables.
Consider migrating some of your existing databases across to other database servers. If your database server is struggling to handle the load of multiple applications all trying to access databases at the same time, moving some of these to other servers may help.
