What causes 2nd service check?

[bru1n at comcast.net]

The single service check I have configured flaps, although the data does not. I even recieved a flap warning for this service over the weekend.

event log:
Service Ok[04-25-2005 09:26:47] SERVICE ALERT: tbird;unix-swap-space;OK;SOFT;3;DISK WARNING - free space: /tmp 13085 MB (96%):
Service Warning[04-25-2005 09:25:47] SERVICE ALERT: tbird;unix-swap-space;WARNING;SOFT;2;DISK WARNING - free space: /tmp 13085 MB (96%)

I changed the service definition to is_volatile=1, and got this:

Service Ok[04-25-2005 09:46:33] SERVICE ALERT: tbird;unix-swap-space;OK;HARD;4;DISK WARNING - free space: /tmp 13085 MB (96%):
Service Warning[04-25-2005 09:41:33] SERVICE ALERT: tbird;unix-swap-space;WARNING;HARD;4;DISK WARNING - free space: /tmp 13085 MB (96%):

The scheduler, and service check detail pages do not report this 2nd check, which flips the state incorrectly. 

More evidence:
from $USER1$/var/status.dat regarding the service on the host:
Note the "***'s" I've added to make comments.

service {
        host_name=tbird
        service_description=unix-swap-space
        modified_attributes=0
        check_command=check-unix-swap
        event_handler=
***        has_been_checked=1
        should_be_scheduled=1
        check_execution_time=0.293
        check_latency=0.220

***        current_state=0
*** This is an incorrect state, according to the plugin-output, below

        last_hard_state=0
        current_attempt=1
        max_attempts=4
        state_type=1
        last_state_change=1114431325
        last_hard_state_change=1114423945
        last_time_ok=1114442482
        last_time_warning=1114431265
        last_time_unknown=0
        last_time_critical=0
***        plugin_output=DISK WARNING - free space: /tmp 13085 MB (96%):
***        performance_data=/tmp=520MB;136;1360;0;13605
*** This service check reports a warning, not an Ok (RC=0)

***        last_check=1114442482
***        next_check=1114442782
*** Why are these the same time?

        check_type=0
        current_notification_number=0
        last_notification=0
        next_notification=0
        no_more_notifications=0

I really want to leverage the object definitions, and not have to go 1.2. Does anyone have any ideas why this is happening and better yet, how to make it work like all the other 2.03b setups. I can't think of anything I've dome to make this behave so inconsistantly. I used nearly all of the defaults to this point.

-Marc


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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