NEW Monitoring graph

jahonix

…(after the auto update is included)...

Will auto update reset the selected graphs as well?
(where is the selection done - probably directly in the browser, right?)

whitexp

@cmb:

@whitexp:

PHP Errors:
[10-Mar-2016 15:07:02 America/Sao_Paulo] PHP Fatal error: Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 125

That means you don't have pecl-rrd, which has been a dependency since this was in place. What do you see for 'pkg info|grep pecl-rrd'? Should look something like:
[2.3-BETA][root@fw1]/root: pkg info|grep pecl-rrd
pecl-rrd-1.1.3_2               PHP bindings to rrd tool system

[2.3-BETA][admin@white.localdomain]/root: pkg info|grep pecl-rrd
pecl-rrd-1.1.3_2 PHP bindings to rrd tool system
[2.3-BETA][admin@white.localdomain]/root:

Crash report details:

PHP Errors:
[17-Mar-2016 09:41:09 America/Sao_Paulo] PHP Fatal error:  Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 128
[17-Mar-2016 09:41:19 America/Sao_Paulo] PHP Fatal error:  Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 128
[17-Mar-2016 09:45:56 America/Sao_Paulo] PHP Fatal error:  Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 128
[17-Mar-2016 09:46:17 America/Sao_Paulo] PHP Fatal error:  Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 128

Filename: /var/crash/minfree
2048

i still have the problem …

Interactive Graph
Error: SyntaxError: Unexpected token F

NOYB

@jahonix:

@jdillard:

…(after the auto update is included)...

Will auto update reset the selected graphs as well?
(where is the selection done - probably directly in the browser, right?)

If you mean will hidden series be restored, yes. It is no different than manually hitting the refresh button. It's just done for you at the selected a interval.

Well there is at least one difference. The loading graph banner isn't displayed.

MikeV7896

So I haven't looked at the monitoring graph since I updated last night (and I'm not at home to look now)… has the last sample being 0 been fixed on the graphs yet? A couple of days ago I noticed that all lines still returned to 0 on the right side of the graph.

NOYB

@virgiliomi:

So I haven't looked at the monitoring graph since I updated last night (and I'm not at home to look now)… has the last sample being 0 been fixed on the graphs yet? A couple of days ago I noticed that all lines still returned to 0 on the right side of the graph.

No.

Odds of having an RRD data point for the graph end time can be greatly increased though by updating/refreshing the graph near the end of the minute. Say like at hh:mm:59.

I committed a hack to the auto update pull request that syncs the refreshes to seconds 59 and it seems to work pretty well to prevent the graph from ending with values of zero (0). Once in a while it will if the RRD is updated between mm:59 and mm+1:00. Or the sync drifts off a bit and hits mm:00 once in a while.

But I think the real way to fix it is to use the most recent RRD data point time as the graph end time. And set graph start time to graph end time minus time period. Think something like that is how it works in previous version.

NOYB

@peter808:

… option for multiple, adjustable graphs on the monitoring page ...

Though not multiple graphs, the quick links would make it real easy one click access to the same graphs you'd set up in your multiple graphs monitoring page. They just wouldn't be on the page at the same time. Unless you open multiple browsers or load them into a page with iframes. Think you could probably create an page that loads the monitoring page into multiple iframes. And if loaded with the correct post to select the quick link each iframe could auto load the desired graph.

MikeV7896

So I updated to the latest snapshot last night, then again this morning… and now every time I visit the monitoring graph, I get this error:

Error: SyntaxError: Unexpected token F

The graph itself doesn't display, and no matter what I change the settings to, I can't shake that error.

Edit: Likely related… a crash report appeared when I went back to the dashboard, with the error...

[19-Mar-2016 08:40:26 America/New_York] PHP Fatal error: Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 128

whitexp

@virgiliomi:

So I updated to the latest snapshot last night, then again this morning… and now every time I visit the monitoring graph, I get this error:

Error: SyntaxError: Unexpected token F

The graph itself doesn't display, and no matter what I change the settings to, I can't shake that error.

Edit: Likely related… a crash report appeared when I went back to the dashboard, with the error...

[19-Mar-2016 08:40:26 America/New_York] PHP Fatal error: Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 128

i have this problem about 1 week

MikeV7896

Just thought I'd note… I updated tonight to the latest snapshot, which I saw included an updated status monitoring package, and the "SyntaxError: Unexpected token F" message still occurs. I just now submitted another crash report, in case it's needed...

maverick_slo

