Hi Ton,
This is what I do to make the upgrades work: To allow the upgrade via apt-get update && apt-get upgrade to complete properly, add the options below and re-run the upgrade * Add to /usr/local/nagios/bin/opsviewd, line 51 ,"-o Port=<other ssh portnr>" * Add to /usr/local/nagios/lib/Opsview/Sshcommands.pm, line 28, "-o","Port=<other ssh portnr>" I appriciate the motivations to fail the complete upgrade, however the issue above would be fixed if opsview.conf would contain a SSH portnr, which is by default 22? BTW I'm following the fora too, however won't loose contact on the mailing list :) Regards Paul -----Original message----- To:Opsview Users <[email protected]>; From:Ton Voon <[email protected]> Sent:Thu 09-12-2010 12:50 Subject:Re: [opsview-users] FW: How do we push new versions to the slave servers after the master is upgraded? Attachment:inline.txt On 8 Dec 2010, at 17:53, Paul wrote: Hi James, ASAIK the suggested way you describe below should work OK. I'm running slaves on a different port than 22, so upgrade always yell slaves can;t be updated. Then I modify two files, indicating the correct port and re-run the update process - which has worked for me for the past 5 times :) Good luck Paul Hi Paul, One thing we were thinking was to force an upgrade to fail if the slaves failed to update. This is the most common case and necessary if, for instance, we make a major update to nagios which will generate a new style configuration which an older nagios would die trying to run (thus slaves just appear to have stopped working) However, this blocks your process. Suggestions? Ton
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
