Xymon Mailing List Archive search

corrupted ps output report?

5 messages in this thread

list Bill Arlofski · Fri, 15 Oct 2010 15:10:33 -0400 ·
I just noticed a PROCS report go red and then green on one of the servers I
monitor.

Since the server is an LDAP server, one of the proc tests we monitor for is
simply:

PROC  /usr/lib/openldap/slapd


The procs report page showed:

(red) /usr/lib/openldap/slapd (found 0, req. 1 or more)

The ps output below it it looks to be corrupted partway through. The format
and line wrapping clearly does not look correct.

I attached an image rather than pasting here since it would surely add
additional wrapping, confusing matters even more.

I guess I am wondering if anyone has seen such a thing and what might have
caused it, and obviously how to address it.

Thanks

--
Bill Arlofski
Reverse Polarity, LLC
Attachments (1)
list Josh Luthman · Fri, 15 Oct 2010 15:38:21 -0400 ·
Is that the output of ps or was it ruined between ps and the server's logs?

Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
quoted from Bill Arlofski


On Fri, Oct 15, 2010 at 3:10 PM, Bill Arlofski <user-0b8af203a56e@xymon.invalid>wrote:
I just noticed a PROCS report go red and then green on one of the servers I
monitor.

Since the server is an LDAP server, one of the proc tests we monitor for is
simply:

PROC  /usr/lib/openldap/slapd


The procs report page showed:

(red) /usr/lib/openldap/slapd (found 0, req. 1 or more)

The ps output below it it looks to be corrupted partway through. The format
and line wrapping clearly does not look correct.

I attached an image rather than pasting here since it would surely add
additional wrapping, confusing matters even more.

I guess I am wondering if anyone has seen such a thing and what might have
caused it, and obviously how to address it.

Thanks

--
Bill Arlofski
Reverse Polarity, LLC

list Henrik Størner · Fri, 15 Oct 2010 20:07:20 +0000 (UTC) ·
quoted from Bill Arlofski
In <user-aef860a4cbec@xymon.invalid> Bill Arlofski <user-0b8af203a56e@xymon.invalid> writes:
I just noticed a PROCS report go red and then green on one of the servers I
monitor.
Since the server is an LDAP server, one of the proc tests we monitor for is
simply:
PROC  /usr/lib/openldap/slapd
The procs report page showed:
(red) /usr/lib/openldap/slapd (found 0, req. 1 or more)
The ps output below it it looks to be corrupted partway through. The format
and line wrapping clearly does not look correct.

Sounds like a bug that was fixed only last week - it's been lurking in
the 4.2.x and 4.3.x code for a very long time. I'd suggest grabbing the
current code from the Subversion repository on Sourceforge, or wait a
few days for the next beta release.


Regards,
Henrik
list Bill Arlofski · Fri, 15 Oct 2010 16:08:01 -0400 ·
quoted from Josh Luthman
On 10/15/10 15:38, Josh Luthman wrote:
Is that the output of ps or was it ruined between ps and the server's logs?
Hi Josh...

I am ass-u-me'ing that is the output of ps that the xymon client on the LDAP
server runs (had run) and sends to the xymon server.   If the snip was too
small to recognize where it came from, that was a snip from the the bottom
portion of a PROC report page (ie: the output of a ps command)

And where (or how) it was ruined is really my question. Seems kind of strange
to get that type of output from ps...

If I can catch it at the time the report comes in, and manually run ps on that
server, I am pretty sure the output would not me malformed like that was.

So, I am a bit concerned. Trying to keep false positives to a minimum as you
can imagine. :)


-- 
Bill Arlofski
Reverse Polarity, LLC
list Bill Arlofski · Fri, 15 Oct 2010 16:22:17 -0400 ·
quoted from Henrik Størner
On 10/15/10 16:07, Henrik St??rner wrote:
Sounds like a bug that was fixed only last week - it's been lurking in
the 4.2.x and 4.3.x code for a very long time. I'd suggest grabbing the
current code from the Subversion repository on Sourceforge, or wait a
few days for the next beta release.


Regards,
Henrik
Excellent!  Thank Henrik.    I can wait. I just wanted to report this to the
list to see if I was the only one. I probably should have checked the bugs
list at sourceforge first.   Thanks again.

--
Bill Arlofski
Reverse Polarity, LLC