Ok guys... thanks to the #puppet irc guys, I have been able to fix my problem.
Seems as though when downloading mysql gem via "gem install mysql", puppetmaster was not interfacing with mysql server correctly, and therefore not populating the database. So i removed the mysql gem - "gem uninstall mysql" and installed the rpm package ruby-mysql.rpm from epel. Puppetmaster with storeconfigs is now working correctly with mysql server. Cheers, Josh On Aug 31, 12:17 pm, josbal <joshua.bald...@gmail.com> wrote: > Does anyone have any suggestions as to why storeconfigs aren't working > for me? > > On Aug 28, 1:44 pm, josbal <joshua.bald...@gmail.com> wrote: > > > Hey Ohad, > > > Does my puppet.conf from my puppetmaster help you? > > > Cheers, > > Josh > > > On Aug 27, 2:53 pm, josbal <joshua.bald...@gmail.com> wrote: > > > > Surething... > > > > [main] > > > # Where Puppet stores dynamic and growing data. > > > # The default value is '/var/puppet'. > > > vardir = /var/lib/puppet > > > > # The Puppet log directory. > > > # The default value is '$vardir/log'. > > > logdir = /var/log/puppet > > > > # Where Puppet PID files are kept. > > > # The default value is '$vardir/run'. > > > rundir = /var/run/puppet > > > > # Where SSL certificates are kept. > > > # The default value is '$confdir/ssl'. > > > ssldir = $vardir/ssl > > > > # Manifest Files for production servers > > > manifest = /etc/puppet/default/site.pp > > > modulepath = /etc/puppet/default/modules > > > > [puppetd] > > > # The file in which puppetd stores a list of the classes > > > # associated with the retrieved configuratiion. Can be loaded in > > > # the separate ``puppet`` executable using the ``--loadclasses`` > > > # option. > > > # The default value is '$confdir/classes.txt'. > > > classfile = $vardir/classes.txt > > > > # Where puppetd caches the local configuration. An > > > # extension indicating the cache format is added automatically. > > > # The default value is '$confdir/localconfig'. > > > localconfig = $vardir/localconfig > > > > # Allow puppetrunner to start catalogue run. > > > listen = true > > > > [puppetmasterd] > > > storeconfigs = true > > > dbadapter = mysql > > > dbuser = puppet > > > dbpassword = puppet > > > dbserver = localhost > > > dbsocket = /var/lib/mysqld/mysqld.sock > > > > # Testing Environment > > > [testing] > > > > # Manifest Files for testing environment > > > manifest = /etc/puppet/testing/site.pp > > > modulepath = /etc/puppet/testing/modules > > > > On Aug 27, 11:53 am, Ohad Levy <ohadl...@gmail.com> wrote: > > > > > You dont need to run it as root, can you please paste your puppet.conf? > > > > > cheers, > > > > Ohad > > > > > On Thu, Aug 27, 2009 at 9:40 AM, josbal <joshua.bald...@gmail.com> > > > > wrote: > > > > > > Why would the permissions / running as root need to change for using > > > > > storeconfigs? > > > > > > As mentioned before our testing puppet server is configured in the > > > > > same way and didn't have this permissions issue. > > > > > > On Aug 27, 11:32 am, Jason Rojas <ja...@nothingbeatsaduck.com> wrote: > > > > > > 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 <joshua.bald...@gmail.com> > > > > > > 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?Ok guys... thanks to the #puppet irc guys, > > > > > > > I have been able to fix my problem. --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
