Topic: SMF could not connect to the database (No noticeable issues)

[showngo]

About once a day or every other day I get a webmaster email that SMF could not connect to the database. There are zero http500 errors and no noticeable spinning wheels of death loading.
The correct info is in the server section. The correct info is in the Settings.php and there is no visible/noticeable downtime.  (Members are on 24/7)
The SMF Error log shows nothing around the times I get the notifications.

Is this just a glitch to not worry about?   SMF 2.0.17 AND now 2.0.18 (No errors updating to 18)

Installed mods

1.   Simple Audio Video Embedder   6.0.1    
2.   Resize Attached Images   2.4.1    
3.   AdditionalMembergroups   1.04
4.   Anti-spam by CleanTalk   2.31
5.   SimplePortal   2.3.7    
6.   SMF 2.0.18 Update   0.1.0    
7.   Recent Forum Topics Boardindex   1.2    
8.   WYSIWYG Quick Reply   2.3

[shadav]

I had the same issue only a lot more often....it was my crappy host
something wrong with their server....

if possible, switch hosts, if not ask the host to move you to another server and see if that helps.

[showngo]

I had the same issue only a lot more often....it was my crappy host
something wrong with their server....

if possible, switch hosts, if not ask the host to move you to another server and see if that helps.

I'll ask them.    Wasn't sure if it was anything with a scheduled task.   I know we do not receive "approval notifications" but it was checked.   I'm still trying to link the times to any events.

[Sir Osis of Liver]

I had the same issue only a lot more often....it was my crappy host
something wrong with their server....

if possible, switch hosts, if not ask the host to move you to another server and see if that helps.

 ^ This.  The connect errors are random, caused by server being overloaded or poorly configured.  You won't see them on a decent host.

[showngo]

With nothing being noticeable, I just turned off the notification for not connecting to the database in the Admin section.

[TheDragon]

I had the same issue after host upgraded to PHP 7.4
but not on occasion - was permanent
NOTHING would fix it
the only solution was to install a fresh version of SMS 2.0.18
and then import old SQL
(changing hosts is not easy - as i have MANY sites there)