Getting a different error now:
15:58:11 tester:/etc/puppet root# puppetmasterd --verbose --debug
Ruby on darwin is broken; puppetmaster will not set its UID to
'puppet' and must run as root
and system.log:
Feb 6 15:24:38 tester puppetmasterd[13934]: Reopening log files
Feb 6 15:24:38 tester puppetmasterd[13934]: Starting Puppet server
version 0.24.7
Not perfect, but the daemon runs, and a test from a client (# puppetd
--server myserver.domain.com --waitforcert 60 --test) is producing
the expected results. I'm seeing hope!
This is the ruby I'm running:
15:25:05 tester:/etc/puppet root# /usr/bin/ruby -v
ruby 1.8.6 (2007-03-13 patchlevel 0) [universal-darwin8.0]
I upgraded ruby to 1.8.6 before I started monkeying around with
puppet, because I was aware of some issues with 1.8.2 that came stock
in 10.4. Not sure why it's complaining.
Now that we've gotten this far there are a lot more things I want to
test and try out, but it's late Friday afternoon, so I have a good to-
do list for Monday morning. I'll let you know how it goes. Thanks
again for the assistance thus far.
On Feb 6, 2009, at 3:10 PM, Nigel Kersten wrote:
> If mkusers is broken, I'd just make a puppet user and group and see if
> that stops this being a problem.
>
> Also please bug report this on the reductivelabs site.
>
> http://projects.reductivelabs.com/issues/
>
>
I'm following the install guide from here:
http://reductivelabs.com/trac/puppet/wiki/InstallationGuide#BuildingtheServer
This is what I've done:
1) Install Puppet and Factor packages from Nigel's site
2) create /etc/puppet/puppet.conf with the following content
[main]
user = 0
group = 0
server = chm200.educ.psu.edu
certname = chm200. educ.psu.edu
autosign = false
[puppetd]
evaltrace = true
factsync = true
3) create /etc/puppet/fileserver.conf
[facts]
path /etc/puppet/dist/facts
allow *
[files]
path /etc/puppet/dist/files
allow *
4) Created first manifest. /etc/puppet/manifests/site.pp
# site.pp
file { "/etc/sudoers":
owner => root, group => root, mode => 440
}
5) mkdir /etc/puppet/dist/facts
6) mkdir /etc/puppet/dist/files
8) sudo puppetmasterd --no-daemonize --verbose
This is what I've got:
bash-3.2# sudo puppetmasterd --no-daemonize --verbose
/Library/Ruby/Site/1.8/puppet/util/settings.rb:1042:in `parse_file':
Could not match line [main] at /etc/puppet/puppet.conf:[main]
(Puppet::Error)
from /Library/Ruby/Site/1.8/puppet/util/settings.rb:1005:in `each'
from /Library/Ruby/Site/1.8/puppet/util/settings.rb:1005:in `parse_file'
from /Library/Ruby/Site/1.8/puppet/util/settings.rb:350:in `unsafe_parse'
from /Library/Ruby/Site/1.8/puppet/util/settings.rb:344:in `parse'
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/sync.rb:229:in
`synchronize'
from /Library/Ruby/Site/1.8/puppet/util/settings.rb:343:in `parse'
from /Library/Ruby/Site/1.8/puppet.rb:177:in `parse_config'
from /usr/bin/puppetmasterd:165
Two questions.
One, what could be wrong
Two, am I supposed to have a space in the certname = chm200. educ.psu.edu entry?
Thanks
Rusty
On Wed, Apr 15, 2009 at 4:00 PM, Daniel Koblas <itsu...@chrisking.com> wrote:
> Well, yes and no. Yes I still get the message "Ruby on darwin is broken;
> puppetmaster will not set its UID to 'puppet' and must run as root" when
> starting up puppetmasterd, but no in that it really can just be ignored,
> because puppet does have to run as root on os x; there's no need for the
> puppet user in this case. After I posted this and a couple of other issues
> I was running into when I was first getting things set up, I got this reply,
> which I found pretty helpful in getting things going, as a lot of my issues
> were just learning-curve related and not anything "broken" in the software
> per se.
> from marcus...@gmail.com:
> "I use Nigel Kerstens packages from
> https://sites.google.com/a/explanatorygap.net/puppet/ and have had no
> trouble with them.
> You don't have to make users on the mac because puppet only runs as
> root, I believe due to a limitation in how macosx works.
> My rough notes on getting started are:
> 1) Install Puppet and Factor packages from Nigel's site
> 2) create /etc/puppet/puppet.conf with the following content
> [main]
> user = 0
> group = 0
> server = puppet.example.com
> certname = puppet. example.com
> autosign = false
> [puppetd]
> evaltrace = true
> factsync = true
>
> 3) create /etc/puppet/fileserver.conf
> [facts]
> path /etc/puppet/dist/facts
> allow *
> [files]
> path /etc/puppet/dist/files
> allow *
>
> 4) mkdir /etc/puppet/dist/facts
> 5) mkdir /etc/puppet/dist/files
> 6) create /etc/puppet/manifests/site.pp (can be empty to start with)
> 7) sudo puppetmasterd --no-daemonize --verbose
> That should get your puppetmasterd running.
> I use the Launchd script from
> https://reductivelabs.com/trac/puppet/wiki/PuppetWithLaunchd to keep
> it running."
> Not sure if this really answers your question, but I hope it helps.
> One resource I found extremely helpful is Nigel Kirsten and Jeff McCune's
> macworld presentation on using puppet, if you haven't seen it, it is worth
> checking out:
> http://northstarlabs.net/blog/wp-content/uploads/2008/02/IT824.mp4
> -Dan
>
> On Apr 15, 2009, at 11:25 AM, rusty wrote:
>
> Daniel,
> Wondering if your still running with this issue, have it resolved, or
> if it matters at all considering functionality?
> I'm seeing the same error on OS X 10.5.6 with puppet installed through
> macports. I am using ruby 1.8.6 too.
> New to the project, hoping to use puppet where I work. Thanks
> Rusty
> On Feb 6, 8:25 pm, Daniel Koblas <itsupp...@chrisking.com> wrote:
>
> So, I used workgroup manager to create a user and grouppuppet/puppet. I was
> hesitant to do this before, as I didn't (and still
> don't) know what all to configure on the account (password, level of
> access, etc), and I also wanted to at least try to troubleshoot
> whether --mkusers didn't work because of something I was missing/
> mangling, or if it just, well, didn't work.
> Getting a different error now:
> 15:58:11 tester:/etc/puppetroot# puppetmasterd --verbose
> --debugRubyondarwinisbroken;puppetmasterwillnotsetitsUIDto
> 'puppet' andmustrunasroot
> and system.log:
> Feb 6 15:24:38 tester puppetmasterd[13934]: Reopening log files
> Feb 6 15:24:38 tester puppetmasterd[13934]: StartingPuppetserver
> version 0.24.7
> Notperfect, but the daemon runs, and a test from a client (# puppetd
> --server myserver.domain.com --waitforcert 60 --test) is producing
> the expected results. I'm seeing hope!
> This is therubyI'm running:
> 15:25:05 tester:/etc/puppetroot# /usr/bin/ruby-vruby1.8.6 (2007-03-13
> patchlevel 0) [universal-darwin8.0]
> I upgradedrubyto 1.8.6 before I started monkeying around with puppet,
> because I was aware of some issues with 1.8.2 that came stock
> in 10.4. Notsure why it's complaining.
> Now that we've gotten this far there are a lot more things I want to
> test and try out, but it's late Friday afternoon, so I have a good to-
> do list for Monday morning. I'll let you know how it goes. Thanks
> again for the assistance thus far.
> On Feb 6, 2009, at 3:10 PM, Nigel Kersten wrote:
>
> If mkusers isbroken, I'd just make apuppetuser and group and see if
Rusty,
No space in the certname. Sorry, that is a typo mistake on my behalf.
Marcus.
I'll be posting and updated guide on how to get this running within a
few months, hopefully to help others like myself. Cheers
Rusty