DB error after Ubuntu/MySQL forced update

I'm getting the following error when trying to connect to my Observium page: DB not connected, please check database connection configuration. DB Error 2002: No such file or directory
I found this post about it, but the fixes suggested here don't seem to work for me. https://www.turnkeylinux.org/forum/support/thu-20181129-0834/db-error-2002-n...
Has anyone else hit this problem and managed to fix it?

is your database service running?
service mariadb status
if so can you login with the credentials in your observium config?
mysql -u {db_user} -p
and enter the password when prompted.
not sure if your issue is related to a broken security update from 2018 just because it gives the same error message, unless there is some other reason you suspect it is.
Thanks Brandon Lund KansasNet Internet Services 785-776-1452
________________________________ From: observium observium-bounces@observium.org on behalf of Jason Vanlandingham via observium observium@observium.org Sent: Thursday, February 17, 2022 11:20 AM To: Observium Network Observation System Cc: Jason Vanlandingham Subject: [Observium] DB error after Ubuntu/MySQL forced update
I'm getting the following error when trying to connect to my Observium page: DB not connected, please check database connection configuration. DB Error 2002: No such file or directory
I found this post about it, but the fixes suggested here don't seem to work for me. https://www.turnkeylinux.org/forum/support/thu-20181129-0834/db-error-2002-n... DB Error 2002: No such file or directory [Observium Turnkey] | TurnKey GNU/Linuxhttps://www.turnkeylinux.org/forum/support/thu-20181129-0834/db-error-2002-no-such-file-or-directory-observium-turnkey www.turnkeylinux.org I installed and configured Observium Turnkey yesterday. Added several devices, it was working great. I've used Observium for years, but had always done a bare/clean install of CentOS, then installed Observium. The system did an update last night at 9pm. Sent me an email. Looked like it was all great until I came into work this morning and now get this trying to access
Has anyone else hit this problem and managed to fix it?
participants (2)
-
Brandon Lund
-
Jason Vanlandingham