RRD Graphs

marrandy

I went from beta 1 to beta 4 build 04/08/10 and that has broken the RRD graphs apart from from the quality one. I did delete all the rrd files then switch RRD off then back up, I saw it recreate the files but still didn't log anything. Is there anything else I can try to get it to work.

Wait…it took several minutes before I saw anything.

Jonb

Still no joys for me.

jimp

I fixed an issue with drawing of quality graphs on fresh installs and NanoBSD earlier today. It was too late for the next snapshot, but the one after should be OK.

Jonb

Jim any ideas on the traffic graphs etc in my instance. Just to let you know when I deleted the rrd files and recreated them I then did a restore of the old rrd graphs.

jimp

Not that I know of, I haven't seen any problems with the other graphs, just the quality graph.

It may not be drawing the data in the graph where you expect though, the graphs start on hard boundaries now and if you catch them early in the day most of the current graph will be empty.

Jonb

Is there a command I can use or anything I can do to see if they system is actually recording the data.

jimp

Just look at:

ls /var/db/rrd/

If the timestamps are current, the files are being touched.

Jonb

-rw-r–r-- 1 root wheel 47608 Aug 5 19:51 GW_WAN-quality.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 19:52 ipsec-packets.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 19:52 ipsec-traffic.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 19:52 lan-packets.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 19:52 lan-traffic.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 19:52 opt1-packets.rrd
-rw-r--r-- 1 root wheel 65672 Aug 5 10:16 opt1-quality.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 19:52 opt1-traffic.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 10:16 opt2-packets.rrd
-rw-r--r-- 1 root wheel 65672 Aug 5 10:16 opt2-quality.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 10:16 opt2-traffic.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 19:52 ovpns1-packets.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 19:52 ovpns1-traffic.rrd
-rw-r--r-- 1 root wheel 49120 Aug 5 19:51 ovpns1-vpnusers.rrd
-rw-r--r-- 1 root wheel 97672 Aug 5 10:16 ppp-cellular.rrd
-rw-r--r-- 1 root wheel 727424 Aug 5 19:51 system-memory.rrd
-rw-r--r-- 1 root wheel 487424 Aug 5 19:51 system-processor.rrd
-rw-r--r-- 1 root wheel 487424 Aug 5 19:51 system-states.rrd
-rw-r--r-- 1 root wheel 4974 Aug 5 19:13 updaterrd.sh
-rw-r--r-- 1 root wheel 194776 Aug 5 19:52 wan-packets.rrd
-rw-r--r-- 1 root wheel 65672 Aug 5 10:16 wan-quality.rrd
-rw-r--r-- 1 root wheel 388984 Aug 5 10:16 wan-queuedrops.rrd
-rw-r--r-- 1 root wheel 388984 Aug 5 10:16 wan-queues.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 19:52 wan-traffic.rrd

Strange as the wan-quality is the one that works

jimp

It's also one being updated: 19:51 GW_WAN-quality.rrd

:-)

Jonb

So is this a graph drawing issue.

Jonb

Strange what is going on.

sizes are the same as well

-rw-r–r-- 1 root wheel 47608 Aug 5 20:20 GW_WAN-quality.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 20:21 ipsec-packets.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 20:21 ipsec-traffic.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 20:21 lan-packets.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 20:21 lan-traffic.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 20:21 opt1-packets.rrd
-rw-r--r-- 1 root wheel 65672 Aug 5 10:16 opt1-quality.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 20:21 opt1-traffic.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 10:16 opt2-packets.rrd
-rw-r--r-- 1 root wheel 65672 Aug 5 10:16 opt2-quality.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 10:16 opt2-traffic.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 20:21 ovpns1-packets.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 20:21 ovpns1-traffic.rrd
-rw-r--r-- 1 root wheel 49120 Aug 5 20:20 ovpns1-vpnusers.rrd
-rw-r--r-- 1 root wheel 97672 Aug 5 10:16 ppp-cellular.rrd
-rw-r--r-- 1 root wheel 727424 Aug 5 20:20 system-memory.rrd
-rw-r--r-- 1 root wheel 487424 Aug 5 20:20 system-processor.rrd
-rw-r--r-- 1 root wheel 487424 Aug 5 20:20 system-states.rrd
-rw-r--r-- 1 root wheel 5780 Aug 5 20:07 updaterrd.sh
-rw-r--r-- 1 root wheel 194776 Aug 5 20:21 wan-packets.rrd
-rw-r--r-- 1 root wheel 65672 Aug 5 10:16 wan-quality.rrd
-rw-r--r-- 1 root wheel 340432 Aug 5 20:16 wan-queuedrops.rrd
-rw-r--r-- 1 root wheel 340432 Aug 5 20:16 wan-queues.rrd
-rw-r--r-- 1 root wheel 194776 Aug 5 20:21 wan-traffic.rrd

status_rrd_graph_img.php.png
status_rrd_graph_img.php.png_thumb

dszp

RRD files are round-robin database files (hence RRD) which remain a consistent size as they store rotating (round-robin) data. So if they will maintain history for a year, they start big enough to hold a year's worth of data and never grow or shrink, they are just updated with new data at the proper place. Hence the same file sizes.

cmb

Jim fixed a permissions issue today that should fix the quality graphs.
https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/3d83f02e958a52e35cf098a3cd3f7031f53d69a0

though that only applies when the directory is created. May need something to fix permissions on existing directories. To manually fix, run:

chown nobody:wheel /var/db/rrd/*quality*.rrd

Jonb

Ok fair enough so the files size shouldn't change. So how would I delve into the problem more to see if it is a graphing issue or data issue.

jimp

@cmb:

Jim fixed a permissions issue today that should fix the quality graphs.
https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/3d83f02e958a52e35cf098a3cd3f7031f53d69a0

though that only applies when the directory is created. May need something to fix permissions on existing directories. To manually fix, run:
chown nobody:wheel /var/db/rrd/*quality*.rrd

In addition to that, you want to change the permissions on the directory itself:

chown nobody:wheel /var/db/rrd/

Or combine the two:

chown -R nobody:wheel /var/db/rrd/

marrandy

@jimp:

Or combine the two:
chown -R nobody:wheel /var/db/rrd/

2.0-BETA4
built on Fri Aug 6 01:44:17 EDT 2010
FreeBSD 8.1-RELEASE

Tried that and even rebooted - Quality still isn't working.

jimp

That will be a no-op on NanoBSD if you reboot after doing it. /var is a RAM disk. You'd need to be on the latest snapshot (I think it should have the fix) before that will work.

marrandy

@jimp:

That will be a no-op on NanoBSD if you reboot after doing it. /var is a RAM disk. You'd need to be on the latest snapshot (I think it should have the fix) before that will work.

That is the latest snapshot.

I only rebooted as its still blank.

jimp

I found another bug, but it's definitely fixed now. :-)

Either apply this by hand, or wait for the next new snapshot:
https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/21934843352aa1dee730f59b06d35f1619c0ab3e

marrandy

I'll wait for the next update.

I'm just testing and providing feedback.

Thanks !!!