RRD graphing

sullrich · Nov 17, 2008, 6:46 PM

Fixed, thanks

nocer · Nov 19, 2008, 12:22 AM

Hello,

Hmm…doesn't seems to be fixed. Still have cpu graph issue, and quality graph back to ALL RED. Still getting

Nov 19 08:51:08 apinger: ALARM: wan(127.0.0.2) *** down ***

for the gateway 127.0.0.2 which I have never ever configured.

cheers,

EDIT: 2.0-ALPHA-ALPHA built on Tue Nov 18 17:47:36 EST 2008 FreeBSD 7.1-PRERELEASE

mino · Nov 19, 2008, 10:05 PM

With the latest snapshort RRD is again working but all Gateway Displays say "offline". And CPU Graph is still not working (like before).

databeestje · Nov 21, 2008, 10:27 PM

127.0.0.2 is for interfaces which are dynamic and down. Atleast that's what they should be.

What is you wan? The gateway code is untested with pppoe or pptp. So I can't really tell.

dump the output from the php command

print_r(return_gateways_array());

and

print_r(return_gateways_status());

Thanks.

nocer · Nov 26, 2008, 6:13 AM

Hi,

Just loaded the latest 2.0-ALPHA-ALPHA built on Tue Nov 25 14:59:09 EST 2008 and still no CPU graph, also found the following while re-creating entire RRD graph;

Nov 26 14:56:32 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'
Nov 26 14:56:32 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'
Nov 26 14:56:32 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'
Nov 26 14:56:31 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'
Nov 26 14:56:31 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'
Nov 26 14:56:31 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'
Nov 26 14:56:31 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'

And,

dump the output from the php command

print_r(return_gateways_array());

and

print_r(return_gateways_status());

gives me nothing ; My WAN is PPPoE.

pfSense console setup

0) Logout (SSH only)
1) Assign Interfaces
2) Set interface(s) IP address
3) Reset webConfigurator password
4) Reset to factory defaults
5) Reboot system
6) Halt system
7) Ping host
8) Shell
9) PFtop
10) Filter Logs
11) Restart webConfigurator
12) pfSense PHP shell
13) Upgrade from console
14) Disable Secure Shell (sshd)

Enter an option: 12

Starting the pfSense shell system…...........

Welcome to the pfSense php shell system
Written by Scott Ullrich (sullrich@gmail.com)

Type "help" to show common usage scenarios.

Available playback commands:
cvssync disabledhcpd enableallowallwan removepkgconfig restartdhcpd restartftphelper restartipsec

pfSense shell: print_r(return_gateways_array());
pfSense shell:
pfSense shell: print_r(return_gateways_status());
pfSense shell:
pfSense shell:

cheers,

sullrich · Nov 26, 2008, 7:11 PM

You need:

exec

After the command..

pfSense shell: print_r(return_gateways_array());
pfSense shell: exec

nocer · Nov 26, 2008, 8:24 PM

Thanks sullrich,

@sullrich:

You need:

exec

After the command..

pfSense shell: print_r(return_gateways_array());
pfSense shell: exec

pfSense shell: print_r(return_gateways_array());
pfSense shell: exec
Array
(
[0] => Array
(
[gateway] => 127.0.0.2
[interface] => wan
[monitor] => 127.0.0.2
[name] => wan
[descr] => Interface WAN Gateway
[attribute] => system
)

[1] => Array
(
[gateway] => 210.xxx.xxx.5
[interface] => wan
[monitor] => 210.xxx.xxx.5
[name] => wan
[descr] => Interface WAN Gateway
[attribute] => system
)

)
pfSense shell: print_r(return_gateways_status());
pfSense shell: exec
Array
(
[127.0.0.2] => Array
(
[monitor] => 127.0.0.2
[gateway] => 127.0.0.2
[interface] => wan
[name] => wan
[lastcheck] => #0 Thu Jan 1 09:00:00 1970
[delay] => 0.000ms
[loss] => 100.0%
[status] => "down"
)

[210.xxx.xxx.5] => Array
(
[monitor] => 210.xxx.xxx.5
[gateway] => 210.xxx.xxx.5
[interface] => wan
[name] => wan
[lastcheck] => #51640 Thu Nov 27 05:18:06 2008
[delay] => 4.051ms
[loss] => 0.0%
[status] => None
)

)
pfSense shell:

