Nagios Support Forum

We have 5 servers ,one test and 4 production.

We have spanned upgrade activity to into four weeks as below

1 week test server
2nd week gap- To test the functionality on test
3rd week 2 production
4th week 2 production

While we did perform upgrade on test it was upgraded from 2.5 to 2.7.
when we did in 3rd week prod it changed from 2.5 to 2.8b
4th week production changed from 2.5 to 2.8c


We did test 2.7 thoroughly but we got new updates on production which we could not test and might cause issues.
Is there any way to hold on new upgrades like just perform upto 2.7 onto production servers and hold off rest of updates(2.7b,2.8c) to next patching cycle.

ravish78 wrote:Is there any way to hold on new upgrades like just perform upto 2.7 onto production servers and hold off rest of updates(2.7b,2.8c) to next patching cycle.

Yes. Just change th url for teh XI download to an older version. For example, the current version is:
http://assets.nagios.com/downloads/nagi ... .8c.tar.gz
Change xi-2012r2.8c.tar.gz to xi-2012r2.7.tar.gz in the url to download an older version:
http://assets.nagios.com/downloads/nagi ... 2.7.tar.gz

Yes, you can always take the tarball that you used for the 2.7 updates and apply that to other systems as well, in fact for your situation, I would highly suggest doing just that instead of using xi-latest.tar.gz. I can provide a link to the 2.7 tarball if you need it still, although I do not believe you can downgrade to 2.7 from 2.8, so it might be best to test and upgrade to 2.8.c when possible.

This can work for us.

We will follow your suggestion of using the downloaded tar-ball in all servers instead of downloading latest one.

As we have upgraded all the systems to 8.c except one we will follow this from next cycle.Thanks for your help.