After upgrade attempt - No Monitoring Engine

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Bionic___
Posts: 54
Joined: Wed Oct 23, 2013 7:49 am

After upgrade attempt - No Monitoring Engine

Post by Bionic___ »

After attempting an upgrade this morning, the monitoring engine will not run.
I cleared all config errors. There were some warnings but no errors.
Stopping and restarting did not help. I did not receive any errors on restart.
The log showed:

Code: Select all

/usr/local/nagiosxi/scripts> tail -f /usr/local/nagios/var/nagios.log
[1462194579] nerd: Channel opathchecks registered successfully
[1462194579] nerd: Fully initialized and ready to rock!
[1462194579] wproc: Successfully registered manager as @wproc with query handler
[1462194579] wproc: Registry request: name=Core Worker 22021;pid=22021
[1462194579] wproc: Registry request: name=Core Worker 22020;pid=22020
[1462194579] wproc: Registry request: name=Core Worker 22022;pid=22022
[1462194579] wproc: Registry request: name=Core Worker 22019;pid=22019
[1462194579] Error: Could not load module '/usr/local/nagios/bin/ndomod.o' -> /usr/local/nagios/bin/ndomod.o: undefined symbol: servicedependency_list
[1462194579] Error: Failed to load module '/usr/local/nagios/bin/ndomod.o'.
[1462194579] Error: Module loading failed. Aborting.
I have read through several threads and tried all debugging advice I could find but to no success.
I am currently stumped. Any help would be appreciated.
bwallace
Posts: 1145
Joined: Tue Nov 17, 2015 1:57 pm

Re: After upgrade attempt - No Monitoring Engine

Post by bwallace »

We'll need a bit more info...

What OS and version is this?
What Nagios version was running prior to upgrading + what Nagios XI version were you upgrading to?
Be sure to check out the Knowledgebase for helpful articles and solutions!
Bionic___
Posts: 54
Joined: Wed Oct 23, 2013 7:49 am

Re: After upgrade attempt - No Monitoring Engine

Post by Bionic___ »

I did a ndo rebuild as defined in thread: https://support.nagios.com/forum/viewto ... 16&t=27135 and it got the monitoring engine started but it appears the upgrade did not take. So Nagios XI is working again but it is still on 2012R2.7 so I am guessing i need to reapply the upgrade. Will it be ok to retry the upgrade?

OS = Red Hat Enterprise Linux Server release 6.7 (Santiago)
Nagios version before attempt = 2012R2.7
Nagios version after attempt = 2012R2.7
Attempting to upgrade to current version 5.2.7
bwallace
Posts: 1145
Joined: Tue Nov 17, 2015 1:57 pm

Re: After upgrade attempt - No Monitoring Engine

Post by bwallace »

I saw that thread before my 1st reply, but wanted to get some more info 1st, before suggesting it. Glad you were able to fix the ndo part.
You should be OK to go ahead and (re)upgrade now. https://assets.nagios.com/downloads/nag ... nstall.pdf
Be sure to check out the Knowledgebase for helpful articles and solutions!
Bionic___
Posts: 54
Joined: Wed Oct 23, 2013 7:49 am

Re: After upgrade attempt - No Monitoring Engine

Post by Bionic___ »

The upgrade failed dramatically. (Many tests failing)
The old version is still working fine.
bwallace
Posts: 1145
Joined: Tue Nov 17, 2015 1:57 pm

Re: After upgrade attempt - No Monitoring Engine

Post by bwallace »

yikes! Can you post the failure/error messages you see during the upgrade?
Be sure to check out the Knowledgebase for helpful articles and solutions!
Bionic___
Posts: 54
Joined: Wed Oct 23, 2013 7:49 am

Re: After upgrade attempt - No Monitoring Engine

Post by Bionic___ »

Code: Select all

