Service alerts misinterpreted

[Ian Davidson]

The 3x service alerts which are nsca'd to the central server are:

SERVICE ALERT: emea-cns3;check-halo-service;CRITICAL;SOFT;1; Halo: Stopped
SERVICE ALERT: emea-cns3;check-halo-service;CRITICAL;SOFT;2; Halo: Stopped
SERVICE ALERT: emea-cns3;check-halo-service;CRITICAL;HARD;3; Halo: Stopped


But in the nagios.log file, these are interpreted as:

EXTERNAL COMMAND: 
PROCESS_SERVICE_CHECK_RESULT;emea-cns3;check-halo-service;2; Halo: Stopped
EXTERNAL COMMAND: 
PROCESS_SERVICE_CHECK_RESULT;emea-cns3;check-halo-service;2; Halo: Stopped
EXTERNAL COMMAND: 
PROCESS_SERVICE_CHECK_RESULT;emea-cns3;check-halo-service;2; Halo: Stopped


Why!!! How are these being misunderstood?

Cheers,
--
Ian Davidson
Corporate Network Services
Juniper Networks
Tel: +44-1372-385653
GSM: +44-7952-173703

"Chaos, panic & disorder - my work here is done."



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
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