Fwd: undeterminate data in report

[Marc Powell]

This is fun. Let's always re-send our previous posts! =)

Begin forwarded message:

> From: Marc Powell <marc at ena.com>
> Date: October 10, 2008 11:40:52 AM CDT
> To: Nagios Users <nagios-users at lists.sourceforge.net>
> Subject: Re: [Nagios-users] undeterminate data in report
>
> Please always respond on list so that others, now and in the future,
> benefit from your experience.
>
> On Oct 10, 2008, at 10:27 AM, Benoit Barriere wrote:
>
>> I confirm that my sed command has done the job. If I check my
>> nagios-10-07-2008-00.log file
>>
>> All seems correct:
>>
>>
>> [1223244000] CURRENT SERVICE_STATE:
>> SRV_CS_HCC;PROCESS_cs_kernel.exe;OK;HARD;1;1 cs_kernel.exe Running
>> (Ram:24.79 MB) –
>> [1223244149] SERVICE_ALERT: SRV_CS_HCC;PROCESS_cs_kernel.exe;OK;HARD;
>> 1;1 cs_kernel.exe Running (Ram:24.81 MB) --
>>
>> I have a lot of service alerts before the Oct 7 : for example the
>> Oct 4 log file
>>
>> [1222985058] SERVICE_ALERT: SRV_CS_HCC;PROCESS_cs_kernel.exe;OK;HARD;
>> 1;1 cs_kernel.exe Running (Ram:38.82 MB) --
>>
>> Any ideas
>
> Did you change permissions on the files such that your web server
> can't read them any more? How about if you set the start date of your
> report to be Oct 3?
>
> What you've done shouldn't cause a problem. I do the same kind of
> thing for hostnames several times a month.
>
> --
> Marc


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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