although I'm not native on rhel and not using upstream packages myself, this maybe due to the major upgrade from 1.10 to .20. For not interrupting services on one node, which also can run multiple sites, it is possible to install multiple (major) versions of omd in parallel. major updates often afford crucial changes to sites, which can't be implemented while running b/c they change syntax and/or configuration files for/or the Backend. This is y you have to manually run omd upgrade site after installation of a major update before you can uninstall the old one. It may be even your "updated" site is still running 1.10 on the other node. You can check w/ omd vetoing SITE the sites actual version. I'm rather not sure y the new version is not actually installing when using your package managers upgrade function, but this may be due to (different) configurations of yum on both nodes, you should review the "working" one. Manual yum install omd-1.20 will temporarily fix the issue for the next 6 month - 1 year i think ; ).
W/ regards Fate Am 25.11.2014 18:48 schrieb "Laura Nunzia Dimauro" <[email protected]>: > Hello, > We are using redhat which uses yum package management. Any idea why omd > is not updating automatically? > > # yum list omd* > Loaded plugins: refresh-packagekit, rhnplugin, security > This system is receiving updates from RHN Classic or RHN Satellite. > Installed Packages > omd-1.10.x86_64 rh61-31 > @labs_consol_stable > Available Packages > omd-1.20.x86_64 rh61-33 > labs_consol_stable > > Thank you > > > ------------------------------ > *From:* Jaroslaw Nowak <[email protected]> > *Sent:* Friday, November 21, 2014 10:20 AM > *To:* Laura Nunzia Dimauro > *Cc:* [email protected] > *Subject:* Re: [omd-users] Question Regarding OMD updates > > > There are of course several ways of doing that in a fully automated > fashion, like using puppet master, for remote updates or similar, but this > would effort such setup and you wouldn't be asking. > for a start, you should use your distributions packet manager for > installing omd from repository. Then you can use your DEV system as > designed by updating your DEV first, verify everything is running as > expected, and updating your production afterwords. > HTTP://labs.consol.de/nagios/omd-repository/ > > When you don't have an identical system and setup on your both nodes, you > should consider that as your starting point. Easiest way is to clone your > machines. As this will make further automation way easier. > > For further readings try searching for howtoforge puppet master and your > distribution. (Expect more advanced content ; ) > > W/ regards, > Fate > Am 21.11.2014 17:37 schrieb "Laura Nunzia Dimauro" <[email protected]>: > >> Hello, >> >> I have subscribed to OMD users. If you could help me with the following >> that would be great. >> >> >> I have OMD running and I've created a site for monitoring with >> Check_MK. I have recently created another site on a server used for >> development purposes and noticed Check_MK was now the most current version, >> 1.2.4p5. >> >> >> Is there a way to set up OMD to automatically update? I want to make >> sure we are using the most current version of Check_MK for all sites at all >> times. >> >> >> Thanks, >> >> Laura >> >> _______________________________________________ >> omd-users mailing list >> [email protected] >> http://lists.mathias-kettner.de/mailman/listinfo/omd-users >> >>
_______________________________________________ omd-users mailing list [email protected] http://lists.mathias-kettner.de/mailman/listinfo/omd-users
