Hi everyone,
A while ago, following the instructions in a forum post, I modified the /etc/collectd.conf file to create a response time graph.
It worked well enough for a while, but then it stopped working. Checking the file, I noticed that the customizations I had added were no longer present.
I tried re-added them, but the graph still doesn’t generate.
Do you know what might have changed and how I can recreate the same graph?
Thanks in advance for your help!
CU203 had a correction patch applied for the building of collectd and this then required the collectd files to be shipped, including the default collectd.conf file.
If you look through the collectd.conf file you will see that the last line in it is
include "/etc/collectd.d/*"
which allows you to create custom plugins, place them in that directory and they will be included into the collectd.conf file.
That might be better than modifying collectd.conf itself which will be overwritten any time an update of some sort is applied to collectd.
Note that collectd will be replaced by telemetryd
https://www.ipfire.org/docs/roadmap/telemetry
First of all, thank you for your reply.
I applied the change you recommended. I moved my configuration to the collectd.custom file, but something probably isn’t working because it stopped working.
collectd.custom seems to have a problem with adding the two ping items from the above post.
Starting Collection daemon...
Parse error in file `/etc/collectd.d/collectd.custom', line 187 near `': syntax error, unexpected $end, expecting EOL
yyparse returned error #1
configfile: Cannot read file `/etc/collectd.d/collectd.custom'.
Unable to read config file /etc/collectd.conf.
Error: Parsing the config file failed!
collectd.custom:
# Use this file to add custom configs and rules for collectd
<Plugin ping>
Host "ipfire.org"
interval 30
timeout 10
</Plugin>
<Plugin ping>
Host "8.8.8.8"
interval 30
timeout 10
</Plugin>
putting those in the collectd.conf works just fine so i not sure exactly what the issue is
Sorry for the delay in my reply; yes, I made the same mistake too—I had forgotten that a blank line was required.
To be exactly: The line must be terminated by an EOL. 
I remember those ‘special’ parser behaviour from long ago with simple compilers. I don’t the EOL is part of the syntax.
