Sounds like you need to run puppetmaster as the root user or change some file permissions.
-Jason On Aug 26, 2009, at 4:58 PM, josbal <[email protected]> wrote: > > Hi Guys, > > Im trying to turn on storeconfigs with a mysql db backend. On my > testing server in our lab, i configured this successfully and can see > if keeping information on all test hosts. > > When trying to implent the same idea onto our production puppet > server, I get the following errors: > > Aug 26 16:35:53 opsynxsr0097 puppetmasterd[27003]: (/Settings[/etc/ > puppet/puppet.conf]/Settings[puppetmasterd]/File[/var/lib/puppet/ > yaml]/ > owner) Cannot manage ownership unless running as root > Aug 26 16:35:53 opsynxsr0097 puppetmasterd[27003]: (/Settings[/etc/ > puppet/puppet.conf]/Settings[puppetmasterd]/File[/var/lib/puppet/ > bucket]/owner) Cannot manage ownership unless running as root > Aug 26 16:35:53 opsynxsr0097 puppetmasterd[27003]: (/Settings[/etc/ > puppet/puppet.conf]/Settings[puppetmasterd]/File[/var/log/puppet/ > masterhttp.log]/owner) Cannot manage ownership unless running as root > Aug 26 16:35:53 opsynxsr0097 puppetmasterd[27003]: (/Settings[/etc/ > puppet/puppet.conf]/Settings[puppetmasterd]/File[/etc/puppet/ > manifests]/ensure) change from absent to directory failed: Could not > set directory on ensure: Permission denied - /etc/puppet/manifests > Aug 26 16:35:53 opsynxsr0097 puppetmasterd[27003]: Could not call: Got > 1 failure(s) while initializing: change from absent to directory > failed: Could not set directory on ensure: Permission denied - /etc/ > puppet/manifests > Aug 26 16:44:23 opsynxsr0097 puppetmasterd[26903]: (/Settings[/etc/ > puppet/puppet.conf]/Settings[puppetmasterd]/File[/var/log/puppet/ > masterhttp.log]/owner) Cannot manage ownership unless running as root > Aug 26 16:44:23 opsynxsr0097 puppetmasterd[26903]: (/Settings[/etc/ > puppet/puppet.conf]/Settings[puppetmasterd]/File[/etc/puppet/ > manifests]/ensure) change from absent to directory failed: Could not > set directory on ensure: Permission denied - /etc/puppet/manifests > Aug 26 16:44:23 opsynxsr0097 puppetmasterd[26903]: (/Settings[/etc/ > puppet/puppet.conf]/Settings[puppetmasterd]/File[/var/lib/puppet/ > yaml]/ > owner) Cannot manage ownership unless running as root > Aug 26 16:44:23 opsynxsr0097 puppetmasterd[26903]: (/Settings[/etc/ > puppet/puppet.conf]/Settings[puppetmasterd]/File[/var/lib/puppet/ > bucket]/owner) Cannot manage ownership unless running as root > Aug 26 16:44:23 opsynxsr0097 puppetmasterd[26903]: Could not call: Got > 1 failure(s) while initializing: change from absent to directory > failed: Could not set directory on ensure: Permission denied - /etc/ > puppet/manifests > Aug 26 16:44:23 opsynxsr0097 puppetd[19641]: Could not retrieve > catalog: Got 1 failure(s) while initializing: change from absent to > directory failed: Could not set directory on ensure: Permission denied > - /etc/puppet/manifests > Aug 26 16:44:23 opsynxsr0097 puppetd[19641]: Starting catalog run > > > The only difference between my testing and production puppet servers, > is my production server is running 2 puppet environments: production & > testing. Im thinking that the storeconfig options are understanding my > environment setttings, as in the error "/etc/puppet/manifests" is > referenced, yet does not exist in my configurations. > > Has anyone got storeconfigs running under environments? Any tips to > assist with the above? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
