@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.
After upgrade from 5.3.4 to 5.4.0, Database Backend error
-
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
===============
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.
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.
Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro
Resent PM with profile.
Thanks
Thanks
Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro
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
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.
If you run into any sticking points in either kb, please let us know.
FOR TECHS: Both profiles now received and shared internally.
Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro
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.
Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro
# ls -l /etc/init.d/ndo2db
-rwxr-xr-x 1 root root 4476 Jan 2 08:18 /etc/init.d/ndo2db
#
-rwxr-xr-x 1 root root 4476 Jan 2 08:18 /etc/init.d/ndo2db
#
Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro
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'
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'
Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro
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]$
# 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]$
Re: After upgrade from 5.3.4 to 5.4.0, Database Backend erro
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/
https://www.mcapra.com/