Your message dated Wed, 11 Nov 2009 22:32:00 +0100
with message-id <200911112232.07138.w...@cyconet.org>
and subject line Re: [Pkg-nagios-devel] Bug#546195: nagios-plugins-basic: using 
check: /usr/lib/nagios/plugins/check_procs ... -C X does not work
has caused the Debian Bug report #546195,
regarding nagios-plugins-basic: using check: 
/usr/lib/nagios/plugins/check_procs ... -C X does not work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
546195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nagios-plugins-basic
Version: 1.4.5-1etch1
Severity: important



-- System Information:
Debian Release: 4.0
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.26-bpo.2-686
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)

Versions of packages nagios-plugins-basic depends on:
ii  iputils-ping        3:20020927-6         Tools to test the reachability of 
ii  libc6               2.3.6.ds1-13etch9+b1 GNU C Library: Shared libraries
ii  libssl0.9.8         0.9.8c-4etch5        SSL shared libraries
ii  procps              1:3.2.7-3            /proc file system utilities
ii  ucf                 2.0020               Update Configuration File: preserv

nagios-plugins-basic recommends no packages.

-- no debconf information

There is bug inside the check_procs (c-code module). You cannot
run check with big X (you know X11). This came out from thin client
testings in LTSP, where check fails, while checking:

/usr/lib/nagios/plugins/check_procs -w 1:1 -c 1:2 -C X

check eats parameter big X somehow strange, giving always 0 procs.



--- End Message ---
--- Begin Message ---
Version: 1.4.12-5

Hi Juhani,

thanks for you reply.

On Monday, 21. September 2009, Juhani Puska wrote:
> This has been collected from out testlab (LTSP), command output
>  attacheched, Interesting row is here:
> 
> Ss+      0  4165  4163  16668 10468  0.1 Xorg            X -auth
> /var/run/ldm-xauth-LABLN4123 -br -noreset -depth 16 vt7 :7
> 
> parameter -C X does not recognize it. I have also found other process
>  (amavisd) which does not filtered by name:

on a lenny installation:

$ /usr/lib/nagios/plugins/check_procs -vvv -w 1:1 -c 1:2 -a "X" > 
/tmp/test.txt; grep "X" /tmp/test.txt
Ss+      0  4378  4374 294768 242756 1.4 Xorg            /usr/X11R6/bin/X :0 
-audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
proc#=0 uid=0 vsz=294768 rss=242756 pid=4378 ppid=4374 pcpu=1.40 stat=Ss+ 
etime= prog=Xorg args=/usr/X11R6/bin/X :0 -audit 0 -auth /var/lib/gdm/:0.Xauth 
-nolisten tcp vt7
Matched: uid=0 vsz=294768 rss=242756 pid=4378 ppid=4374 pcpu=1.40 stat=Ss+ 
etime= prog=Xorg args=/usr/X11R6/bin/X :0 -audit 0 -auth /var/lib/gdm/:0.Xauth 
-nolisten tcp vt7
S+    1000 23188 22829   3076   780  0.0 check_procs     
/usr/lib/nagios/plugins/check_procs -vvv -w 1:1 -c 1:2 -a X
proc#=1 uid=1000 vsz=3076 rss=780 pid=23188 ppid=22829 pcpu=0.00 stat=S+ etime= 
prog=check_procs args=/usr/lib/nagios/plugins/check_procs -vvv -w 1:1 -c 1:2 -a 
X
PROCS OK: 1 process with args 'X'

$ /usr/lib/nagios/plugins/check_procs -vvv -w 1:1 -c 1:2 -a "amavisd" > 
/tmp/test.txt; grep "amavisd" /tmp/test.txt
Ss     106  7074     1  31024 22528  0.0 amavisd-new     amavisd (master)
proc#=0 uid=106 vsz=31024 rss=22528 pid=7074 ppid=1 pcpu=0.00 stat=Ss etime= 
prog=amavisd-new args=amavisd (master)
Matched: uid=106 vsz=31024 rss=22528 pid=7074 ppid=1 pcpu=0.00 stat=Ss etime= 
prog=amavisd-new args=amavisd (master)
S      106  7075  7074  31936 22016  0.0 amavisd-new     amavisd (virgin child)
proc#=1 uid=106 vsz=31936 rss=22016 pid=7075 ppid=7074 pcpu=0.00 stat=S etime= 
prog=amavisd-new args=amavisd (virgin child)
Matched: uid=106 vsz=31936 rss=22016 pid=7075 ppid=7074 pcpu=0.00 stat=S etime= 
prog=amavisd-new args=amavisd (virgin child)
S      106  7076  7074  31936 22004  0.0 amavisd-new     amavisd (virgin child)
proc#=2 uid=106 vsz=31936 rss=22004 pid=7076 ppid=7074 pcpu=0.00 stat=S etime= 
prog=amavisd-new args=amavisd (virgin child)
Matched: uid=106 vsz=31936 rss=22004 pid=7076 ppid=7074 pcpu=0.00 stat=S etime= 
prog=amavisd-new args=amavisd (virgin child)
R+    1000  7098  6722   3872   684  0.0 check_procs     
/usr/lib/nagios/plugins/check_procs -vvv -w 1:1 -c 1:2 -a amavisd
proc#=3 uid=1000 vsz=3872 rss=684 pid=7098 ppid=6722 pcpu=0.00 stat=R+ etime= 
prog=check_procs args=/usr/lib/nagios/plugins/check_procs -vvv -w 1:1 -c 1:2 -a 
amavisd
PROCS CRITICAL: 3 processes with args 'amavisd'

> I have't look (no time at the moment) the c-code, but both of these are
> multirunning processes, like here amavisd:
> 
>   1583 ?        Ss     0:01 amavisd (master)
> 30939 ?        S      0:00  \_ amavisd (ch7-avail)
> 31005 ?        S      0:00  \_ amavisd (ch8-avail)
> 32474 ?        S      0:00  \_ amavisd (ch7-avail)
>    427 ?        S      0:01  \_ amavisd (ch6-avail)
>   1509 ?        S      0:00  \_ amavisd (ch2-avail)

$ ps aux|grep ^amavis
amavis    7074  0.0  1.4  31024 22528 ?        Ss   22:27   0:00 amavisd 
(master)
amavis    7075  0.0  1.3  31936 22016 ?        S    22:27   0:00 amavisd 
(virgin child)
amavis    7076  0.0  1.3  31936 22004 ?        S    22:27   0:00 amavisd 
(virgin child)

so it looks this was fixed during the Lenny release cycle.

With kind regards, Jan.
-- 
Never write mail to <w...@spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++ 
------END GEEK CODE BLOCK------

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to