Page 1 of 1
New NagiosXI server after a back up / restore
Posted: Wed Sep 09, 2015 1:04 pm
by JakeHatMacys
So my goal of migrating our old server onto a VM appears to have worked via back up & restore....
But I'm running into an issue where the monitoring Engine won't run, I just get the following:
Capture.JPG
Any ideas where to start with this? I actually took the liberty of upgrading from 2.5 to 2.7 to see if that would kick it into gear. No avail obviously (this new box isn't live yet but the old one was 2.5).
Tail end of nagios.log via /usr/local/nagios/var
Code: Select all
[1441821527] ndomod registered for aggregated status data'
[1441821527] ndomod registered for retention data'
[1441821527] ndomod registered for contact data'
[1441821527] ndomod registered for contact notification data'
[1441821527] ndomod registered for acknowledgement data'
[1441821527] ndomod registered for state change data'
[1441821527] ndomod registered for contact status data'
[1441821527] ndomod registered for adaptive contact data'
[1441821527] Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.
[1441821527] Error: Module loading failed. Aborting.
Re: New NagiosXI server after a back up / restore
Posted: Wed Sep 09, 2015 1:28 pm
by lmiltchev
Can you show us the output of the following commands?
Code: Select all
service nagios stop
service ndo2db stop
service ndo2db start
service nagios start
grep broker /usr/local/nagios/etc/nagios.cfg
/usr/local/nagios/bin/nagios | head -2
/usr/local/nagios/bin/ndo2db | head -2
grep ndo /var/log/messages | tail -20
Re: New NagiosXI server after a back up / restore
Posted: Wed Sep 09, 2015 2:08 pm
by JakeHatMacys
lmiltchev wrote:Can you show us the output of the following commands?
Code: Select all
service nagios stop
service ndo2db stop
service ndo2db start
service nagios start
grep broker /usr/local/nagios/etc/nagios.cfg
/usr/local/nagios/bin/nagios | head -2
/usr/local/nagios/bin/ndo2db | head -2
grep ndo /var/log/messages | tail -20
grep broker /usr/local/nagios/etc/nagios.cfg
Code: Select all
broker_module=/usr/local/nagios/bin/ndomod.o config_file=/usr/local/nagios/etc/ndomod.cfg
event_broker_options=-1
broker_module=/opt/OV/HPBsmIntNagios/lib64/libbsmintneb4.so
/usr/local/nagios/bin/nagios | head -2
/usr/local/nagios/bin/ndo2db | head -2
grep ndo /var/log/messages | tail -20
Code: Select all
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for notification data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for comment data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for downtime data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for flapping data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for program status data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for host status data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for service status data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for adaptive program data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for adaptive host data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for adaptive service data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for external command data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for aggregated status data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for retention data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for contact data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for contact notification data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for acknowledgement data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for state change data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for contact status data'
Sep 9 15:05:29 esu4v412 nagios: ndomod registered for adaptive contact data'
Sep 9 15:05:29 esu4v412 nagios: Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.
Re: New NagiosXI server after a back up / restore
Posted: Wed Sep 09, 2015 4:08 pm
by lmiltchev
I suspect this is the line that is causing the issue:
Code: Select all
broker_module=/opt/OV/HPBsmIntNagios/lib64/libbsmintneb4.so
even though I am not a 100% sure...
Can you comment out this line, restart nagios and ndo2db, and check to see if this is going to fix the issue?
Re: New NagiosXI server after a back up / restore
Posted: Thu Sep 10, 2015 8:15 am
by JakeHatMacys
lmiltchev wrote:I suspect this is the line that is causing the issue:
Code: Select all
broker_module=/opt/OV/HPBsmIntNagios/lib64/libbsmintneb4.so
even though I am not a 100% sure...
Can you comment out this line, restart nagios and ndo2db, and check to see if this is going to fix the issue?
Awesome, that worked, yeah that's from the BSM connector that isn't active on this box now anyway. But it will be eventually, i'll have it removed and re-installed and see if that resolves the issue.
Re: New NagiosXI server after a back up / restore
Posted: Thu Sep 10, 2015 9:06 am
by hsmith
JakeHatMacys wrote:lmiltchev wrote:I suspect this is the line that is causing the issue:
Code: Select all
broker_module=/opt/OV/HPBsmIntNagios/lib64/libbsmintneb4.so
even though I am not a 100% sure...
Can you comment out this line, restart nagios and ndo2db, and check to see if this is going to fix the issue?
Awesome, that worked, yeah that's from the BSM connector that isn't active on this box now anyway. But it will be eventually, i'll have it removed and re-installed and see if that resolves the issue.
Are we all right to close out this topic and mark it 'resolved'?
Re: New NagiosXI server after a back up / restore
Posted: Thu Sep 10, 2015 9:11 am
by JakeHatMacys
hsmith wrote:JakeHatMacys wrote:lmiltchev wrote:I suspect this is the line that is causing the issue:
Code: Select all
broker_module=/opt/OV/HPBsmIntNagios/lib64/libbsmintneb4.so
even though I am not a 100% sure...
Can you comment out this line, restart nagios and ndo2db, and check to see if this is going to fix the issue?
Awesome, that worked, yeah that's from the BSM connector that isn't active on this box now anyway. But it will be eventually, i'll have it removed and re-installed and see if that resolves the issue.
Are we all right to close out this topic and mark it 'resolved'?
Aye