On Fri, Dec 17, 2010 at 7:33 AM, Brian LaShomb <blash...@gmail.com> wrote: > Thanks Nigel, > I deleted the /etc/puppet and /var/lib/puppet directories and then recreated > the /var/lib/puppet directory with puppet user/group ownership. I then reran > the package installers. No more rrd error. But it still hangs on the > "Finishing Transaction" line. I had already created the puppet user and > group ahead of time. > Thought I might need to create that site.pp manifest again, so I did the > same and reran puppetmasterd, still hangs in the same place.
Are you sure it's actually hung rather than just running as a daemon? Can nodes connect to it and do things? I won't be online for a little while, but if you should be able to get a hand on our IRC channel #puppet http://projects.puppetlabs.com/projects/puppet/wiki/Irc_Channel > > > > > On Thu, Dec 16, 2010 at 6:02 PM, Nigel Kersten <ni...@puppetlabs.com> wrote: >> >> On Thu, Dec 16, 2010 at 1:40 PM, Brian LaShomb <blash...@gmail.com> wrote: >> > Hi all... finally getting around to trying Puppet, I'm excited to get >> > started, but I'm stuck on install. My server a 3-month old Xserve with >> > 6GB >> > of RAM. Didn't configure any other services for it yet, and I tried >> > installing puppet and facter 3 different ways (because I thought the >> > missing >> > rrd directory could've been an install glitch). >> > First I tried downloading from puppetlabs.com and using 'ruby install'. >> > Second, I tried the packages for OS X (linked to from Puppet's site). >> > Third >> > I tried 'gem install'. >> > After install, I create a file called site.pp at /etc/puppet/manifests >> > with >> > the following. I change this file to puppet user and group permissions. >> > >> > file { "/etc/passwd": owner => "root", >> > >> > group => "bin", mode => 644, >> > >> > } >> > >> > Then I start puppet using: sudo puppetmasterd --verbose --debug >> > --no-daemonize >> > The end of the output shows: >> > err: /File[/var/lib/puppet/rrd]/ensure: change from absent to directory >> > failed: Could not set 'directory on ensure: Permission denied - >> > /var/lib/puppet/rrd >> > debug: Finishing transaction 2165906120 >> > Could not run: Got 1 failure(s) while initializing: change from absent >> > to >> > directory failed: Could not set 'directory on ensure: Permission denied >> > - >> > /var/lib/puppet/rrd >> >> There's a bug we fixed in the package creation script. >> >> We didn't create /var/lib/puppet ahead of time, so creating >> /var/lib/puppet/rrd fails. >> >> Create /var/lib/puppet and it should all be good. >> >> Note that the other big bug is that --mkusers doesn't work. There is a >> patch in, but no release that includes it yet. >> >> You can create the puppet user/group by hand. >> >> >> >> > >> > I have no rrd directory... here is what I have. >> > server:~ admin$ ls -al /var/lib/puppet/ >> > total 0 >> > drwxr-xr-x 11 root wheel 374 Dec 16 14:31 . >> > drwxr-xr-x 4 root wheel 136 Dec 16 14:31 .. >> > drwxr-x--- 2 puppet puppet 68 Dec 16 14:31 bucket >> > drwxr-xr-x 2 root wheel 68 Dec 16 14:31 facts >> > drwxr-xr-x 2 root wheel 68 Dec 16 14:31 lib >> > drwxr-x--- 3 puppet puppet 102 Dec 16 14:31 log >> > drwxr-x--- 2 puppet puppet 68 Dec 16 14:31 reports >> > drwxrwxrwt 3 root wheel 102 Dec 16 14:31 run >> > drwxr-x--- 2 puppet puppet 68 Dec 16 14:31 server_data >> > drwxr-xr-t 2 root wheel 68 Dec 16 14:31 state >> > drwxr-x--- 2 puppet puppet 68 Dec 16 14:31 yaml >> > >> > From here I've tried creating the rrd directory and applying user and >> > group >> > permissions to puppet, but it just hangs with the following output when >> > rerunning the aforementioned puppetmasterd command. >> > notice: Starting Puppet master version 2.6.4 >> > debug: No file server configuration file; autocreating modules mount >> > with >> > default permissions >> > debug: No file server configuration file; autocreating plugins mount >> > with >> > default permissions >> > debug: Finishing transaction 2165520200 >> > >> > What am I missing? Thanks for the help... I can't wait to start using >> > Puppet! >> > >> > -Brian >> > >> > >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Puppet Users" group. >> > To post to this group, send email to puppet-us...@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. >> > >> >> >> >> -- >> Nigel Kersten - Puppet Labs - http://www.puppetlabs.com >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-us...@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. >> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > -- Nigel Kersten - Puppet Labs - http://www.puppetlabs.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
