AnsweredAssumed Answered

Probe warning messages from controller

Question asked by david.pippenger on Jun 23, 2010
Latest reply on Jun 24, 2010 by david.pippenger

I have a small timed probe written in bash (one of many) that seems to periodically cause the controller to throw out an error message I can't translate. 

 

Timed probe check_vax_udp_ports returned error code 0/15. 

 

The "0/15" is what I'm having problems with. Through trial and error in the past I determined the first number in the #/# sequence is the exit code of the probe itself. In this case it's zero as I expect since the probe is exiting normally with an "exit 0". It's really the second number I can't work out.... 15 is definitely not an exit code being generated by my script... even if it was unless someone changed the way exit codes work you only get one per exit, not two.... 

 

I do fork a compiled helper app in the execution of the bash... so I was trying to work out if maybe the 15 represented the controller killing a sub-process or something.... but I'm really just not sure. It would be great if someone could give me a definitive answer about that second number's source. 

 

--Dave P.

Outcomes