Project

General

Profile

Bug #1399

rrdtool respawning too fast

Added by Chris Buechler over 8 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
RRD Graphs
Target version:
Start date:
03/30/2011
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

This has been showing up on a number of systems recently.

apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
rrdtool.core (3.64 MB) rrdtool.core rrdtool.core Todor K, 06/27/2013 07:57 AM

Associated revisions

Revision 3d54aa10 (diff)
Added by Renato Botelho almost 7 years ago

Avoid killing apinger's rrdtool processes on kill_traffic_collector(). It helps a problem reported on comment of ticket #1399

History

#1 Updated by Maxim Luppov over 8 years ago

Noticed this message in syslog long ago.

#2 Updated by Ermal Luçi over 8 years ago

This seems to be an assumption made from apinger that after an error occured you cannot respawn rrdtool faster than 300secoonds.
You just loose one round of update to the rrd's.

I would say close this.

#3 Updated by Chris Buechler over 8 years ago

  • Priority changed from Normal to Low
  • Target version deleted (2.0)

at a minimum should get rid of the log message at some point

#4 Updated by Chris Buechler over 7 years ago

  • Target version set to 2.1

#5 Updated by Julien Desrosiers about 7 years ago

Hi,

I'm using pfsense 2.0.1 on embedded (ALIX).

RRD Graphs no longer works.

System logs show :

Sep 29 20:35:00 kernel: pid 50109 (rrdtool), uid 0: exited on signal 11
Sep 29 20:35:00 kernel: pid 49309 (rrdtool), uid 0: exited on signal 11
Sep 29 20:34:59 kernel: pid 47834 (rrdtool), uid 0: exited on signal 11
Sep 29 20:34:58 kernel: pid 41099 (rrdtool), uid 0: exited on signal 11
Sep 29 20:34:58 kernel: pid 39929 (rrdtool), uid 0: exited on signal 11
Sep 29 20:34:58 kernel: pid 37763 (rrdtool), uid 0: exited on signal 11
Sep 29 20:34:58 kernel: pid 36378 (rrdtool), uid 0: exited on signal 11
Sep 29 20:34:58 kernel: pid 33996 (rrdtool), uid 0: exited on signal 11
Sep 29 20:34:58 kernel: pid 32139 (rrdtool), uid 0: exited on signal 11
Sep 29 20:34:58 kernel: pid 29865 (rrdtool), uid 0: exited on signal 11
Sep 29 20:34:58 kernel: pid 29120 (rrdtool), uid 0: exited on signal 11
Sep 29 20:34:25 apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.

What do you think?

#6 Updated by Chris Buechler about 7 years ago

post to the forum or mailing list, that doesn't have any relation to this.

#7 Updated by Seth Mos almost 7 years ago

I just had a epiphany, the enable_rrd_graphing() kills off any rrdtool process, including apinger'

Hence causing above message. I'll check in a fix with this ticket. We also need to solve the TMPFILE issue in updaterrd.sh in 2.0.[12] because that slowly fills /tmp with files and never cleans up.

In 2.1 we use a variable without tmp files, might be a good backport.

#8 Updated by Ermal Luçi almost 7 years ago

Its internal to apinger and a 'protection'.
I will double check again to see if it can be fixed.

#9 Updated by Florent THOMAS over 6 years ago

Hy,

I have the same message on a 2.0.3 release.
It seems to block my web UI.
Is there any reason to upgrade to 2.1 for solving this issue?

regards

#10 Updated by Todor K over 6 years ago

Same message appeared to me after upgrade from 2.0.3 to 2.1 p13
I have anohter server upgraded to 2.1 p8 (few days earlier) and the message does not appear there.

#11 Updated by Todor K over 6 years ago

Attaching rrdtool.core from 2.1 p13

#12 Updated by Ermal Luçi over 6 years ago

  • Status changed from New to Feedback

This should have been minimized now with the latest fixes in apinger.
Also there is no killing of apinger being done only reloading config and no kill of rrdtool by the rrd graph configuration which impacted this as well.

#13 Updated by Chris Buechler over 6 years ago

  • Target version changed from 2.1 to 2.2

doesn't seem to happen anymore, but will put it out to 2.2 for confirmation.

#14 Updated by Chris Buechler about 5 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF