yum install php53-xml

or if you’re using puppet

package { ["php53-xml"]:
          ensure => present
        }

And finally, to get it to install, I used the below. I had to make it go to multiple lines to fit on the page but I have it all on 1 line in my puppet script:

exec { "pear channel-discover pear.phpunit.de;
pear channel-discover pear.symfony-project.com;
pear install --alldeps phpunit/PHPUnit  ":
          creates => "/usr/bin/phpunit"
 }

puppet --configprint all

It’ll print all your puppet configuration variables.

I’m setting all this up with puppet standalone. I don’t think we really gain anything by using the daemons, so it’s just a simple call to

puppet site.pp -v

And the changes are applied.

I ran into a snag today trying to get templates working. I kept getting the below error when trying to update my test system:

Could not find template ‘push.erb’ at /etc/puppet/manifests/site.pp:32 on node somename.myserver.local

Using strace:

[root@somename manifests]# strace -o ~/trace.txt -e trace=file puppet site.pp
Could not find template 'push.erb' at /etc/puppet/manifests/site.pp:32 on
node somename.myserver.local
[root@somename manifests]# tail -n 1 ~/trace.txt
stat("/var/puppet/templates", 0x7fffb7073a30) = -1 ENOENT (No such file or directory)

Fortunately there’s also config tool to check this stuff:

[root@somename manifests]# puppet --configprint templatedir
/var/puppet/templates

I have everything under /etc/puppet, NOT /var/puppet. I want the templates directory to reside in there too. I had a /etc/puppet/puppetd.conf file, and I set the templatedir variable in there under [puppetd] and [puppetmasterd] and [puppet] (I really had no idea which it needed) – and when that still didn’t work I tried renaming the config to puppet.conf. These are the lines I needed:

[puppet]
templatedir=/etc/puppet/templates

Thanks to the guys in #puppet on freenode for helping me sort this out.

See the puppet site and documentation for more info.

I kept getting the below error when trying to start puppet, even though I had created the user and group through the accounts prefs pane. Apparently that’s not good enough for the PuppetMaster to run.

For some reason this figuring this out was a huge pain. These are the steps I took to getting it installed. If it looks simple, well, that’s because it really is. Most people suggest solving this with MacPorts, but then I still wouldn’t know how to set up users and groups on Snow Leopard, so I’d just be screwing myself over in the long run.

Anyways, here’s the error I was getting:

err: /File[/var/puppet/rrd]: Failed to retrieve current state of resource:
Could not find group puppet

How to solve:

1. Install Facter and Puppet


This is easy enough – Snow Leopard comes with Ruby by default. Both can be downloaded from the Reductive Labs download page.

2. Install Server Admin Tools.


As of this blog entry, you can find them in Apple’s downloads section, although it was kind of a pain to find.

3. Enable Remote Management for youself


I was not able to connect to localhost until I enabled this option. You can control which users have management rights, so I’m not to concerned here.

4. Create user and group for puppet.


Use the GUI tool to create new a puppet user and group. You should now be able to start the pupptermasterd (yay!)

I’ll expand this post if I realize I forgot anything, or if questions come in.