Xymon Mailing List Archive search

Xymon losing processes

4 messages in this thread

list Ryan Skadberg · Tue, 28 May 2013 12:02:16 -0400 ·
So, I got an email saying this:

&red %^syslog-ng$ (found 0, req. between 1 and 1)

Yet, in the process list in the same email is this:

  PID  PPID USER      STARTED S PRI %CPU     TIME %MEM   RSZ    VSZ CMD
11357     1 root       May 20 S  24 23.3 1-05:57:01  0.2 10028 26356
syslog-ng

It seems when the CPU percentage gets to a certain level, Xymon no longer
sees the process as valid.

Any ideas on fixing this?

Thanks!
Skadz
list Phil Crooker · Wed, 29 May 2013 09:08:54 +1000 ·
Have you tried it without the regular expression components? I've had a lot of problems getting those to work in analysis.cfg. Try it with just a straight string.
 
cheers, Phil
quoted from Ryan Skadberg
 

So, I got an email saying this:

&red %^syslog-ng$ (found 0, req. between 1 and 1)

Yet, in the process list in the same email is this:

PID PPID USER STARTED S PRI %CPU TIME %MEM RSZ VSZ CMD
11357 1 root May 20 S 24 23.3 1-05:57:01 0.2 10028 26356 syslog-ng

It seems when the CPU percentage gets to a certain level, Xymon no longer sees the process as valid.

Any ideas on fixing this?

Thanks!
Skadz
list Jeremy Laidman · Wed, 29 May 2013 10:27:11 +1000 ·
quoted from Ryan Skadberg
On 29 May 2013 02:02, Ryan Skadberg <user-fd74ceebcd5d@xymon.invalid> wrote:
It seems when the CPU percentage gets to a certain level, Xymon no longer
sees the process as valid.

This is a known problem, and AFAIK it hasn't been fixed.  Read the thread
here, which includes a fix for Linux:

http://lists.xymon.com/pipermail/xymon/2011-August/032153.html

J
list Ryan Skadberg · Tue, 28 May 2013 22:17:53 -0400 ·
Thanks Jeremy, will add that patch to my rpm build for the next release.

Skadz
quoted from Jeremy Laidman


On Tue, May 28, 2013 at 8:27 PM, Jeremy Laidman <user-71895fb2e44c@xymon.invalid>wrote:
On 29 May 2013 02:02, Ryan Skadberg <user-fd74ceebcd5d@xymon.invalid> wrote:
It seems when the CPU percentage gets to a certain level, Xymon no longer
sees the process as valid.

This is a known problem, and AFAIK it hasn't been fixed.  Read the thread
here, which includes a fix for Linux:

http://lists.xymon.com/pipermail/xymon/2011-August/032153.html

J