[Nagiosplug-checkins] Assistance needed with check_procs runn ing on AIX

[Voon, Ton]

Ludse,
 
We've had reported successes of check_procs on AIX with r1.3.0, so I'm a bit
surprised there is a problem.
 
Can you use the latest snapshots at
http://nagiosplug.sourceforge.net/snapshot/
<http://nagiosplug.sourceforge.net/snapshot/>  and run check_procs -v -v -v
and send the output?
 
Which ps command do you use?
 
Ton

-----Original Message-----
From: Ludse.Verhoeven at VOPAK.COM [mailto:Ludse.Verhoeven at VOPAK.COM] 
Sent: Monday, September 01, 2003 11:54 AM
To: nagiosplug-checkins at lists.sourceforge.net
Subject: [Nagiosplug-checkins] Assistance needed with check_procs running on
AIX



Hello, 

Joined this mailing-list just the other day, mainly because I have a problem
with the check_procs-plugin. On Linux the plugin works just fine, but I've
also compiled the plugin for use on several AIX 4.3.3-servers (I know, it's
almost outdated ;-) and there it exits with an "segmentation fault" or an
"illegal instruction"-error. Looked on the nagios-plugin-site for newer
releases (we're running v1.3.0 still) and found the v1.3.1-release. But,
after compilation of these sources the same problem exists. 

A bit more in-depth: 
For the 1.3.0-sources to work I already had to modify the configure.in-file
to provide a ps-command with the correct parameters and to interpret these
parameters in the (I thought) correct way. After compilation and testing the
check_procs-command seemed to work just fine and the plugin was implemented
in our checking-procedures via Nagios. However, after a number of days that
AIX-system suddenly gave an "segmentation failure" (rc=139) when running the
check. The check-results however were correct. Not sure what exactly changed
on that system, but 2 other more-or-less identical AIX-servers don't have
that problem. Furthermore, another system, which runs an AIX-4.3.3-version,
but on a Bull-platform, also suddenly came up with errors regarding this
check. In this case the errormessage was "illegal instruction" (rc=132), but
with the same type of problems just stated. 

I imagine that these errors may be a result of the changed
configure.in-parms I've mentioned earlier, but I'm very curious why this
didn't occur in the first place and secondly, what to do about it...... I
know almost for sure that the problem will disappear when I reboot the
system, but that's not an option (at least not for this minor glitch). 

Can anyone help me with this? I can provide details on the changed
configure.in-parms (or any other topic) if necessary. 

With kind regards, 
       L. Verhoeven



This private and confidential e-mail has been sent to you by Egg.
The Egg group of companies includes Egg Banking plc
(registered no. 2999842), Egg Financial Products Ltd (registered
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
carries out investment business on behalf of Egg and is regulated
by the Financial Services Authority.  
Registered in England and Wales. Registered offices: 1 Waterhouse Square,
138-142 Holborn, London EC1N 2NA.
If you are not the intended recipient of this e-mail and have
received it in error, please notify the sender by replying with
'received in error' as the subject and then delete it from your
mailbox.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-plugins.org/archive/commits/attachments/20030901/203af12e/attachment.html>