[Puppet Users] Re: /etc/init.d/puppet on debian

2009-05-09 Thread Gary Law
2009/5/3 Russ Allbery > > Gary Law writes: > > > The init script is clearly trying to make the pid file appear in > > /var/run/puppet... so I've little idea why this is happening. > > > > from the init script: > > start_puppet() { > > start-stop-daemon --start --quiet --pidfile > > /var/

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-05-03 Thread Marcin Owsiany
On Sat, May 02, 2009 at 07:46:07PM -0700, Russ Allbery wrote: > That flag doesn't say where to write the PID file. It tells > start-stop-daemon where puppetd *will* write the PID file. Or rather, where the deamon has written the pid, so that start-stop-daemon can check whether it's running. > Y

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-05-02 Thread Russ Allbery
Gary Law writes: > The init script is clearly trying to make the pid file appear in > /var/run/puppet... so I've little idea why this is happening. > > from the init script: > start_puppet() { > start-stop-daemon --start --quiet --pidfile > /var/run/puppet/$NAME.pid \ > -

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-05-02 Thread Gary Law
Returning late to this thread, it seems that my pid is getting written to /var/puppet/run/puppetd.pid But the debian /etc/init.d/puppet script is expecting it in /var/run/puppet/puppetd.pid The init script is clearly trying to make the pid file appear in /var/run/puppet... so I've little idea why

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-10 Thread Marcin Owsiany
On Wed, Apr 08, 2009 at 07:44:07PM +0100, Gary Law wrote: > 2009/4/6 Marcin Owsiany > > > > > On Mon, Apr 06, 2009 at 10:50:17AM +0100, Gary Law wrote: > > > + start-stop-daemon --stop --quiet --pidfile /var/run/puppet/puppetd.pid > > [...] > > > g...@dv01:~ $ ps -ef | grep [p]uppet > > > root

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-08 Thread Gary Law
2009/4/6 Marcin Owsiany > > On Mon, Apr 06, 2009 at 10:50:17AM +0100, Gary Law wrote: > > + start-stop-daemon --stop --quiet --pidfile /var/run/puppet/puppetd.pid > [...] > > g...@dv01:~ $ ps -ef | grep [p]uppet > > root 6774 1 0 Apr04 ?00:06:49 ruby /usr/sbin/puppetd -w > 5 > >

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-06 Thread Larry Ludwig
Hi all can you also look into this bug and see if it applies to debian/ ubuntu. http://projects.reductivelabs.com/issues/2137 and if so make adjustments according. -L -- Larry Ludwig Reductive Labs --~--~-~--~~~---~--~~ You received this message because you a

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-06 Thread Marcin Owsiany
On Mon, Apr 06, 2009 at 10:50:17AM +0100, Gary Law wrote: > + start-stop-daemon --stop --quiet --pidfile /var/run/puppet/puppetd.pid [...] > g...@dv01:~ $ ps -ef | grep [p]uppet > root 6774 1 0 Apr04 ?00:06:49 ruby /usr/sbin/puppetd -w 5 Try: start-stop-daemon --stop --pidfile /

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-06 Thread Gary Law
2009/4/4 Marcin Owsiany > > On Fri, Apr 03, 2009 at 05:58:45PM +0100, Gary Law wrote: > > g...@dv01:/ $ sudo /etc/init.d/puppet stop > [...] > > I can't see any obvious reason why this isn't working > > sudo bash -x /etc/init.d/puppet stop > > might be enlightening.. Hi Marcin :) Here you go.

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-04 Thread Marcin Owsiany
On Fri, Apr 03, 2009 at 05:58:45PM +0100, Gary Law wrote: > g...@dv01:/ $ sudo /etc/init.d/puppet stop [...] > I can't see any obvious reason why this isn't working sudo bash -x /etc/init.d/puppet stop might be enlightening.. -- Marcin Owsiany http://marcin.owsiany.pl/ GnuPG: 102

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-03 Thread Martin Wheldon
Here we go now I'm back to a machine. [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter pluginsync=false environment=production [puppetmasterd] environments=production,testing,development templatedir=/var/lib/puppet

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-03 Thread Gary Law
2009/4/2 Keith Edmunds > > OK, you're running exactly the same version of puppet as I am, and I have > the same entries for [puppetd] save for the server name. I don't have the > problem you have. > > It's worth stopping puppet and then checking for any running puppet > process (I use "ps -ef|gre

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-03 Thread Martin Wheldon
I'm also running the same version of Puppet from the Debian Lenny repositories and I don't see this issue. I do however see that the init script doesn't honour the START=no in /etc/default/puppet. I'll post my config file later when I get access to my kit :) Martin On Thu, Apr 2, 2009 at 11:19

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-02 Thread Keith Edmunds
OK, you're running exactly the same version of puppet as I am, and I have the same entries for [puppetd] save for the server name. I don't have the problem you have. It's worth stopping puppet and then checking for any running puppet process (I use "ps -ef|grep puppet") and killing any that may b

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-02 Thread Gary Law
2009/4/2 Keith Edmunds > > On Thu, 2 Apr 2009 22:06:22 +0100, gary@gmail.com said: > > > Basically, the stop argument doesn't seem to work, and AFAIK nothing gets > > written to /var/run/puppet. > > What is the output of: > > $ dpkg -l|grep puppet > > and > > $ cat /etc/puppet/puppet.conf >

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-02 Thread Keith Edmunds
On Thu, 2 Apr 2009 22:06:22 +0100, gary@gmail.com said: > Basically, the stop argument doesn't seem to work, and AFAIK nothing gets > written to /var/run/puppet. What is the output of: $ dpkg -l|grep puppet and $ cat /etc/puppet/puppet.conf Keith --~--~-~--~~~---

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-02 Thread Gary Law
2009/4/1 Keith Edmunds > > You haven't said which version of Debian you are running. If you are > running Etch/oldstable/V4.0, you have a very old version of puppet in the > > You STILL haven't said what you have in /etc/puppet/puppet.conf, so I'm > going to back off from trying to help further

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Russ Allbery
Nigel Kersten writes: > Keith, can you make sure you bug report this on bugs.debian.org ? > > A few of us have joined in to help the Debian Puppet packaging > project, and we're going to start churning through the reported bugs > next week. That's excellent news -- thank you very much for doing

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Russ Allbery
Rob McBroom writes: > On 2009-Apr-1, at 9:35 AM, Nigel Kersten wrote: >> A few of us have joined in to help the Debian Puppet packaging project, >> and we're going to start churning through the reported bugs next week. > Will this include getting it added to backports? Thanks. As long as you c

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Keith Edmunds
You haven't said which version of Debian you are running. If you are running Etch/oldstable/V4.0, you have a very old version of puppet in the standard repository. If you're running Lenny/stable/5.0, the version in the repository works fine. In neither case would I install from experimental, given

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Trevor
so this was a problem because 1. apt-get insatll puppet 2. apt-get install puppet- 3. apt-get install puppet/experimental so experimental installs /etc/init.d/puppet.dpkg-dist (/var/run/ puppet/puppet.pid) but non-experimental installs /etc/init.d/puppet(/var/run/ puppet.pid) so I didnt r

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Rob McBroom
On 2009-Apr-1, at 9:35 AM, Nigel Kersten wrote: > A few of us have joined in to help the Debian Puppet packaging > project, and we're going to start churning through the reported bugs > next week. Will this include getting it added to backports? Thanks. -- Rob McBroom

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Nigel Kersten
Ah. I misread the thread. Ta. On Wed, Apr 1, 2009 at 8:52 AM, Keith Edmunds wrote: > > On Wed, 1 Apr 2009 06:35:04 -0700, nig...@google.com said: > >> Keith, can you make sure you bug report this on bugs.debian.org ? > > I don't see a bug. From /usr/share/doc/puppet/NEWS.Debian.gz: > > "Handling

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Keith Edmunds
On Wed, 1 Apr 2009 06:35:04 -0700, nig...@google.com said: > Keith, can you make sure you bug report this on bugs.debian.org ? I don't see a bug. From /usr/share/doc/puppet/NEWS.Debian.gz: "Handling of the rundir setting has been changed; we now store PID files in /var/run/puppet, and the inits

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Nigel Kersten
Keith, can you make sure you bug report this on bugs.debian.org ? A few of us have joined in to help the Debian Puppet packaging project, and we're going to start churning through the reported bugs next week. On Tue, Mar 31, 2009 at 11:37 PM, Keith Edmunds wrote: > > On Tue, 31 Mar 2009 14:35

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-03-31 Thread Keith Edmunds
On Tue, 31 Mar 2009 14:35:13 -0700 (PDT), mailtrevh...@gmail.com said: > the --pidfile option is passed to start-stop-daemon when starting. I know. > and the file /var/run/puppetd.pid is created Not from /etc/init.d/puppet it isn't:

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-03-31 Thread Trevor
Hey Keith and Puppet-Users, the --pidfile option is passed to start-stop-daemon when starting. and the file /var/run/puppetd.pid is created, it just does not contain the pid. it contains $ cat /var/run/puppetd.pid $ pet$ that is not the string "pet", it is a repeat of the prompt, so some non p

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-03-31 Thread Keith Edmunds
On Tue, 31 Mar 2009 11:54:01 -0700 (PDT), mailtrevh...@gmail.com said: > "/etc/init.d/puppet stop" does not work because the /var/run/ > puppetd.pid file does not contain the pid. What do you have in /etc/puppet/puppetd.conf under [puppetd]? Anything relating to where the PID file is written? T