Reporting error message

Status
Not open for further replies.

adrianwi

Guru
Joined
Oct 15, 2013
Messages
1,231
Suddenly seeing lots of these flooding the console every 5 minutes:

Code:
Sep  5 09:35:57 freenas1 uwsgi: [reporting.rrd:163] Failed to generate graph: b'ERROR: bad CF: rx\n'
Sep  5 09:40:56 freenas1 uwsgi: [reporting.rrd:163] Failed to generate graph: b'ERROR: bad CF: rx\n'
Sep  5 09:40:56 freenas1 uwsgi: [reporting.rrd:163] Failed to generate graph: b'ERROR: bad CF: rx\n'
Sep  5 09:40:56 freenas1 uwsgi: [reporting.rrd:163] Failed to generate graph: b'ERROR: bad CF: rx\n'
Sep  5 09:40:57 freenas1 uwsgi: [reporting.rrd:163] Failed to generate graph: b'ERROR: bad CF: rx\n'
Sep  5 09:40:57 freenas1 uwsgi: [reporting.rrd:163] Failed to generate graph: b'ERROR: bad CF: rx\n'
Sep  5 09:40:57 freenas1 uwsgi: [reporting.rrd:163] Failed to generate graph: b'ERROR: bad CF: rx\n'
Sep  5 09:40:57 freenas1 uwsgi: [reporting.rrd:163] Failed to generate graph: b'ERROR: bad CF: rx\n'
Sep  5 09:40:57 freenas1 uwsgi: [reporting.rrd:163] Failed to generate graph: b'ERROR: bad CF: rx\n'
Sep  5 09:45:56 freenas1 uwsgi: [reporting.rrd:163] Failed to generate graph: b'ERROR: bad CF: rx\n'


Any ideas, and should I file a bug report?
 

adrianwi

Guru
Joined
Oct 15, 2013
Messages
1,231
No!

Took me a little whilst to get around to updating, but I'm still seeing the error, although not for quite as long. Seems to be generated from the Reporting > Network tab where some of the graphs are missing.

preview
 

adrianwi

Guru
Joined
Oct 15, 2013
Messages
1,231
Thanks!
 
Status
Not open for further replies.
Top