Ask the Community
Groups
Alerts: Could Not Connect to Database - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h2 data-id="symptom">Symptom</h2> <ul><li>Could not connect to database</li> <li>Email alerts are sent indicating cannot connect to database</li> </ul><h2 data-id="possible-causes">Possible Causes</h2> <ul><li>These can be normal if the system was undergoing maintenance, updates, or other actions that would prevent subsystems from accessing the database normally and can generally be ignored.</li> <li>Under heavy load, the backup system may generate these messages even though there are no problems with the connection to the database.</li> </ul><h2 data-id="resolution">Resolution</h2> <p>To reduce the frequency of seeing this error, in the Legacy UI, adjust the setting under the Alertman section of the Settings file (Settings > System, Updates, and Licensing > General Configuration) to increase the number of minutes a connection cannot be made before generating an email. This setting is:</p> <p><code class="code codeInline" spellcheck="false" tabindex="0">[Alertman]<br>DatabaseEmailTimeoutMins=60<br>// Minutes the system database must be down before an email is sent</code></p> <p>If this issue persists contact support to review the system I/O performance and/or database health.</p> </article> </main>