check_cluster2 problem found - looking for a solution

[Subhendu Ghosh]

I thought you already had the sevice IDs as they were being passed (not 
completely) to check_cluster2...

On Wed, 2 Feb 2005, Greg Vickers wrote:

> Thanks for the info Subhendu - where can I find the service ID #'s?
>
> Subhendu Ghosh wrote:
>> shell wrapper around check_cluster with all the Service IDs hardcoded...
>> -sg
>> 
>> On Wed, 2 Feb 2005, Greg Vickers wrote:
>> 
>>> Hi all,
>>> 
>>> I'm pretty sure that I know what the problem is with passing a massive 
>>> list of service IDs to check_cluster2.
>>> 
>>> This is my theory: When Nagios forks off a process to run check_cluster2 
>>> the list of service state ID numbers (converted by Nagios from on-demand 
>>> macros) is passed on the command line. The numbers are many characters 
>>> long and the environment that check_cluster2 runs in doesn't have enough 
>>> space on the command line for all the numbers. Any characters that make up 
>>> the 23rd ID number are truncated, hence 1 service always critical, that 
>>> service ID isn't found.
>>> 
>>> Does this sound like what is happening? Is there another clever way to 
>>> pass the list of service state ID numbers to the forked process so that 
>>> there is no truncation and you can pass as many service state ID numbers 
>>> as you want?
>>> 
>>> If you can help or have suggestions please email me or the list :)
>>> 
>>> Thanks,
>>> 
>> 
>
>

-- 



-------------------------------------------------------
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