How to debug Nagios

[Greg Vickers]

I've found the problem - truncated service id's do not cause an error to 
be reported from check_cluster2 e.g.:

$USER1$/check_cluster2 <blah> <blah> 
$SERVICESTATE:hostid:serviceid$,$SERVICESTATE:hos<EOL>

Does not cause an error and reports on the service status up to the last 
complete service state id - so I assume that the environment is running 
out of space at the 22 service mark when the nagios exe forks 
check_cluster2 with a massive command line...

Does anyone have any ideas on how to get around this problem apart from 
having a great big command line environment variable? And how would I 
set this environment variable so that a large command line space is 
available to check_cluster2?

Thanks,
Greg

Greg Vickers wrote:
> Hi all,
> 
> I'm having a problem with Nagios 2.0b1 and plugins 1.4b1 - 
> check_cluster2 doesn't seem to accept more than 22 services to check in 
> one hit.
> 
> Is there a way I can watch how Nagios and check_cluster2 interact so I 
> can try to find where the problem is happening?
> 
> Thanks,

-- 
Greg Vickers
Lab Monitor Project Manager
Teaching and Learning Services
Information Technology Services
Queensland University of Technology

email: g.vickers at qut.edu.au
phone: (07) 3864 8276

CIROS code: 00213J


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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