Wrong last check time on passive checks

[skridsko grafstrom]

Guess I fixed it myself with a cleanup of old records, and a restart. =)

> >>> skridsko 25/5/2007 07:29 >>>
>
> I run a distributed Nagios setup, but using my own scripts to collect
> the results from remote servers instead of NCSA. Results are submitted
> using the following format, as described in the manual:
>
> [<timestamp>] PROCESS_SERVICE_CHECK_RESULT;<host_name>;<description>;<return_code>;<plugin_output>
>
> Everything is fine except for the fact that the "last check" time is
> wrong on all the checks. I have checked the timestamps to ensure that
> they are in the correct format. In addition, the "last update" time
> reflects the correct timing though. What else might be wrong here?
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> 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
>
>

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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