On 21 May 2009, at 16:27, Andrew Hall wrote: > On 2009-05-21 02:50, James Whittington wrote: > >> I provided the script to one other Opsview list member so I'm >> interested >> to see if it works for him as well. > > Thanks for the script but sadly - due to details in an earlier post - > we cannot run commands via SSH from slave to master. > > This is due to our security team insisting on a restricted shell for > the nagios user on the master. > > However, we have another solution which at the moment is purely at the > design stage...
I think this is a great idea as this means the slave has the knowledge (from the timestamp file) that the master can still communicate correctly. > 1. The master is periodically running "retrieve_opsview_info" on the > slave as part of its standard checks. > > 2. We edit this script so it also touches a file therefore updating > its timestamp. > > 3. A further script on the slave (configured as a local service > check?) considers the difference between the timestamp on this file > and now(). Can you model this nagios plugin on check_opsview_slave_cluster? Maybe call it check_opsview_slave_communication? > 4. If this is over a defined threshold (10 mins?) then it issues a > re-start of the opsview-web service. For extra bonus points, you could create this service automatically on all slaves when the reverse_ssh flag is set. Ton _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/listinfo/opsview-users
