Bug#890286: rrdcached: "gmetad RRD_update [...] rrdcached: Permission denied" if limited socket specified first

2018-02-14 Thread Chad William Seys
Hi Jean-Michel, I'm as sure as anything in this life that there was no other rrdcached using the socket. :) Thanks for your work! Chad. On 02/14/2018 02:46 AM, Jean-Michel Vourgère wrote: > Hi Chad > > Thank you for your detailed report. > > Before I dig more into it, can you double check

Bug#890286: rrdcached: "gmetad RRD_update [...] rrdcached: Permission denied" if limited socket specified first

2018-02-14 Thread Jean-Michel Vourgère
Hi Chad Thank you for your detailed report. Before I dig more into it, can you double check there is no other instance of rrdcached running, and using the same socket location? I think rrdcached was disabled by default on jessie, and was enabled by default on stretch. And since you are using

Bug#890286: rrdcached: "gmetad RRD_update [...] rrdcached: Permission denied" if limited socket specified first

2018-02-12 Thread Chad W Seys
Package: rrdcached Version: 1.6.0-1+b2 Severity: normal Hi, This is probably an upstream bug, with a workaround in Stretch. Upon upgrading from Jessie to Stretch ganglia gmetad could no longer use rrdcached to write rrds . Here's an example line from /var/log/messages: gangle