check_procs -C on AIX 5L

RyeR at schneider.com RyeR at schneider.com
Wed Dec 17 19:17:24 CET 2003


I am having issues with the check_procs command on AIX 5L systems.  There
is certain instance where it will report a Critical state of no processes
existing, when indeed the process does exist.  After digging, I believe it
is issuing a ps -el.  I have also changed the check_proc.c code to use the
verbose setting.  This the output when I run the command on a AIX 5L system

root $ ./check_procs -w 1: -c 1: -C syslogd
/usr/bin/ps -el
Not parseable:   200003 A   0      1      0   0  60 20 fb8f000  1928
-  0:28 init
Not parseable:   240001 A   0 131178 155720   0  60 20 1cd1c400   604
-  0:00 syslogd
Not parseable:   240001 A   0 155720      1   0  60 20 2ce2400   712
-  0:00 srcmstr
Not parseable:   240001 A   0 172076 155720   0  60 20 7d27400  3036
-  0:07 sendmail
Not parseable:   240001 A   0 180272 155720   0  60 20 10d30400  1784
-  0:04 portmap
Not parseable:   240001 A   0 188462 155720   0  60 20 6d26400   644
-  0:00 inetd
Not parseable:   240001 A   0 196656 155720   0  48  8 1ad3a400   828
-  0:00 xntpd
Not parseable:   240001 A   0 204852 155720   0  60 20 1d41400   720
-  7:54 dpid2
Not parseable:   240001 A   0 213044 155720   0  60 20 dd4d400   804
-  0:40 hostmibd
Not parseable:   240001 A   0 245824 155720   0  60 20 d60400   356
-  0:00 biod
Not parseable:   240001 A   1 262212 155720   0  60 20 cd4c400  2092
-  0:00 rpc.statd
Not parseable:   240001 A   0 327772 155720   0  60 20 15db5400  1656
-  0:00 dtlogin
Not parseable:    40001 A 560 344258 696544   0  60 20 638e400  1968
-  0:00 sshd
Not parseable:    40001 A   0 385120      1   0  60 20 3de3400   308
-  0:00 diagd
Not parseable:   240001 A   0 434326 491674   0  60 20 bfcb400  2944
- 499:32 dtgreet
Not parseable:   200001 A   0 548906 524386   1  60 20 12c9a400   316
pts/0  0:00 ps
Not parseable:   240001 A 560 630858 344258   0  60 20 68e1400   680
pts/0  0:00 ksh
Not parseable:    40001 A   0 639090      1   0  60 20 1b1b3400  1292
-  0:00 sshd
Not parseable:   200001 A   0 647304 630858   1  60 20 5503400   876
pts/0  0:00 ksh
Not parseable:    40001 A   0 663802      1   0  60 20 1bddb400   416
-  0:02 prngd
syslogd CRITICAL - 0 processes running with command name syslogd

So of course any process listed as "not pareable" does not correctly work.

I was hoping someone might have run into this, before I have to resort to
looking at the source code.

Thanks
Ralph




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at 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





More information about the Users mailing list