[EMAIL PROTECTED] schrieb am 17.06.2008 04:28:23:
> I really need some help with this guys. My setup was working for the
> longest time and I can't think of any changes made to it that would
> cause this behavior. I get random (and quite annoying!) Nagios alerts
> that say "Problem: $SERVER is UP!" (with the actual host name) or
> sometimes it just literally says "Problem: HOST is UP". Note, this
> only happens during my off hours time. I've never seen this during the
> day. I'm running Nagios on Debian Etch and I've tried version 3.02
> from the backports and that had the same issue. It has to be my config
> but I can't figure out for the life of me what it could possibly be!
>
> Any help you can give me will be SO much appreciated!
>
> I'm going to attach my configs. Thanks everyone.
After looking throgh the config, I cannot find any culprits which would
cause such behaviour. Maybe you have some bogus notification commands?
The "Problem: ... is UP" doesn't seem to make sense to me and does not
correspond to the default configuration. Recovery alerts shold start
with "Recovery: ..."
Please post your host-notify-by-email command definitions.
Regards
Sascha
--
Sascha Runschke
Netzwerk- und Systemmanagement
Telefon : +49 (201) 102-1879 Mobil : +49 (173) 5419665 Fax : +49 (201)
102-1102105
GFKL Financial Services AG
Vorstand: Dr. Peter Jänsch (Vors.), Jürgen Baltes, Dr. Till Ergenzinger, Dr.
Tom Haverkamp
Vorsitzender des Aufsichtsrats: Dr. Georg F. Thoma
Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
