[rrd-users] rrdcached absolute vs relative paths

[Steve Shipway]

> $ /usr/local/bin/rrdcached -l unix:/tmp/rrdcached.sock -w 43200 -z 43200 -t 8
> -f 86400 \
> 	-l 172.25.7.4 -b /usr/local/var/rrd -j /usr/local/var/rrd/journal -p
> /tmp/rrdcached.pid
...

> $ rrdtool last --daemon 172.25.7.4 10.128.5.238/snmp/octets-23.rrd
> -1
> ERROR: opening '10.128.5.238/snmp/octets-23.rrd': No such file or directory

You should try to make the -l listener options come last; some of the options to rrdcached (eg, -b) can only affect SUBSEQUENT listeners (this may seem odd but it allows you to specify different levels of access to different listeners).  Also, the TCP listener doesn’t allow absolute paths for obvious security reasons, so paths are relative to the -b base directory.  Try this order, and things should work:

$ /usr/local/bin/rrdcached -w 43200 -z 43200 -t 8 -f 86400 -p /tmp/rrdcached.pid \
	-b /usr/local/var/rrd -j /usr/local/var/rrd/journal \
	-l 172.25.7.4 -l unix:/tmp/rrdcached.sock

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: s.shipway at auckland.ac.nz
 Please consider the environment before printing this e-mail 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4928 bytes
Desc: not available
Url : http://lists.oetiker.ch/pipermail/rrd-users/attachments/20110620/403d34f4/attachment.bin