Greg
2009-May-06 05:59 UTC
[Puppet Users] Puppet Reporting - ignoring reports config option?
Hi all, I''ve gotten a fair way into implementing a pilot puppet implementation. I have a reasonable amount of the configuration done, and have been working on reporting. At present, on the puppetmaster I have: report = true <-- puppetmaster is also a puppet... reportserver = puppet reportdir = /var/opt/csw/puppet/reports <-- Files definately being uploaded from 2 clients. reportfrom = i.am@somewhere.com reports = tagmail,store,log tagmap = /etc/opt/csw/puppet/tagmail.conf (I''ve chopped out the seemingly less relevant options... They are all pretty much standard as per puppetd --genconfig, though I have commented out the CA options to leave them as defaults) in tagmail.conf I only have one line: all: sysadmin@somewhere.com Running "puppetmasterd --debug" it appears to only run the ''store'' report, which of course shoves the yaml file into /var/opt/csw/puppet/ reports as its supposed to do... Logs from puppetmasterd: May 6 15:40:19 pmaster puppetmasterd[1802]: [ID 702911 daemon.info] Expiring the node cache of test1 May 6 15:40:19 pmaster puppetmasterd[1802]: [ID 702911 daemon.info] Not using expired node for test1 from cache; expired at Wed May 06 15:39:19 +1000 2009 May 6 15:40:19 pmaster puppetmasterd[1802]: [ID 702911 daemon.info] Caching node for test1 May 6 15:40:20 pmaster puppetmasterd[1802]: [ID 702911 daemon.notice] Compiled catalog for test1 in 1.02 seconds May 6 15:40:54 pmaster puppetmasterd[1802]: [ID 702911 daemon.info] Processing reports store for test1 I am guessing that "Processing reports store for <server>" indicates which report (store) is being run, and that since I have only one log entry that it is the only report being attempted. I''ve reviewed as much of the reporting code as I can follow, but am drawing a blank at exactly where it reads the config option - the only Ruby I have done is relating to understanding Puppet... This is all running off 0.24.7 on Solaris 10 using the latest Blastwave packages... Any thoughts on what I''m missing would be appreciated. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Greg
2009-May-06 07:07 UTC
[Puppet Users] Re: Puppet Reporting - ignoring reports config option?
Gahhhhh... Figured out the problem literally 5 minutes after I posted... Problem was that I had generated a puppet.conf using --genconfig and forgotten to remove genconfig = true... Logs reported that the config file had been re-read, but obviously not true if this setting has been left enabled - after all --genconfig prints a config file and exits... Obviously had I actually restarted puppetmasted I would have seen this... <kicking self for a wasted day> Greg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---