RRD graphing
-
Hello,
Thank you always databeestje, everything is back to as it supposed to be since your last post, Sun Nov 30 21:11:20 EST 2008 build. The CPU and Quality graph started drawing again correctly, and the Gateway also looks normal, no more 127.0.0.2 is shown, no annoying apinger logs in the system.log any more.
cheers,
-
That's good to hear.
Thank you for helping testing!
-
Hi,
today i look into my "System Log" and it show many errors every 5 Minutes these messages are repeated in the log:
apinger: Error while feeding rrdtool: Broken pipe apinger: rrdtool respawning too fast, waiting 300s.My quality graph is gone and this messages are shown since the automatic PPPOE restart which took place(as reported in the other topic this feature is still buggy). I hope i can help.
-
can you show me the output of a
ls -ld /var/db/rrd -
drwxr-xr-x 2 nobody nobody 512 Dec 1 10:22 /var/db/rrd -
make that ls -ld /var/db/rrd/Notice the trailing /
-
# ls -ld /var/db/rrd/ drwxr-xr-x 2 nobody nobody 512 Dec 1 10:22 /var/db/rrd/Same output… do you really are intrested in the directory permission or in the content of the directory itself (ls -al) ?
-
It was the directory permissions. But those look good. The directory permissions need to be owned by nobody because that is what apinger runs under.
You say this happens every pppoe restart, does that mean it works ok some times?
-
I can see WAN RRD graphs, wan is PPPoE.
This message in a log.
php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'inblock' in '/var/db/rrd/wan-traffic.rrd ….. -
Hi,
wondering if this is the case; http://forum.pfsense.org/index.php/topic,12890.0.html
cheers,