After upgrade from 5.3.4 to 5.4.0, Database Backend error

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro

Post by dwhitfield »

@jwelch, profile from you?

@karlson, I told you this via PM, but I might as well say here too so the techs don't go looking for it...the profile did not actually attach to your PM.
jwelch
Posts: 225
Joined: Wed Sep 05, 2012 12:49 pm

Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro

Post by jwelch »

===============
REPAIR COMPLETE
===============
Stopping ndo2db: done.
Starting ndo2db: done.
Running configuration check...
Stopping nagios:.. done.
Starting nagios: done.

=======================
nagios database repair succeeded
nagiosql database repair succeeded


No change in symptom.
kcarlson
Posts: 56
Joined: Thu Oct 20, 2016 9:17 am

Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro

Post by kcarlson »

Resent PM with profile.
Thanks
jwelch
Posts: 225
Joined: Wed Sep 05, 2012 12:49 pm

Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro

Post by jwelch »

profile.zip PM'd.
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro

Post by dwhitfield »

You should both run through https://support.nagios.com/kb/article.p ... ategory=44 and if that doesn't resolve the issue, https://support.nagios.com/kb/article.php?id=25 might lead you on the right path. The second one clearly isn't directly on point, but it is dealing with the database.

If you run into any sticking points in either kb, please let us know.

FOR TECHS: Both profiles now received and shared internally.
jomann
Development Lead
Posts: 611
Joined: Mon Apr 22, 2013 10:06 am
Location: Nagios Enterprises

Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro

Post by jomann »

The database backend showing as red is typically due to not having an ndo2db init.d script (/etc/init.d/ndo2db), but since you're on RHEL 6 it is unlikely that you don't have the script. However, you may need to make sure that permissions are correct on it so that the nagios user can check the ndo2db status.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
jwelch
Posts: 225
Joined: Wed Sep 05, 2012 12:49 pm

Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro

Post by jwelch »

# ls -l /etc/init.d/ndo2db
-rwxr-xr-x 1 root root 4476 Jan 2 08:18 /etc/init.d/ndo2db
#
jwelch
Posts: 225
Joined: Wed Sep 05, 2012 12:49 pm

Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro

Post by jwelch »

mysqld.log is full of the following, but looks like the entries go back to September: (there are no other ERROR entries)

160928 15:16:08 [ERROR] Invalid (old?) table or database name '.ssh'
160928 15:17:08 [ERROR] Invalid (old?) table or database name '.ssh'
160928 15:18:08 [ERROR] Invalid (old?) table or database name '.ssh'
160928 15:19:07 [ERROR] Invalid (old?) table or database name '.ssh'
160928 15:20:08 [ERROR] Invalid (old?) table or database name '.ssh'
160928 15:21:08 [ERROR] Invalid (old?) table or database name '.ssh'
160928 15:22:08 [ERROR] Invalid (old?) table or database name '.ssh'
...
170103 13:43:11 [ERROR] Invalid (old?) table or database name '.ssh'
170103 13:44:11 [ERROR] Invalid (old?) table or database name '.ssh'
170103 13:45:11 [ERROR] Invalid (old?) table or database name '.ssh'
170103 13:46:11 [ERROR] Invalid (old?) table or database name '.ssh'
170103 13:47:11 [ERROR] Invalid (old?) table or database name '.ssh'
170103 13:48:11 [ERROR] Invalid (old?) table or database name '.ssh'
jwelch
Posts: 225
Joined: Wed Sep 05, 2012 12:49 pm

Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro

Post by jwelch »

postgresql is running.

# service postgresql status
postmaster (pid 7585) is running...
#

Stopped and started postgresql...if I leave it down, XI complains about database problems, which clear up when I start postgresql.

[nagios]$ /etc/init.d/postgresql status
postmaster (pid 61347) is running...
[nagios]$
User avatar
mcapra
Posts: 3739
Joined: Thu May 05, 2016 3:54 pm

Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro

Post by mcapra »

Can you share the outputs of the following commands:

Code: Select all

ls -al /var/lib/mysql
find /var/lib/mysql -name .ssh
Former Nagios employee
https://www.mcapra.com/
Locked