[Nagiosplug-help] [Nagios-users] OK prompt in Solaris

[kyle.odonnell at gmail.com]

I use nrpe and snmp to monitor various services on our sun servers.
Each service using either is dependent on the 'nrpe' or 'snmp'
service.  If either of these services go down our ops team
investigates.  If a box drops to the 'ok' prompt, these services will
not be running.

This isn't directly monitoring for a machine at the 'ok' prompt, but
if you send your syslog messages to a centralized host, and monitor
for strings, the combination should make debugging the problem easier.

Alternatively, if you have some kind of portmaster or lantronix device
used to remotly connect to serial console, you could write a plugin to
check through serial.



On 6/20/07, Masopust, Christian <christian.masopust at siemens.com> wrote:
> Hello Lalita,
>
> i think you should be able to use check_tcp with any available port (e.g.
> 21, 23, ...)
>
> Christian
>
>
> --
> "I sense much NT in you, NT leads to Blue Screen.
> Blue Screen leads to downtime, downtime leads to suffering. NT is the path
> to the darkside."
>
> - Unknown Unix Jedi
>
>
>
>
> ________________________________
>
> 	From: nagios-users-bounces at lists.sourceforge.net
> [mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Lalita
> Drolia
> 	Sent: Wednesday, June 20, 2007 12:13 PM
> 	To: nagios-users at lists.sourceforge.net;
> nagiosplug-help at lists.sourceforge.net
> 	Subject: [Nagios-users] OK prompt in Solaris
> 	
> 	
>
> 	Hi,
>
> 	I have come to know that there is a situation in Solaris machines called
> "Ok Prompt" where the machine can be pinged but not accessed as it is hung.
>
> 	Can you tell me the best check to deploy in such a situation? I decided to
> use check_ssh but unfortunately solaris 8 servers do not have ssh installed
> by default.
>
> 	What could be another alternative in such a scenario?
>
> 	Kindly help.
>
> 	Thanks in advance :-)
>
> 	
>
> 	With Regards,
>
> 	Lalita
>
>
> 	Notice: This email message, together with any attachments, may contain
> information of BEA Systems, Inc., its subsidiaries and affiliated entities,
> that may be confidential, proprietary, copyrighted and/or legally
> privileged, and is intended solely for the use of the individual or entity
> named in this message. If you are not the intended recipient, and have
> received this message in error, please immediately return this by email and
> then delete it.
>
>