On Fri, Nov 30, 2012 at 11:29 AM, GordonJB <g.bonth...@gmail.com> wrote:
> 1) I didn't think so, but looking in my ps, I have the following: > > puppet 17826 1 1 03:27 ? 00:04:37 master > www-data 18614 1350 0 Nov29 ? 00:00:00 /usr/sbin/apache2 -k start > root 18626 1350 0 Nov29 ? 00:00:06 > /usr/lib/phusion_passenger/ApplicationPoolServerExecutable 0 > /usr/lib/phusion_passenger/passenger-spawn-server /usr/bin/ruby > /tmp/passenger.1350 > root 18628 18626 0 Nov29 ? 00:02:19 Passenger spawn server > www-data 18638 1350 0 Nov29 ? 00:04:41 /usr/sbin/apache2 -k start > www-data 18639 1350 0 Nov29 ? 00:04:39 /usr/sbin/apache2 -k start > > I thought the puppet master service was puppet-master, is that it up the > top? Yes, that's it. For puppet-3.0, it's shown as 'master', I think previous puppet versions would display it as 'puppetmasterd'. Now, the fact that its parent pid is '1', suggests that it was launched via init, i.e. it's the standalone puppet master, not one of your Passenger-invoked masters. I don't have a passenger setup here at the moment, but can do so to provide a comparison if required. For now, I'd suggest you do whatever the equivalent of 'service puppetmaster stop; chkconfig puppetmaster off' is on your OS (i.e. stop the standalone puppet master, and prevent it from starting across reboots). You may also need to restart your httpd as I'd be surprised if your VirtualHost is listening on 8140 with that standalone puppet master bound to that port already. Hopefully I've not misinterpreted the above! Thanks, Matt. -- 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.