cheers,

Accounts · Nov 27, 2008, 8:59 AM

My cpu seems to have stoped charting, is this related to this topic?

nocer · Nov 27, 2008, 9:10 AM

@Accounts:

My cpu seems to have stoped charting, is this related to this topic?

yup, and "Quality" graph too :'(

databeestje · Nov 28, 2008, 10:35 PM

the quality graphs have been changed over to a new format because we use the apinger files.

This means removing the /var/db/rrd/*-quality.rrd files. And then reboot.

The processor graph should have been fixed. This was a off by one.

The wan being show down is definitely a issue with pppoe and pptp interfaces. This will need some time on my part. Not having a pppoe or pptp setup makes it that more time consuming.

databeestje · Nov 28, 2008, 11:54 PM

does

echo " gateway '". get_interface_gateway("wan") ."' found\n";

on the command page produce output on your pppoe install?

databeestje · Nov 29, 2008, 12:15 AM

I have added a debug statement that should log this to the system logs.

Please check a new snapshot and see if you see any found dynamic gateway x.x.x.x in the system logs and paste the output here.

nocer · Nov 29, 2008, 1:36 AM

Hello databeestje, thanks for follow ups;

@databeestje:

does
echo " gateway '". get_interface_gateway("wan") ."' found\n";
on the command page produce output on your pppoe install?

yup, it correctly looks my gateway; "gateway '210.xxx.xxx.5' found" is the output. Which is my real WAN IP obtained by PPPoE from ISP.

@databeestje:

Please check a new snapshot and see if you see any found dynamic gateway x.x.x.x in the system logs and paste the output here.

Well, it looks there's no snaps since 25th…snap server seems to be taking a nap now.

cheers,

2.0-ALPHA-ALPHA
built on Tue Nov 25 14:59:09 EST 2008
FreeBSD 7.1-PRERELEASE

nocer · Nov 29, 2008, 5:26 AM

Hi,

@databeestje:

I have added a debug statement that should log this to the system logs.

Please check a new snapshot and see if you see any found dynamic gateway x.x.x.x in the system logs and paste the output here.

Surely found "PHP: found dynamic gateway 210.xxx.xxx.130" in the system log.

BTW, still no luck with CPU graph. Quality graph is back but dead red.

cheers,

2.0-ALPHA-ALPHA
built on Fri Nov 28 22:55:11 EST 2008
FreeBSD 7.1-PRERELEASE

mino · Nov 29, 2008, 8:52 AM

php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'delay' in '/var/db/rrd/wan-quality.rrd'

And the quality graphs are only showing a error that you need to look in the logs.

databeestje · Nov 29, 2008, 9:25 AM

mino, please remove the quality rrd files and let them be recreated. The format has changed.

databeestje · Nov 29, 2008, 9:30 AM

nocer, I will have to look into it further. It is not obvious to me what causes this yet. The debug statement did help though. Now I know it is triggering the right path.

That the quality graph is red is correct since it pings 127.0.0.2 which is a dummy address which is normally used when it can't find the gateway for a dynamic interface. That one always times out :-)

I'll have another look at the cpu graph then.
Is this a single or dual core box?

nocer · Nov 29, 2008, 10:28 AM

Thank you always databeestje :)

I'm running Atom230@1.60GHz, a single core but HT capable with SMP kernel. As for the quality graph, it used to ping my gateway correctly and created right graph, and I of course deleted 127.0.0.2 from the apinger.conf and restarted the process(not a reboot) so there's nothing apinger to do with 127.0.0.2.

cheers,

databeestje · Nov 29, 2008, 12:20 PM

If the gateway IP comes through normally in the code it will automatically configure apinger to ping the right gateway.

I'll add more debugging and see if I can work out what is happening.

databeestje · Nov 29, 2008, 11:29 PM

I think I may have solved it, the debugging statements are all there but it took a while to set up a testing rig.

Please test another snapshot.