Hi,
I'am sorry, but your patch don't seems to work for me...
If i don't use "Include Soft States", my trend never returns from
CRITICAL STATE...
Regards
Eric
[1106321235] SERVICE ALERT: localhost;ssh;CRITICAL;SOFT;1;timeout..10s
[1106321295] SERVICE ALERT: localhost;ssh;CRITICAL;SOFT;2;timeout..10s
[1106321355] SERVICE ALERT: localhost;ssh;CRITICAL;HARD;3;timeout..10s
[1106324425] HOST ALERT: localhost;DOWN;SOFT;1;CRITICAL - timed out
[1106324435] HOST ALERT: localhost;DOWN;SOFT;2;CRITICAL - timed out
...
[1106324515] HOST ALERT: localhost;DOWN;HARD;10;CRITICAL - timed out
[1106324515] HOST NOTIFICATION:...=20
[1106324615] SERVICE ALERT: localhost;PING;CRITICAL;HARD;1;CRITICAL
[1106324825] HOST ALERT: localhost;UP;HARD;1;PING OK
[1106324825] HOST NOTIFICATION: eric;localhost;UP;host-notify;PING OK
[1106324905] SERVICE ALERT: localhost;PING;OK;HARD;1;PING OK
[1106324955] SERVICE ALERT: localhost;ssh;CRITICAL;SOFT;1;Socket timeout
[1106325005] SERVICE ALERT: localhost;ssh;OK;SOFT;2;SSH OK - OpenSSH
Le mercredi 19 janvier 2005 =E0 20:03 -0600, Ethan Galstad a =E9crit :
> On 5 Jan 2005 at 14:22, Strickland, Kristian wrote:
>=20
> > Hi to all, and Happy New Year.
> >=20
> > On 2004-12-13 22:26, Ethan Galstad wrote:
> >=20
> > > I"ll check into modifying the code to do this during the 2.0 beta
> > > process, but I"m not convinced I want to muddle with the CGIs much
> > > anymore unless there are real bugs.
> >=20
> > On the nagios-users list, there's a thread that points out a bug that
> > affects the "Service State Trends". From a post by Eric Bollengier:
> >=20
> > ----------------- quote
> >=20
> > [1099042385] SERVICE ALERT: test;ssh;CRITICAL;SOFT;1;Connection
> > refused [1099042445] SERVICE ALERT: test;ssh;CRITICAL;SOFT;2;Socket
> > timeout [1099042525] SERVICE ALERT: test;ssh;CRITICAL;HARD;3;Socket
> > timeout [1099042715] HOST ALERT: test;DOWN;SOFT;1;CRITICAL
> > [1099042725] HOST ALERT: test;DOWN;SOFT;2;CRITICAL [1099042735] HOST
> > ALERT: test;DOWN;SOFT;3;CRITICAL [1099042745] HOST ALERT:
> > test;DOWN;SOFT;4;CRITICAL [1099042755] HOST ALERT:
> > test;DOWN;HARD;5;CRITICAL [1099042755] SERVICE ALERT:
> > test;ping;CRITICAL;HARD;1;CRITICAL [1099042935] HOST ALERT:
> > test;UP;HARD;1;PING OK [1099042935] SERVICE ALERT:
> > test;ping;OK;HARD;1;PING OK [1099042945] SERVICE ALERT:
> > test;ssh;CRITICAL;SOFT;1;Socket timeout [1099043005] SERVICE ALERT:
> > test;ssh;OK;SOFT;2;TCP OK
> >=20
> > =3D=3D=3D=3D> BUG ssh is in CRITICAL HARD STATE, but OK is SOFT !!
> >=20
> > ----------------- end quote
> >=20
> > I've had this same thing happen to me, though with a different
> > service. The result is a 5 day 8 hour block of "critical" in my
> > report unless I edit the proper log file and change the SOFT to HARD.
> >=20
> > Either fixing the real problem OR including SOFT states in reporting
> > would show the correct states.
> >=20
>=20
> This problem should be fixed in CVS for the daemon now (my commit two=20
> days back). I also added the option to include soft states in the=20
> trends and availability CGIs. Please let me know if the CVS patches=20
> don't fix the logging issue, as I haven't had a lot of time to test=20
> them.
>=20
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]