Re: [Puppet Users] puppet terminating - continually forcing itself to stop

2011-07-11 Thread Chris Phillips
On 5 July 2011 16:26, Chris Phillips ch...@untrepid.com wrote: On 5 July 2011 14:24, Martin Alfke tux...@gmail.com wrote: On 07/05/2011 03:19 PM, Brian Gallew wrote: I was seeing the behavior on my Solaris boxes when running Puppet under SMF. The issue, in my case, was that I was trying

Re: [Puppet Users] puppet terminating - continually forcing itself to stop

2011-07-11 Thread Dominic Cleal
On 11/07/11 09:18, Chris Phillips wrote: Coming into work this morning I've seen a bunch of func processes have stopped and puppet is doing nothing at all about it, despite a manifest advising something else: Manifest says - service { funcd: ensure = running, enable

Re: [Puppet Users] puppet terminating - continually forcing itself to stop

2011-07-11 Thread Chris Phillips
On 11 July 2011 14:54, Dominic Cleal dcl...@redhat.com wrote: On 11/07/11 09:18, Chris Phillips wrote: Coming into work this morning I've seen a bunch of func processes have stopped and puppet is doing nothing at all about it, despite a manifest advising something else: Manifest says -

[Puppet Users] puppet terminating - continually forcing itself to stop

2011-07-05 Thread Chris Phillips
Hi, I've a puppet module running which ensures the puppet service is not running and not starting on boot. A few times a few different nodes have become stuck, apparently always thinking that the service is running when it is not. The following below excerpt just goes round and round run after

Re: [Puppet Users] puppet terminating - continually forcing itself to stop

2011-07-05 Thread Ken Barber
What does your service {} block look like? Are you using hasstatus = true? For example: service { puppet: ensure = running, enable = true, hasstatus = true, } ken. On Tue, Jul 5, 2011 at 9:53 AM, Chris Phillips ch...@untrepid.com wrote: Hi, I've a puppet module running which ensures the

Re: [Puppet Users] puppet terminating - continually forcing itself to stop

2011-07-05 Thread Chris Phillips
Currently it's just like this: service { puppet: #ensure = running, #enable = true, ensure = stopped, enable = false, subscribe = File[/etc/puppet/puppet.conf], hasrestart = true, hasstatus = true,

Re: [Puppet Users] puppet terminating - continually forcing itself to stop

2011-07-05 Thread vagn scott
On 07/05/2011 07:15 AM, Chris Phillips wrote: debug: Service[puppet](provider=redhat): Executing '/sbin/service puppet stop' notice: Caught TERM; calling stop [root@gibsvlin-erp2dst ~]# /etc/init.d/puppet status puppetd is stopped That's just weird looking. So puppet is running, and

Re: [Puppet Users] puppet terminating - continually forcing itself to stop

2011-07-05 Thread Brian Gallew
I was seeing the behavior on my Solaris boxes when running Puppet under SMF. The issue, in my case, was that I was trying to work around an SMF bug. My workaround was to svcadm disable puppetd;svccfg import /var/svc/manifest/network/puppetd.xml;svcadm enable puppet. The astute viewer will

Re: [Puppet Users] puppet terminating - continually forcing itself to stop

2011-07-05 Thread Martin Alfke
On 07/05/2011 03:19 PM, Brian Gallew wrote: I was seeing the behavior on my Solaris boxes when running Puppet under SMF. The issue, in my case, was that I was trying to work around an SMF bug. My workaround was to svcadm disable puppetd;svccfg import

Re: [Puppet Users] puppet terminating - continually forcing itself to stop

2011-07-05 Thread vagn scott
On 07/05/2011 09:24 AM, Martin Alfke wrote: On 07/05/2011 03:19 PM, Brian Gallew wrote: I was seeing the behavior on my Solaris boxes when running Puppet under SMF. The issue, in my case, was that I was trying to work around an SMF bug. My workaround was to svcadm disable

Re: [Puppet Users] puppet terminating - continually forcing itself to stop

2011-07-05 Thread Chris Phillips
On 5 July 2011 14:24, Martin Alfke tux...@gmail.com wrote: On 07/05/2011 03:19 PM, Brian Gallew wrote: I was seeing the behavior on my Solaris boxes when running Puppet under SMF. The issue, in my case, was that I was trying to work around an SMF bug. My workaround was to svcadm disable