/var/nagios.tmpXXX files never delete (2.0b3)

[Bob Johnson]

Hi Chris,

Thank you for the response and ideas.

> Are you running one of the MSSQL plugins? I think I remember a post a
> few months ago saying that one of those plugins was leaving a lot of
> temporary files around.

I am not running any of the MSSQL plugins, although (probably unrelated) I
am executing a handful of mysql checks.  I would like to lean towards the
plugins as the potential source at this time, but after recompiling the
latest stable release of plugins, there was no net effect.

> You could check the creation date of the files with the "stat" command,
> and correlate it to your nagios.log to see if it was a particular
> service check or notification command that created them, and which one.

Good idea.  Here's some output (all of the tmp files are similar in deltas):

$stat nagios.tmpzZfhVt
  File: `nagios.tmp0eySOR'
  Size: 1912568         Blocks: 3739       IO Block: 131072 regular file
Device: 807h/2055d      Inode: 78325       Links: 1
Access: (0664/-rw-rw-r--)  Uid: ( 1001/  nagios)   Gid: ( 1001/  nagios)
Access: 2005-07-28 00:42:27.000000000 -0700
Modify: 2005-07-28 00:42:27.000000000 -0700
Change: 2005-07-28 00:42:27.000000000 -0700

$more nagios.tmp0eySOR
########################################
#          NAGIOS STATUS FILE
#
# THIS FILE IS AUTOMATICALLY GENERATED
# BY NAGIOS.  DO NOT MODIFY THIS FILE!
########################################

info {
        created=1122536547
        version=2.0b3
        }

program {
        modified_host_attributes=0
        modified_service_attributes=0
        nagios_pid=3297
        daemon_mode=1
        program_start=1122531794
        last_command_check=1122536542
        last_log_rotation=1122534007
        enable_notifications=0
        active_service_checks_enabled=1
        passive_service_checks_enabled=1
        active_host_checks_enabled=1
        passive_host_checks_enabled=1
        enable_event_handlers=1
        obsess_over_services=1
        obsess_over_hosts=1
        check_service_freshness=0
        check_host_freshness=0
        enable_flap_detection=0
        enable_failure_prediction=1
        process_performance_data=0
        global_host_event_handler=
        global_service_event_handler=
        }

host {
        host_name=host1
        modified_attributes=0
        check_command=check-host-alive
        event_handler=
        has_been_checked=1
        should_be_scheduled=0
        check_execution_time=0.017
        check_latency=0.000
        current_state=0
        last_hard_state=0
        check_type=0
        plugin_output=PING OK - Packet loss = 0%, RTA = 0.19 ms
        performance_data=
        last_check=1122529374
        next_check=0
        current_attempt=1
        max_attempts=10
        state_type=1
        last_state_change=1122529364
        last_hard_state_change=1122529364
        last_time_up=1122529374
        last_time_down=0
        last_time_unreachable=0
        last_notification=0
        next_notification=0
        no_more_notifications=0
        current_notification_number=0
        notifications_enabled=0
        problem_has_been_acknowledged=0
        acknowledgement_type=0
        active_checks_enabled=1
        passive_checks_enabled=1
        event_handler_enabled=1
        flap_detection_enabled=1
        failure_prediction_enabled=1
        process_performance_data=1
        obsess_over_host=1
        last_update=1122536547
        is_flapping=0
        percent_state_change=0.00
        scheduled_downtime_depth=0
        }

host {
        host_name=host2
        modified_attributes=0
        check_command=check-host-alive
        event_handler=
        has_been_checked=1
        should_be_scheduled=0
        check_execution_time=0.017
        check_latency=0.000
        current_state=0
        last_hard_state=0
        check_type=0
        plugin_output=PING OK - Packet loss = 0%, RTA = 0.18 ms
        performance_data=
        last_check=1122529374
        next_check=0
        current_attempt=1
        max_attempts=10
        state_type=1
        last_state_change=1122529364
        last_hard_state_change=1122529364
        last_time_up=1122529374
        last_time_down=0
        last_time_unreachable=0
        last_notification=0
        next_notification=0
        no_more_notifications=0
        current_notification_number=0
        notifications_enabled=0
        problem_has_been_acknowledged=0
        acknowledgement_type=0
        active_checks_enabled=1
        passive_checks_enabled=1
        event_handler_enabled=1
        flap_detection_enabled=1
        failure_prediction_enabled=1
        process_performance_data=1
        obsess_over_host=1
        last_update=1122536547
        is_flapping=0
        percent_state_change=0.00
        scheduled_downtime_depth=0
        }

[...~2MB removed...]

$

So, essentially, those 2MB files are filling up my var directory at a
relatively rapid rate.  (As a side note, PING is not the only output in
the tmp files -- they contain the output from all of the checks.)

Thank you again for the advice, and any additional ideas are greatly
appreciated.




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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