PROC question

4 messages in this thread

list Doug Williams · Fri, 20 Mar 2009 14:17:07 -0400 ·

Or more like a problem. :)
 
Hi,
 
I have one server that has over 1700 processes, which includes a LOT of
java processes, causing a lot of characters per line.   So the entire PS
output is not sent to the server; is truncated around 1400 lines.
 
The problem is that any PROC I define to be monitored, that happens not
to be within that 1400 lines stays in alarm condition.
 
I played with setting MAXLINE and MAXMSG_STATUS to very high numbers,
but to no success
 
I also noted that in BB man pages it, says:
 
/*
The maximum size of a message is defined by the maximum allowed length
of your shell's command line, and is typically 8-32 KB. 

If you need to send longer status messages, you can specify "@" as the
message: bb will then read the status message from its stdin. 

*/

Is there any way to get default tests such as PROC to be able to use the
"@" capability, or will I just need to create a script monitoring procs
on that server and EXHOST for default PROC test for that server?

Thanks

Doug

list Kristian Nielsen · Sat, 21 Mar 2009 09:03:54 +0100 ·

▸ quoted from Doug Williams

"Williams, Doug (Consultant-RIC)" <user-63162c140807@xymon.invalid> writes:

The problem is that any PROC I define to be monitored, that happens not
to be within that 1400 lines stays in alarm condition.
 
I played with setting MAXLINE and MAXMSG_STATUS to very high numbers,
but to no success

Check `man 5 hobbitserver.cfg`:

       MAXMSG_CLIENT
              The  maximum  size  of  a  "client" message in kB, default: 512.
              "client" messages are generated by the Hobbit client, and  often
              include  large  process-listings. You should only change this if
              you see messages in the hobbitd log file about  client  messages
              being truncated.

Note in particular the bit about checking hobbitd log file first. If the
problem is some size limit, the log should have a message about it, hopefully
showing exactly which limit you need to extend (there are several).

 - Kristian.

list Doug Williams · Sat, 21 Mar 2009 06:53:15 -0600 ·

Yup, that did it!  Thanks Much!!!!!
Doug

▸ quoted from Kristian Nielsen

 

-----Original Message-----
From: Kristian Nielsen [mailto:user-bc00a861a9ff@xymon.invalid] 
Sent: Saturday, March 21, 2009 4:04 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] PROC question

"Williams, Doug (Consultant-RIC)" <user-63162c140807@xymon.invalid> writes:

The problem is that any PROC I define to be monitored, that happens
not
to be within that 1400 lines stays in alarm condition.
 
I played with setting MAXLINE and MAXMSG_STATUS to very high numbers,
but to no success

Check `man 5 hobbitserver.cfg`:

       MAXMSG_CLIENT
              The  maximum  size  of  a  "client" message in kB,
default: 512.
              "client" messages are generated by the Hobbit client, and
often
              include  large  process-listings. You should only change
this if
              you see messages in the hobbitd log file about  client
messages
              being truncated.

Note in particular the bit about checking hobbitd log file first. If the
problem is some size limit, the log should have a message about it,
hopefully
showing exactly which limit you need to extend (there are several).

 - Kristian.

list Henrik Størner · Tue, 24 Mar 2009 13:29:40 +0100 ·

▸ quoted from Doug Williams

On Fri, Mar 20, 2009 at 02:17:07PM -0400, Williams, Doug (Consultant-RIC) wrote:

I have one server that has over 1700 processes, which includes a LOT of
java processes, causing a lot of characters per line.   So the entire PS
output is not sent to the server; is truncated around 1400 lines.
 
The problem is that any PROC I define to be monitored, that happens not
to be within that 1400 lines stays in alarm condition.
 
I played with setting MAXLINE and MAXMSG_STATUS to very high numbers,
but to no success

If this is using the Hobbit client, you will also need to increase
the MAXMSG_CLIENT setting. The Hobbit client sends a CLIENT message
first; the hobbitd_client module on the server then converts this
into a STATUS message for each of the status columns. So you need
to increase both.

▸ quoted from Doug Williams

I also noted that in BB man pages it, says:
 
/*
The maximum size of a message is defined by the maximum allowed length
of your shell's command line, and is typically 8-32 KB. 

If you need to send longer status messages, you can specify "@" as the
message: bb will then read the status message from its stdin. 

*/

The Hobbit client uses the latter method, and does not have the
few KB limit.


Regards,
Henrik

PROC question 🔗 link

PROC question