I am, but there were standalone processes I'm not sure how to kill and disable.
I've currently got (from ps -ef | grep puppet): root 1296 1 0 11:34 ? 00:00:13 /usr/bin/ruby /usr/bin/puppet agent puppet 2246 1 0 11:58 ? 00:01:29 master puppet 5868 1 1 14:33 ? 00:00:26 master Is that OK, or do those master processes need getting rid of? Thanks, Gordon On Friday, 30 November 2012 14:37:06 UTC, Ygor wrote: > > You are using passenger, right ? > I believe you have to stop the passenger process and/or the apache process > it is running on. > > “Sometimes I think the surest sign that intelligent life exists elsewhere > in the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > ----- Original Message ----- > From: "Matthew Burgess" <matthew....@gmail.com <javascript:>> > To: puppet...@googlegroups.com <javascript:> > Sent: Friday, November 30, 2012 9:24:54 AM > Subject: Re: [Puppet Users] Simultaneous Client updates > > On Fri, Nov 30, 2012 at 2:08 PM, GordonJB <g.bon...@gmail.com<javascript:>> > wrote: > > I don't suppose you know how to stop the service on 3.0? There is no > > puppetmaster process left, just puppet, and I'd like to keep the puppet > > client running! > > If there's no master process left, then it is stopped, surely? > > Here's an output of 'ps -ef | grep puppet' on my server: > > puppet 2777 1 0 10:17 ? 00:02:11 /usr/bin/ruby > /usr/bin/puppet master > root 2959 1 0 10:17 ? 00:00:03 /usr/bin/ruby > /usr/bin/puppet agent > > So, assuming you only have your 'puppet agent' process showing up > there, then all is good. > > Now, what you probably want to do is restart your httpd server. Once > it's back up and running, use 'lsof -i :8140' to confirm that httpd is > listening on the port that your puppet agents will be trying to > connect to. Now watch the output of 'ps' whilst an agent checks in > (you can trigger this by running 'puppet agent --test'). Depending on > your Passenger settings, you should see a 'master' process appear, > then disappear again once the agent is has completed its run. > > Regards, > > Matt. > > > On Friday, 30 November 2012 12:02:06 UTC, Matthew Burgess wrote: > >> > >> On Fri, Nov 30, 2012 at 11:29 AM, GordonJB <g.bon...@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 view this discussion on the web visit > > https://groups.google.com/d/msg/puppet-users/-/DhYEdDqRZdUJ. > > > > To post to this group, send email to > > puppet...@googlegroups.com<javascript:>. > > > To unsubscribe from this group, send email to > > puppet-users...@googlegroups.com <javascript:>. > > 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...@googlegroups.com<javascript:>. > > To unsubscribe from this group, send email to > puppet-users...@googlegroups.com <javascript:>. > 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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/33tSnpggKKoJ. 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.
