Bug #1399
rrdtool respawning too fast
| Status: | New | Start date: | 03/30/2011 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | RRD Graphs | |||
| Target version: | 2.1 | |||
| 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.
Associated revisions
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 about 2 years ago
Noticed this message in syslog long ago.
#2
Updated by Ermal Luçi almost 2 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 almost 2 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 about 1 year ago
- Target version set to 2.1
#5
Updated by Julien Desrosiers 8 months 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 8 months ago
post to the forum or mailing list, that doesn't have any relation to this.
#7
Updated by Seth Mos 5 months 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 4 months ago
Its internal to apinger and a 'protection'.
I will double check again to see if it can be fixed.