Nagiosgrapher problem with building graph for particular check_service

[yuris]

You are right, I've been changing definition couple of times, and since 
I have not been changing it for some some time (like 30 minutes) rrd 
file was updated on it's own and graph started to work!

So it seems like manual deleting of rrd file is not absolutely 
necessary, it's possible to just wait for some time and it will be 
updated automatically.

Thanks for the help!

--
best regards,
yuris


Marc Powell wrote:
> On Jul 9, 2010, at 7:51 AM, yuris wrote:
>
>   
>> And the problem is that graphs for Milter are not shown, Nagiosgrapher 
>> complains that "some error occured":
>>
>> RRD Error: No DS called 'sec' in 
>> '/var/lib/nagiosgrapher/rrd/<hostname>/457eb765jjf8905k0000567849c.rrd'
>>     
>
> It seems you may have been modifying the definition at least once. Try deleting the rrd file and allowing it to be recreated based on your current definition.
>
> --
> Marc
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> 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 Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
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