Bug #2753: RRD Graphs failes after pfSense upgrade (2.0.1 -> 2.0.2) - pfSense - pfSense bugtracker

Actions

Copy link

Bug #2753

closed

RRD Graphs failes after pfSense upgrade (2.0.1 -> 2.0.2)

Added by Lasse Gurra over 12 years ago. Updated almost 11 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

RRD Graphs

Target version:

Start date:

01/11/2013

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.0.x

Affected Architecture:

i386

Description

After upgrading from 2.0.1-RELEASE to 2.0.2-RELEASE RRD Graph stopped working with the following error message in the System logs:

Jan 11 12:30:15 apinger: Error while feeding rrdtool: Broken pipe
Jan 11 12:30:11 php: /status_rrd_graph_settings.php: Creating rrd update script
Jan 11 12:30:11 php: /status_rrd_graph_settings.php: RRD create failed exited with 1, the error is: /libexec/ld-elf.so.1: /usr/local/lib/libpng.so.6: unsupported file layout

Actions

Copy link

Updated by Renato Botelho over 12 years ago

Project changed from pfSense Packages to pfSense
Category set to RRD Graphs

Actions

Copy link

Updated by Warm Noise over 12 years ago

Have been watching status on this issue for a couple months, since a similar scenario has applied to my setup as well.

Basically RRD data is still intact, but stopped collecting after the 2.0.2-RELEASE upgrade path. Did not see the libpng.so.6 lib error as above. However I finally used the "reset RRD data" from the web interface and RRD collection resumed. Here is the transcript when resetting the data:

system.log:Mar 28 20:53:38 php: /status_rrd_graph_settings.php: Creating rrd update script
system.log:Mar 28 20:54:15 apinger: Error while feeding rrdtool: Broken pipe
system.log:Mar 28 20:56:23 php: : Creating rrd update script
system.log:Mar 28 20:57:15 apinger: Error while feeding rrdtool: Broken pipe
system.log:Mar 28 20:58:15 apinger: rrdtool respawning too fast, waiting 300s.

Was there a binary format change that should have occurred during the upgrade?

Actions

Copy link

Updated by Florent THOMAS over 12 years ago

Hy,

I'm running on the pfsense 2.0.3 and since a reboot, my web UI is no more available.
I have exactly the same message in my logs. Could it be the reason of the blocking part?

regards

Actions

Copy link

Updated by Florent THOMAS over 12 years ago

Sorry,

Forgot my logs :

May 18 19:03:35 gateway apinger: Exiting on signal 15.                                                   
May 18 19:03:36 gateway apinger: Starting Alarm Pinger, apinger(3430)                                    
May 18 19:04:36 gateway apinger: Error while feeding rrdtool: Broken pipe                                
May 18 20:39:09 gateway apinger: Starting Alarm Pinger, apinger(33401)                                   
May 18 20:40:09 gateway apinger: Error while feeding rrdtool: Broken pipe                                
May 18 20:41:09 gateway apinger: rrdtool respawning too fast, waiting 300s.                              
May 19 02:21:12 gateway apinger: Error while feeding rrdtool: Broken pipe                                
May 19 02:32:46 gateway apinger: Starting Alarm Pinger, apinger(33373)                                   
May 19 02:33:46 gateway apinger: Error while feeding rrdtool: Broken pipe                                
May 19 02:34:46 gateway apinger: rrdtool respawning too fast, waiting 300s.

Actions

Copy link