2.3 Quality monitoring not working

cmb

If it pings from Diag>Ping with WAN chosen as the source, then the only difference between that and what dpinger is doing for gateway monitoring is the payload size. 1 is still considerably smaller than what typical ping utilities use. Granted I've yet to hear of anything having issues at a 1 byte payload, it was just no payload that triggers bugs in other things dropping valid traffic. Try setting the payload to 56, which is the default of ping. That makes it the same as what Diag>Ping does.

That IP doesn't ping at all from here, but maybe it does within your ISP's network.

dennypage

To match the default behavior of ping, you need to use a data payload of 56 bytes. When ping reports that it received 64 bytes, the ICMP header (8 bytes) is included in the count.

Apathia

Works just fine in Diag > Ping but still nothing in the quality graphs even with the increased payload.

My ISP has a total of 4 DNS servers (64.71.255.204, 64.71.255.198, 2607:f798:18:10:0:640:7125:5204, and 2607:f798:18:10:0:640:7125:5198) and I've tried using them all to no avail.

screencapture-10-10-10-1-diag_ping-php-1461699716368.png

dennypage

Can you share a screenshot of your gateway status page (Status / Gateways)?

And a screenshot of the config page for the gateway (System / Routing / Gateways / Edit)?

Apathia

Yep.

screencapture-10-10-10-1-status_gateways-php-1461710588853.png

screencapture-10-10-10-1-system_gateways_edit-php-1461710610636.png

cmb

Thanks for the correction, Denny.

So that screenshot of the status screen confirms it's working fine. What does a screenshot of the graph look like?

Apathia

This

screencapture-10-10-10-1-status_monitoring-php-1461711282614.png

cmb

Are all your other monitoring graphs fine? Any gateway names in the Graphs drop down other than those two? Seem to match up to the status page.

Apathia

Everything else works fine (except for Queues/Queuedrops but I don't have any traffic shaping so it's not broken). Nothing else in the drop down menu.

cmb

Could you send me copies of your /var/db/rrd/WAN_DHCP-quality.rrd and WAN_DHCP6-quality.rrd files? Can download them under Diag>Command, or via scp.

Apathia

I also reboot the system to see if it had any effect. It did not :(

cmb

Thanks, you can remove those now if you'd like. Files are sane, but their contents stop on April 12.

Try moving those two files to a different filename, and reboot afterwards. Give it 5 minutes post-reboot to gather data. Does it work then?

Apathia

Omg, I think that actually fixed it. It seems to actually be recording it now.

Between 2.2 and 2.3, are there differences in how it records the info? The reason why the logs stop is because I updated while trying to keep the RRD data.

cmb

Glad that worked. Maybe the conversion on upgrade failed on your system. That RRD file is updated during upgrade since it had standard deviation now as well. Did you have any rrdtool logs in your system log?

Apathia

What's weird is I first upgraded the system and then followed it up with a fresh install after a few days of it not working. When I did the fresh install, I didn't import anything and just set up the basic things and still no go for the quality monitor. I did eventually end up importing my old config to get a few other things back to what I had.

As far as anything in the system logs, well I'll have to check later when I have access to it.
EDIT: Nothing in the logs as far as I can see, anything specific I can search for or just rrdtool?

cmb

@Apathia:

What's weird is I first upgraded the system and then followed it up with a fresh install after a few days of it not working. When I did the fresh install, I didn't import anything and just set up the basic things and still no go for the quality monitor. I did eventually end up importing my old config to get a few other things back to what I had.

huh, yeah that's odd. The reinstall would have started with fresh rrd data files as long as the config you restored didn't include RRD data. So it shouldn't have happened in that case. Sure you didn't have RRD data in the restored config maybe?

@Apathia:

As far as anything in the system logs, well I'll have to check later when I have access to it.
EDIT: Nothing in the logs as far as I can see, anything specific I can search for or just rrdtool?

Just rrdtool would suffice. 'clog /var/log/system.log | grep rrdtool'

Apathia

@cmb:

@Apathia:

What's weird is I first upgraded the system and then followed it up with a fresh install after a few days of it not working. When I did the fresh install, I didn't import anything and just set up the basic things and still no go for the quality monitor. I did eventually end up importing my old config to get a few other things back to what I had.

huh, yeah that's odd. The reinstall would have started with fresh rrd data files as long as the config you restored didn't include RRD data. So it shouldn't have happened in that case. Sure you didn't have RRD data in the restored config maybe?

@Apathia:

As far as anything in the system logs, well I'll have to check later when I have access to it.
EDIT: Nothing in the logs as far as I can see, anything specific I can search for or just rrdtool?

Just rrdtool would suffice. 'clog /var/log/system.log | grep rrdtool'

No results when searching for rrdtool.

I did have the data in my old config, but I didn't restore it right away. After the upgrade I backed it up then did a factory reset but that still didn't work so I did a fresh install. After waiting a day or two with it still not working, I did finally restore it to get the misc settings that I hadn't bothered to go through initially.