...
Writing Makefile for Nagios::Monitoring::Plugin
cp lib/Nagios/Monitoring/Plugin/Performance.pm blib/lib/Nagios/Monitoring/Plugin/Performance.pm
cp lib/Nagios/Monitoring/Plugin/Range.pm blib/lib/Nagios/Monitoring/Plugin/Range.pm
cp lib/Nagios/Monitoring/Plugin/Threshold.pm blib/lib/Nagios/Monitoring/Plugin/Threshold.pm
cp lib/Nagios/Monitoring/Plugin.pm blib/lib/Nagios/Monitoring/Plugin.pm
cp lib/Nagios/Monitoring/Plugin/Functions.pm blib/lib/Nagios/Monitoring/Plugin/Functions.pm
cp lib/Nagios/Monitoring/Plugin/Getopt.pm blib/lib/Nagios/Monitoring/Plugin/Getopt.pm
cp lib/Nagios/Monitoring/Plugin/Config.pm blib/lib/Nagios/Monitoring/Plugin/Config.pm
cp lib/Nagios/Monitoring/Plugin/ExitResult.pm blib/lib/Nagios/Monitoring/Plugin/ExitResult.pm
Manifying blib/man3/Nagios::Monitoring::Plugin::Performance.3pm
Manifying blib/man3/Nagios::Monitoring::Plugin::Range.3pm
Manifying blib/man3/Nagios::Monitoring::Plugin::Threshold.3pm
Manifying blib/man3/Nagios::Monitoring::Plugin.3pm
Manifying blib/man3/Nagios::Monitoring::Plugin::Config.3pm
Manifying blib/man3/Nagios::Monitoring::Plugin::Getopt.3pm
Manifying blib/man3/Nagios::Monitoring::Plugin::Functions.3pm
Manifying blib/man3/Nagios::Monitoring::Plugin::ExitResult.3pm
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/check_stuff.t ..............................
Dubious, test returned 13 (wstat 3328, 0xd00)
Failed 13/14 subtests
t/Nagios-Monitoring-Plugin-01.t ..............
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 15/15 subtests
t/Nagios-Monitoring-Plugin-02.t ..............
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 103/103 subtests
t/Nagios-Monitoring-Plugin-03.t ..............
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 61/61 subtests
t/Nagios-Monitoring-Plugin-04.t ..............
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 30/30 subtests
t/Nagios-Monitoring-Plugin-Functions-01.t ....
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 113/113 subtests
t/Nagios-Monitoring-Plugin-Functions-02.t ....
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 37/37 subtests
t/Nagios-Monitoring-Plugin-Functions-03.t ....
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 8/8 subtests
t/Nagios-Monitoring-Plugin-Getopt-01.t .......
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 76/76 subtests
t/Nagios-Monitoring-Plugin-Getopt-02.t .......
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 14/14 subtests
t/Nagios-Monitoring-Plugin-Getopt-03.t .......
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 1/1 subtests
t/Nagios-Monitoring-Plugin-Getopt-04.t .......
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 11/11 subtests
t/Nagios-Monitoring-Plugin-Performance-02.t ..
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 3/3 subtests
t/Nagios-Monitoring-Plugin-Performance.t .....
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run
t/Nagios-Monitoring-Plugin-Range.t ...........
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 151/151 subtests
t/Nagios-Monitoring-Plugin-Threshold.t .......
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 93/93 subtests

Test Summary Report
-------------------
t/check_stuff.t                            (Wstat: 3328 Tests: 14 Failed: 13)
  Failed tests:  1-10, 12-14
  Non-zero exit status: 13
t/Nagios-Monitoring-Plugin-01.t            (Wstat: 65280 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 15 tests but ran 1.
t/Nagios-Monitoring-Plugin-02.t            (Wstat: 65280 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 103 tests but ran 1.
t/Nagios-Monitoring-Plugin-03.t            (Wstat: 65280 Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 61 tests but ran 2.
t/Nagios-Monitoring-Plugin-04.t            (Wstat: 65280 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 30 tests but ran 1.
t/Nagios-Monitoring-Plugin-Functions-01.t  (Wstat: 65280 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 113 tests but ran 1.
t/Nagios-Monitoring-Plugin-Functions-02.t  (Wstat: 65280 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 37 tests but ran 1.
t/Nagios-Monitoring-Plugin-Functions-03.t  (Wstat: 65280 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 8 tests but ran 1.
t/Nagios-Monitoring-Plugin-Getopt-01.t     (Wstat: 65280 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 76 tests but ran 1.
t/Nagios-Monitoring-Plugin-Getopt-02.t     (Wstat: 65280 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 14 tests but ran 1.
t/Nagios-Monitoring-Plugin-Getopt-03.t     (Wstat: 65280 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
t/Nagios-Monitoring-Plugin-Getopt-04.t     (Wstat: 65280 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 11 tests but ran 1.
t/Nagios-Monitoring-Plugin-Performance-02.t (Wstat: 1024 Tests: 4 Failed: 4)
  Failed tests:  1-4
  Non-zero exit status: 4
  Parse errors: Bad plan.  You planned 3 tests but ran 4.
t/Nagios-Monitoring-Plugin-Performance.t   (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/Nagios-Monitoring-Plugin-Range.t         (Wstat: 65280 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 151 tests but ran 1.
t/Nagios-Monitoring-Plugin-Threshold.t     (Wstat: 65280 Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 93 tests but ran 2.
Files=16, Tests=33,  1 wallclock secs ( 0.06 usr  0.05 sys +  0.51 cusr  0.11 csys =  0.73 CPU)
Result: FAIL
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: After upgrade attempt - No Monitoring Engine

Post by tgriep »

It looks like one of the required packages didn't install. We would need the full upgrade.log file to verify that.
Try logging in the the XI server and run the following to install them manually.

Code: Select all

yum install --disablerepo=rpmforge -y 'perl(Test::Simple)' 'perl(Class::Accessor)' perl-Params-Validate perl-Config-Tiny
Then try the upgrade if there are no errors from the above.
Let us know if this helps.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Bionic___
Posts: 54
Joined: Wed Oct 23, 2013 7:49 am

Re: After upgrade attempt - No Monitoring Engine

Post by Bionic___ »

I got the packages installed but the install is still failing.
I have attached the update log.
We have a service provider maintaining the OS and they have the only access to the RedHat repositories. They installed the packages.
You do not have the required permissions to view the files attached to this post.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: After upgrade attempt - No Monitoring Engine

Post by tgriep »

This is from the upgrade.log file
No package perl(Test::Simple) available.
No package perl(Class::Accessor) available.
No package perl-Config-Tiny available.
No package perl-Math-Calc-Units available.
So it looks like they didn't installed.

If this system doesn't have access to the repositories that it needs, that will cause issues.
Is there a chance to allow the system to have the repos enabled while doing the upgrade?

Can you login to the XI server and run the following commands and attach the /tmp/output.txt file?
yum repolist >/tmp/output.txt
yum list installed >>/tmp/output.txt
yum cpan -l >>/tmp/output.txt
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked