WRT3200 - collected - RRDtool problem

Hi guys, I've been using collected together with RRD for a long time to get graphs and watch my router statistics. For some reason after the latest reset (manual reset after 23.05.0 update), RRDTool no longer works.

I've never touched any default settings after installation other than installing and configuring additional plugins. This time around the whole thing does not work. under setup, I see a message that No RRD data was found. I've tried several things including creating and setting appropriate folder permissions for RRD storage directory with zero success. Because I've never visited RRDTool Plugin configuration I don't know what I had in there. But as suggested somewhere I've tried to create /etc/rrd folder manually and set inclusive permission. If possible can someone tell me what I am missing and why RRDTool Plugin is not sending any data?

Thanks!

Please do not ever point/store Data to your flash.
The default config for rrd output plugin is /tmp/rrd that will disappear following a reboot.

Set up a usb storage drive and point it to the usb drive if you want to persist the data over time.

You can also use logread -e collectd after boot to see the plugins loaded, and anything unusual over the startup process.

1 Like

Thank you so much for your reply.

I'm not sure what has happened but I completely uninstalled everything just like I did previously. But this time I went to every single plug-in and without changing anything. I just applied and saved whatever it was in there. After reboot everything just worked, just like before, I haven't touched a single setting other than applying plug-in I want to use.

Problem is fixed but what was the problem? I'm still clueless.

Gremlins ? :melting_face:

In all seriousness, and only from my own anecdotal reference I always looked at the rrd db as problematic once it was set to persistence and any changes were applied after that setting took effect.

If I added a new plugin sometimes I would make small modifications to some parameters, or even find the plugin was not what I wanted and remove it. Every change would be reflected in the rrd db structure such that depending on different time spans, refresh periods, et al, Iā€™d see removed plugins appear, different processes showing/not showing, . . . Confusing at best.

We know that if the db was in /var a simple reboot would create a new db structure based on the current plugins/parameters last set and all is well with the world.

Bottom line, any time I need to add/modify/remove a collectd plugin I set the rrd plugin location back to /var first, and then only once satisfied I create a new persistent db ie. /mnt/data/rrd_x where x represents the current period db, while still retaining previous periods data.