Re: Internal error while talking to rrdcached

Thanks for the responses! In fact, the issue was resolved already on Friday
(response was posted in the Zenoss community thread
http://community.zenoss.org/thread/18663, but could not update this thread
until now):
The problem was indeed with the permissions: server had connections limited
by hosts file and following change was required in /etc/hosts.allow:

rrdcached: localhost


Now the data is collected correctly. Of course, one could try improving
rrdcache's error message in the future, albeit it seems all logical now.


Br,

Juha


On Mon, Nov 5, 2012 at 6:45 AM, Steve Shipway <[email protected]>wrote:

> Rrdcached is one of the parts of rrdtool that is rapidly developing.  It
> may be that the Zenoss application requires a more recent version in order
> to get additional options.****
>
> ** **
>
> However the error seems to indicate that your problem lies more at the
> filesystem end; possibly the rrdcached cannt read the required file due to
> ownerships, permissions, or simply process limits such as the max open file
> descriptors (to fix this latter, update the limits.conf and restart the
> rrdcached process).  My tentative guess at this point would be the ‘nofile’
> setting in limits.conf preventing the file from being opened.****
>
> ** **
>
> Steve****
>
> ** **
> ------------------------------
>
> *Steve Shipway***
>
> ITS Unix Services Design Lead****
>
> University of Auckland, New Zealand****
>
> Floor 1, 58 Symonds Street, Auckland****
>
> *Phone: +64 (0)9 3737599 ext 86487*
>
> *DDI: +64 (0)9 924 6487*
>
> *Mobile: +64 (0)21 753 189*
>
> *Email: [email protected]*
>
> P Please consider the environment before printing this e-mail ****
>
> ** **
>
> *From:* [email protected][mailto:
> [email protected]] *On
> Behalf Of *Juha Mustonen
> *Sent:* Friday, 2 November 2012 9:23 p.m.
> *To:* [email protected]
> *Subject:* [rrd-developers] Internal error while talking to rrdcached****
>
> ** **
>
> Hi,****
>
> ** **
>
> I'm getting following error from Zenoss monitoring setup, but the root
> cause is unclear. ****
>
> Possibly you could give some insight or tips where to look at? Already
> tried via Zenoss community forum (http://community.zenoss.org/thread/18663)
> but no luck there so far.****
>
> ** **
>
> [Error]****
>
> 2012-11-02 10:20:32,411 ERROR zen.ThresholdInstance: Unable to read RRD
> file for usedBlocks_usedBlocks****
>
> Traceback (most recent call last):****
>
>   File "/opt/zenoss/Products/ZenModel/ThresholdInstance.py", line 150, in
> checkRaw****
>
>     cycleTime, rrdType = self._getRRDType(dataPoint)****
>
>   File "/opt/zenoss/Products/ZenModel/ThresholdInstance.py", line 173, in
> _getRRDType****
>
>     data = rrdtool_fn()****
>
>   File "/opt/zenoss/Products/ZenUtils/Utils.py", line 1739, in _inner****
>
>     return fn(*args,**kwargs)****
>
>   File "/opt/zenoss/Products/ZenModel/ThresholdInstance.py", line 172, in
> rrdtool_fn****
>
>     return rrdtool.info(self.context().path(dp), *rrd_daemon_args())****
>
> error: request: internal error while talking to rrdcached****
>
> ** **
>
> [Process] ****
>
> zenoss   12303  0.0  0.0 114288  1156 ?        Ssl  10:06   0:00
> /usr/bin/rrdcached -b /opt/zenoss/perf -p /opt/zenoss/var/rrdcached.pid -l
> /opt/zenoss/var/rrdcached.sock -j /opt/zenoss/var/rrd_journals****
>
> ** **
>
> ** **
>
> Is there any (rrdcached?) command that I could run/tryout test whether the
> problem really is in rrdtool/rrdcached ?****
>
> ** **
>
> Br,
> Juha****
>



-- 
Juha

_______________________________________________
rrd-developers mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers