I know this is how the server is failing because of a review of the
Windows Event logs. The server is crashing because of a memory leak.
First it stops accepting incoming HTTP requests to try and conserve what
memory is left, then it stops accepting RDP connections, then the TCP/IP
fails completely. And yes, it is a Mount Everest of problems as it's my
RES PowerFuse server that provides remote desktop to remote users in a
Citrix type environment. Fortunately when the HTTP stops accepting
connections, I can usually log in via RDP remotely and reboot the
server, but I would like to know if I've missed the window and RDP is no
longer up and running and I have to physically drive to the site and
reboot from there. Once RDP fails, TCP/IP is usually right behind it. An
update on OS and PowerFuse software is scheduled, but until then, I have
to keep the remote users up and running.
Nagios Version: 3.0b5
Services Checked: HTTP (check_http), PING (check_ping), RDP (check_tcp
3389)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hugo
van der Kooij
Sent: Monday, November 26, 2007 12:06 PM
To: Nagios Users Mailinglist
Subject: Re: [Nagios-users] Nagios Doesn't Notify for Multiple Services
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joel Roberts wrote:
> I have a server that has been crashing in the following order:
>
> HTTP 80 fails
> RDP 3389 fails
> TCP/IP Stack fails
I think this is not the way things go down the drain.
> I have set up monitoring and notifications for each one, but I only
> receive notifications for the first failure, port 80 not responding.
> Once RDP fails I don't receive alerts and once the TCP/IP stack fails
> (PING stops responding) I don't receive alerts for that either.
After a service check fails the host check kicks in. So if the host
check also fails there will be no further service checks.
Now assume that the TCP/IP stack fails. Then all services depending on
it will be in a heap of trouble. (If you think Mount Everest is a big
heap. It is peanuts compared to this one.)
Just to see if my theory is right.
- Stop HTTP service. Wait for notification.
- Stop RDP service. Do you get a notification?
If this scenario works then the probem is that your system died not like
you expected and indicated above but in a different manner.
Also: What does your log tell you about notifications and events?
My 0.02 Euro says it is not a Nagios issue but something odd with the
host tested.
PS: Did you ever provide us with the required details? Like the Nagios
version, description of the service and host checks used, . ?
Hugo.
- --
[EMAIL PROTECTED] http://hugo.vanderkooij.org/
PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc
A: Yes.
>Q: Are you sure?
>>A: Because it reverses the logical flow of conversation.
>>>Q: Why is top posting frowned upon?
Bored? Click on http://spamornot.org/ and rate those images.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFHSxktBvzDRVjxmYERAvp/AKCcZtCMWNV3d5pFObSSBSsxNgrhiACgn/6t
2OxSuzXCpiE1+hkDFzh5NlE=
=NA/6
-END PGP SIGNATURE-
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@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
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@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
