I'm a first-time Puppet user, working with FreeBSD 9.2, Puppet 3.3.1, and
Ruby 2.0. I'm starting out with a very simple setup to test the waters:
node 'myhost' {
package { 'devel/jsmin':
ensure => 'installed',
provider => 'ports'
}
}
When I run:
puppet apply -v --debug manifests/site.pp
I get a bunch of output with various Linuxisms like selinux, rpm, apt-get,
dpkg, etc (making me think I need to specify that this is a FreeBSD host?),
and then:
Debug: Prefetching ports resources for package
Debug: Executing '/usr/sbin/pkg_info -aoQ'
Debug: Executing '/usr/sbin/pkg_info -aoQ'
Debug: Executing '/usr/local/sbin/portupgrade -N -M BATCH=yes devel/jsmin'
It all looks good, except that the process seems to stall out here. Running
'/usr/local/sbin/portupgrade -N -M BATCH=yes devel/jsmin' manually works
fine and completes in a few seconds. I can see from the `ps` listing that
command is active, but it just sits there, not completing.
I'm not sure how to debug this any further. Is it considered a bad idea to
run Puppet on a FreeBSD host? Based on my Google searches and amount of
discussion around it, it seems like there are very few people who are doing
this.
Any insight would be greatly appreciated.
Thanks,
Patrick
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5f2d0086-69b5-4a5e-8d36-419e294f1695%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