Hmm this doesn`2t look right.
I intentionally selected IPsec iface as in last 8 hours there was 0 traffic.
Green line seems to be left over from quality graph.
I checked with multiple browsers, same behaviour.

monitoring.PNG_thumb

abu_cwarky

@virgiliomi:

Just thought I'd note… I updated tonight to the latest snapshot, which I saw included an updated status monitoring package, and the "SyntaxError: Unexpected token F" message still occurs. I just now submitted another crash report, in case it's needed...

This happened to me also. Although i couldn't find why, this is cause by /usr/local/etc/php/extensions.ini being empty. This is the content of the file where graph is workng :

extension=bcmath.so
extension=bz2.so
extension=ctype.so
extension=curl.so
extension=dom.so
extension=filter.so
extension=gettext.so
extension=hash.so
extension=json.so
extension=ldap.so
extension=mbstring.so
extension=mcrypt.so
extension=openssl.so
extension=pcntl.so
extension=pdo.so
extension=pdo_sqlite.so
extension=pfSense.so
extension=posix.so
extension=radius.so
extension=readline.so
extension=rrd.so
extension=session.so
extension=shmop.so
extension=simplexml.so
extension=sockets.so
extension=sqlite3.so
extension=ssh2.so
extension=suhosin.so
extension=sysvmsg.so
extension=sysvsem.so
extension=sysvshm.so
extension=tokenizer.so
extension=xml.so
extension=xmlreader.so
extension=xmlwriter.so
extension=zlib.so
extension=zmq.so
zend_extension=/usr/local/lib/php/20131226/opcache.so
zend_extension=/usr/local/lib/php/20131226/xdebug.so

I just edited the file with the above lines and this solved the problem. If you want you can give it a try.

whitexp

@abu_cwarky:

@virgiliomi:

Just thought I'd note… I updated tonight to the latest snapshot, which I saw included an updated status monitoring package, and the "SyntaxError: Unexpected token F" message still occurs. I just now submitted another crash report, in case it's needed...

This happened to me also. Although i couldn't find why, this is cause by /usr/local/etc/php/extensions.ini being empty. This is the content of the file where graph is workng :
extension=bcmath.so
extension=bz2.so
extension=ctype.so
extension=curl.so
extension=dom.so
extension=filter.so
extension=gettext.so
extension=hash.so
extension=json.so
extension=ldap.so
extension=mbstring.so
extension=mcrypt.so
extension=openssl.so
extension=pcntl.so
extension=pdo.so
extension=pdo_sqlite.so
extension=pfSense.so
extension=posix.so
extension=radius.so
extension=readline.so
extension=rrd.so
extension=session.so
extension=shmop.so
extension=simplexml.so
extension=sockets.so
extension=sqlite3.so
extension=ssh2.so
extension=suhosin.so
extension=sysvmsg.so
extension=sysvsem.so
extension=sysvshm.so
extension=tokenizer.so
extension=xml.so
extension=xmlreader.so
extension=xmlwriter.so
extension=zlib.so
extension=zmq.so
zend_extension=/usr/local/lib/php/20131226/opcache.so
zend_extension=/usr/local/lib/php/20131226/xdebug.so
I just edited the file with the above lines and this solved the problem. If you want you can give it a try.

it solve the problem .. thanks

I believe the devs need to find out coz this file becomes empty after a few updates.

jdillard

@whitexp:

it solve the problem .. thanks

I believe the devs need to find out coz this file becomes empty after a few updates.

I'll bring this to garga's attention and get back to you. Thanks for looking into it!

edit: Garga says he pushed a change that should fix it, but try running the following instead of editing:

sort -u -o /usr/local/etc/php/extensions.ini /usr/local/etc/php/extensions.ini

jdillard

@maverick_slo:

Hmm this doesn`2t look right.
I intentionally selected IPsec iface as in last 8 hours there was 0 traffic.
Green line seems to be left over from quality graph.
I checked with multiple browsers, same behaviour.

Did you have a graph selected before going back to none on the right axis? I haven't figured out a fix for that yet…

maverick_slo

Yup, thats the case.
Default I have 2 wans quality then I change to traffic and remove right axis…

jdillard

@maverick_slo:

Yup, thats the case.
Default I have 2 wans quality then I change to traffic and remove right axis…

I just changed it to draw the graphs from scratch every time and it fixed this issue (and also got rid of a bunch of duplicate code). Everything should behave the same, but you may want to double check everything.

MikeV7896

@jdillard:

…but try running the following instead of editing:
sort -u -o /usr/local/etc/php/extensions.ini /usr/local/etc/php/extensions.ini

Yeah, there's nothing to sort in an empty file… :)

Unless one of those filenames should be something else? :)

Edit: Or, unless you were referring to sorting AFTER updating? Couldn't tell...

jdillard

I somehow missed the empty part of the post :-[

Let me get back with Garga, he set up that part.

NOYB

@jdillard:

@maverick_slo:

Yup, thats the case.
Default I have 2 wans quality then I change to traffic and remove right axis…

I just changed it to draw the graphs from scratch every time and it fixed this issue (and also got rid of a bunch of duplicate code). Everything should behave the same, but you may want to double check everything.

Would be nice if the draw_graph function had an option to "redraw" instead. Seems that draw from scratch should only be needed if the graph options have changed. That way updating same graph would be smoother, and probably more efficient too.

jdillard

I might have to redo that for after 2.3 and can include the auto-update and multi-option stuff you worked on at that point.

There has got to be a better way that reuses more of the code…