Upgrade to Nagios 2014 failed

[sreinhardt]

Did you remove the broker_module line at the bottom of your config referencing mod_gearman? Maybe it would be easier to ask for the nagios.cfg again and we can also verify.

[RIDS_I2MP]

HI Team,

before I share the nagios.cfg, Please suggest the best way to proceed here. I have restored back to Nagios 2012R2.8c, Do you suggest I comment out the Modgearman broker module line in nagios.cfg file, stop the modgearman and worker services and then proceed with upgrade or run upgrade and then follow the above steps before restarting the nagios service?

[slansing]

You can either comment it out and stop the modgearman service, then try to upgrade, or you can completely remove it. Now, not upgrading mod_gearman will not cause your upgrade to fail alone, but once you do upgrade you will need to update your gearman install to one that is compatible with Nagios Core 4 following my post here, page 2:

http://support.nagios.com/forum/viewtop ... n&start=10

[RIDS_I2MP]

Hi,

I'm planning to run this upgrade again today and install the mod-gearman after I get the error message, however, I'm stuck with a question now, what if the upgrade still fails? will a restore change the mod-gearman files as well (I mean would it revert the version of mod-gearman as well)?

Also, Please suggest how I uninstall Mod-Gearman from my System

[abrist]

what if the upgrade still fails? will a restore change the mod-gearman files as well (I mean would it revert the version of mod-gearman as well)?

well, an XI restore would not entirely revert mod_gearman. Your best bet would be to do what Sam suggested:
stop the gearmand and mod_gearman_worker processes:

Code: Select all

service gearmand stop
service mod_gearman_worker stop

Comment out the broker line in your nagios.cfg for the time being, for example:

Code: Select all

#broker_module=.../mod_gearman.o server=localhost:4730 eventhandler=yes services=yes hosts=yes

Then run the XI upgrade. After it completes, follow Sam's steps on the following thread to get gearman working with core 4 and XI2014:
http://support.nagios.com/forum/viewtop ... =10#p97980

[lmiltchev]

If you see a config error during an upgrade to XI 2014, where it is NOT shown WHAT the error actually is, the error is most probably associated with service dependencies or service escalations. If you have any service dependencies or escalations defined, you can try just deactivating them in the CCM, and trying to run the upgrade again. I've seen this a few times already...

Regarding Mod Gearman, you can see what packages you have on your system by running:

Code: Select all

yum list installed | grep gearman

Then you can remove them by running:

Code: Select all

yum remove <package1> <package2> ...

[tribbink]

My Upgrade from Nagios 2012R2.9 to 2014 lates version also fails, with the same error.

/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg --> 0 warning and 0 errors
NDO2DB 1.5.2

Mod gearman is not installed.

make[1]: Leaving directory `/tmp/nagiosxi/subcomponents/nagioscore/nagios-4.0.6'
Running configuration check... CONFIG ERROR! Restart aborted. Check your Nagios configuration.

after the upgrade NagiosXI2014 fails - monitoring Engine wil not start. Error

Have to roll back VMWare snapshot

[lmiltchev]

If you see a config error during an upgrade to XI 2014, where it is NOT shown WHAT the error actually is, the error is most probably associated with service dependencies or service escalations. If you have any service dependencies or escalations defined, you can try just deactivating them in the CCM, and trying to run the upgrade again. I've seen this a few times already...

Did you try this?

[tribbink]

i dont have configured those dependicies
They are empty

[lmiltchev]

Both are empty?

Code: Select all

cat /usr/local/nagios/etc/serviceescalations.cfg
cat /usr/local/nagios/etc/servicedependencies.cfg

Can you rerun the upgrade as such:

Code: Select all

cd /tmp/nagiosxi
./upgrade | tee /tmp/debug.txt

and post the "debug.txt" file that was generated in the "/tmp/" directory by running the above command?