Issue #9166 has been updated by Jeff Blaine.
With patch applied: Upon first restart of the master, then first connect by a client, I am seeing the following: <pre> debug: Processing report from rcf-cm-test.our.org with processor Puppet::Reports::Rrdgraph debug: Failed to load library 'RRD' for feature 'rrd' </pre> After that, with the master still running, another client run results in: <pre> err: Report processor failed: Failed to update resources: unknown DS name 'changed' </pre> Some RRDs, graphs and HTML do get created though. <pre> -rw-r--r-- 1 puppet puppet 10446 Aug 29 06:43 changes-daily.png -rw-r--r-- 1 puppet puppet 228 Aug 29 06:26 changes.html -rw-r--r-- 1 puppet puppet 11615 Aug 29 06:43 changes-monthly.png -rw-r--r-- 1 puppet puppet 2944 Aug 29 06:43 changes.rrd -rw-r--r-- 1 puppet puppet 10997 Aug 29 06:43 changes-weekly.png -rw-r--r-- 1 puppet puppet 10215 Aug 29 06:43 changes-yearly.png -rw-r--r-- 1 puppet puppet 220 Aug 29 06:26 daily.html -rw-r--r-- 1 puppet puppet 10283 Aug 29 06:43 events-daily.png -rw-r--r-- 1 puppet puppet 223 Aug 29 06:26 events.html -rw-r--r-- 1 puppet puppet 11452 Aug 29 06:43 events-monthly.png -rw-r--r-- 1 puppet puppet 2944 Aug 29 06:43 events.rrd -rw-r--r-- 1 puppet puppet 10834 Aug 29 06:43 events-weekly.png -rw-r--r-- 1 puppet puppet 10061 Aug 29 06:43 events-yearly.png -rw-r--r-- 1 puppet puppet 403 Aug 29 06:26 index.html -rw-r--r-- 1 puppet puppet 230 Aug 29 06:26 monthly.html -rw-r--r-- 1 puppet puppet 10013 Aug 29 06:43 resources-daily.png -rw-r--r-- 1 puppet puppet 238 Aug 29 06:26 resources.html -rw-r--r-- 1 puppet puppet 12174 Aug 29 06:43 resources-monthly.png -rw-r--r-- 1 puppet puppet 8368 Aug 29 06:43 resources.rrd -rw-r--r-- 1 puppet puppet 10390 Aug 29 06:43 resources-weekly.png -rw-r--r-- 1 puppet puppet 10724 Aug 29 06:43 resources-yearly.png -rw-r--r-- 1 puppet puppet 10732 Aug 29 06:44 time-daily.png -rw-r--r-- 1 puppet puppet 213 Aug 29 06:26 time.html -rw-r--r-- 1 puppet puppet 11882 Aug 29 06:44 time-monthly.png -rw-r--r-- 1 puppet puppet 5656 Aug 29 06:44 time.rrd -rw-r--r-- 1 puppet puppet 11090 Aug 29 06:44 time-weekly.png -rw-r--r-- 1 puppet puppet 10451 Aug 29 06:44 time-yearly.png -rw-r--r-- 1 puppet puppet 225 Aug 29 06:26 weekly.html -rw-r--r-- 1 puppet puppet 225 Aug 29 06:26 yearly.html </pre> I can reproduce the `unknown DS 'changed'` error at will by forcing something on the node to require a change (`rm /etc/ntp.conf`, re-run). FWIW, RRD support to Ruby was added with: <pre> gem install RubyRRDtool --no-ri --no-rdoc </pre> [ Insert "I dunno" image ] ---------------------------------------- Bug #9166: rrdgraph report processor tries to chown stuff to root? https://projects.puppetlabs.com/issues/9166 Author: Jeff Blaine Status: In Topic Branch Pending Merge Priority: Normal Assignee: Jeff Blaine Category: reports Target version: Affected Puppet version: Keywords: Branch: https://github.com/jamtur01/puppet/tree/tickets/master/9166 2.7.3 <pre> notice: Compiled catalog for rcf-cm-test.our.org in environment production in 0.02 seconds err: /File[/var/lib/puppet/rrd/rcf-cm-test.our.org]/ensure: change from absent to directory failed: Failed to set owner to '0': Operation not permitted - /var/lib/puppet/rrd/rcf-cm-test.our.org err: Report processor failed: Got 1 failure(s) while initializing: change from absent to directory failed: Failed to set owner to '0': Operation not permitted - /var/lib/puppet/rrd/rcf-cm-test.our.org </pre> It made the new dir for the node fine as user puppet, then tried to chown it to UID 0 for some reason? <pre> ~:rcf-cm-master # ls -l /var/lib/puppet/rrd/ total 4 drwxr-xr-x 2 puppet puppet 4096 Aug 23 12:47 rcf-cm-test.our.org/ </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
