On 17 May 2010, at 21:19, Sean R. Kirkpatrick wrote:
We’ve been having an unfortunate episode with the previous version
of Opsview community – in particular, when the new release was
announced a short time ago, we were unable to turn off the warning
notification. Upgrading the version was simply not a significant
issue for us as the previous version was working well, and we didn’t
see any compelling reason to upgrade.
We tried disabling notifications for the service, the host, and even
deleting the check completely, to no avail. Yesterday my boss
changed the 24x7 notification time period to be 02:00 – 24:00, all
in the hopes of disabling the 00:23 Warning Opsview Upgrade message
(the poor fellow on call just can’t get excited about a pending
update, mind you, and he’s getting grumpy that we can’t turn the
damn thing off.) This failed to prevent the message from being sent.
So my resistance to updating Opsview has been beaten down, and today
I installed the 3.7 version of Opsview Community. Imagine my
surprise when I again received the Update Warning at 12:23 – it
doesn’t exist! How can it be warning still?
Imagine my further surprise when I tried to reset the 24x7 time to
00:00 – 24:00, only to be told that “This object cannot be edited.”
Fine, I’ll just hand edit the nagios timeperiods.cfg file and reset
the configuration. Nope, didn’t work, 24x7 still says 02:00 – 24:00.
Can anyone please help me resolve these issues?
To sort out the timeperiod one (I guess we didn't expect anyone to
change the 24x7 timeperiod to not actually be 24x7), start a mysql
session and run:
update timeperiods set sunday='00:00-24:00', monday='00:00-24:00',
tuesday='00:00-24:00', wednesday='00:00-24:00',
thursday='00:00-24:00', friday='00:00-24:00', saturday='00:00-24:00',
sunday='00:00-24:00' where id=1;
As to the mysterious extra Opsview Update warnings - are you sure it
is coming from this particular Opsview instance? Maybe you have a test
environment which is sending the alert out?
Perhaps you have a distributed environment and the check is assigned
to run from a slave (it should only run from the master). Look at the
servicecheck definition and see how many hosts it is associated with.
If you set notifications for this particular service check to not send
warnings, then this should be blocked.
Ton
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
