I have no graphs for some services

[david.perez]

Deer Shinkers,

This is my setup:
- CentOS 6.4
- Shinken + PNP4Nagios + Thruk from OMD 1.10

I have 20 hosts with nearly the same services.
I've changed the name of 2 of them, and I have graph data for all the services belonging to these hosts in var/pnp4nagios/perfdata.

For the other hosts, many services don't have neither .rrd nor .xml file in var/pnp4nagios/perfdata/hostname
even though the command produces performance data. I don't understand why.

In my templates, I have defined an action_url for a service and for a host.

Any idea please?
Can I reset the state of pnp4nagios?
I've tried to remove the content of the var/pnp4nagios/perfdata folder with no success.

[naparuba]

Is the enable_perfdata parameter is on on theses services? Try to drop your retention data and restart shinken.

[david.perez]

Thanks Naparuba,

Yes process_perf_data = 1 in my service template.
How can I drop retention data?

[quote author=naparuba link=topic=1650.msg6802#msg6802 date=1393851804]
Is the enable_perfdata parameter is on on theses services? Try to drop your retention data and restart shinken.
[/quote]

[naparuba]

what is your retention module?

[david.perez]

$ cat shinken-specific.d/module_nagios_retention.cfg
define module{
module_name NagiosRetention
module_type nagios_retention_file
path /omd/sites/pro/var/nagios/retention.dat
}

#Now the good flat file retention module
define module{
module_name PickleRetention
module_type pickle_retention_file
path /omd/sites/pro/var/shinken/retention.dat
}

So, I'll try to delete /omd/sites/pro/var/shinken/retention.dat

After having read this, I've come to the conclusion that I use the pickle retention module.

[quote author=naparuba link=topic=1650.msg6807#msg6807 date=1393917693]
what is your retention module?
[/quote]

[david.perez]

It seems that deleting that file is magical. ;D
Now, a lot of new .rrd files are being created.
It would be worth to place this in the FAQ.
It's been hard to discover this.

[naparuba]

Not need, this was fixed in the incomming 2.0, this parameter won't be load from retention now