Service Status Type

[Fernando Gomes Lima]

Hi Jasmine,

I got this screen

Host		Service	Status	Last Check	Duration			Attempt	Status Information
monitor1	PING		CRITICAL	07-10-2003	09:41:28 27d 21h 9m 11s 1/3		 PING
CRITICAL - Packet loss = 0%, RTA = 637.81 ms

I have no idea what's going on!!!

Fernando Gomes
SchlumbergerSema
Network & Infrastructure Solutions
Security Engineer
flima at slb.com

Trab: +55 21 3824 6954
Cel. : +55 21 9888 9046
(GMT: -03:00)



-----Original Message-----
From: Jasmine [mailto:jasmine.chua at securecirt.com]
Sent: quarta-feira, 9 de julho de 2003 18:46
To: flima at slb.com
Cc: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Service Status Type


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That's strange, I have never seen something like that happened in Nagios
before. What do you mean when you said the status is critical? Are you
referring to host or service status? Maybe you can show us more details.

Jasmine

On Thursday 10 July 2003 05:02, Fernando Gomes Lima wrote:
>     Hi all,
>
> We have a host that is up and beeing showed as status critical any idea of
> what's going on?
> Fernando Gomes
> SchlumbergerSema
> Network & Infrastructure Solutions
> Security Engineer
> flima at slb.com
>
> Trab: +55 21 3824 6954
> Cel. : +55 21 9888 9046
> (GMT: -03:00)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/DI01NgvTa7Hj2AURAo8VAJwLZKG1kiar1yCihzA1ZXTXWpBLNACfdwlF
zeEJxuMWAa+TvevAIg3kLFE=
=CbKT
-----END PGP SIGNATURE-----




-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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