[mrtg] Re: daemon robustness problem

[Tobias Oetiker]

Yesterday Greg.Volk at edwardjones.com wrote:

> Well, if it helps I have compressed and attached the bad (?)
> RRD file to this message as badrrd.zip. It appears to respond
> to some rrdtool commmands without error, but gives errors for
> others...

[...]

> rra[0].cf = "RRD"

> rra[1].cf = ""

> rra[2].cf = ""

> rra[3].cf = ""

> rra[4].cf = "MAX"

> rra[5].cf = "MAX"

> rra[6].cf = "MAX"

> rra[7].cf = "MAX"

> When I compare 'info' data to that of a healthy, working
> RRD file I see that the rra[n].cf values are usually "MAX"
> or "AVERAGE", but not "RRD."

> If that is the issue, then I suppose the real question is
> how did the rra[0].cf get set to RRD? Or maybe rra[n].cf
> doesn't have anything to do with the errors - I'm not very
> familiar with the actual RRD data structure to begin with.

it does ... but I have no idea how this could happen ... what is
makeing RRD and "" appear in the place of AVERAGE ... these files
can be fixed by dumping and then editing the text to AVERAGE

cheers
tobi
>
>
>
> Today oetiker at ee.ethz.ch wrote:
> >
> > I have heard this from other folks, but I am totally lost as to
> > what the reason for the strange state could be ...
> >
> >
> > >
> > > Every so often, I run into the following error...
> > >
> > > > mrtg switch-r-core1a.cfg
> > > Daemonizing MRTG ...
> > > > ERROR: Cannot update /home/mrtg/public_html/switch-r-core1a/switch-r-core1a_port-channel10.rrd with '1020433785:0:0' unknown consolidation function 'RRD'
> > >
> > > This causes the daemon to die, and all the targets in that particular
> > > config file go un-updated until I realize that this has happened. To
> > > fix it I end up deleting the RRD file that caused the error, delete
> > > the PID file that was left behind due to the daemon's death, and then
> > > relaunch the daemon.
> > >
> > > What causes this?
> > >
> > > Could it be bad hardware (disk?) errors on my system? The OS
> > > hasn't ever complained about any hardware problems, and the
> > > box has never crashed - it's at 168 days of uptime right now
> > > - so I don't think any dirty-shutdowns are to blame.
> > > Could I be looking at an RRDtool bug? I'm running v1.0.33. I
> > > looked at the changelog since 1.0.33 and didn't see anything
> > > mentioning this.
> > >
> > > Has anyone else run into this?
> > >
> > > Thanks
> > >
>
>
> -- Attached file removed by Listar and put at URL below --
> -- Type: application/octet-stream
> -- Size: 1k (1123 bytes)
> -- URL : http://www.ee.ethz.ch/~slist/pantomime/badrrd.zip
>
>
> --
> Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
> Archive     http://www.ee.ethz.ch/~slist/mrtg
> FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
> WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
>
>

-- 
 ______    __   _
/_  __/_  / /  (_) Oetiker, ETZ J97, ETH, 8092 Zurich, Switzerland
 / // _ \/ _ \/ / phoneto:+41(0)1-632-5286  faxto:+41(0)1-632-1517
/_/ \.__/_.__/_/ oetiker at ee.ethz.ch http://google.com/search?q=tobi

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi