"/etc/init.d/puppet stop" does not work because the /var/run/ puppetd.pid file does not contain the pid. Is their some issue with / sbin/start-stop-daemon and ruby? It appears that start-stop-daemon does not git a pid back from the exec to puppetd. --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Tue, 31 Mar 2009 11:54:01 -0700 (PDT), mailtrevhere@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? The pidfile here is /var/run/puppet/puppetd.pid: $ ps -p $(cat /var/run/puppet/puppetd.pid) PID TTY TIME CMD 13459 ? 00:17:05 ruby Keith --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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 printable character is contained in /var/run/puppetd.pid It looks like exec() on puppetd is not returning a pid in the expected format from start-stop-daemon. the man page for puppetd does not list a --pidfile option. Cheers, Trevor On Mar 31, 1:28 pm, Keith Edmunds <k...@midnighthax.com> wrote:> 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? > > The pidfile here is /var/run/puppet/puppetd.pid: > > $ ps -p $(cat /var/run/puppet/puppetd.pid) > PID TTY TIME CMD > 13459 ? 00:17:05 ruby > > Keith--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Tue, 31 Mar 2009 14:35:13 -0700 (PDT), mailtrevhere@gmail.com said:> the --pidfile option is passed to start-stop-daemon when starting.I know.> and the file /var/run/puppetd.pid is createdNot from /etc/init.d/puppet it isn''t: -------------------------------------------------------------------------------- start_puppet() { start-stop-daemon --start --quiet --pidfile /var/run/puppet/$NAME.pid \ --startas $DAEMON -- $DAEMON_OPTS } -------------------------------------------------------------------------------- Hence my asking what you have under [puppetd] in /etc/puppet/puppet.conf, which you chose not to answer. If, for example, you have: rundir = /var/run ...then you will see exactly the symptoms you describe. Keith --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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 <kae@midnighthax.com> wrote:> > On Tue, 31 Mar 2009 14:35:13 -0700 (PDT), mailtrevhere@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: > > -------------------------------------------------------------------------------- > start_puppet() { > start-stop-daemon --start --quiet --pidfile /var/run/puppet/$NAME.pid \ > --startas $DAEMON -- $DAEMON_OPTS > } > -------------------------------------------------------------------------------- > > Hence my asking what you have under [puppetd] in /etc/puppet/puppet.conf, > which you chose not to answer. If, for example, you have: > > rundir = /var/run > > ...then you will see exactly the symptoms you describe. > > Keith > > > >-- Nigel Kersten nigelk@google.com System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Wed, 1 Apr 2009 06:35:04 -0700, nigelk@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 initscripts have been modified to ensure that this directory exists on startup. It is no longer necessary to set rundir explicitly in /etc/puppet/puppet.conf, and you should ensure that you have no explicit rundir setting in your puppet.conf unless you want to use a custom rundir setting for your own local purposes." Keith --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Ah. I misread the thread. Ta. On Wed, Apr 1, 2009 at 8:52 AM, Keith Edmunds <kae@midnighthax.com> wrote:> > On Wed, 1 Apr 2009 06:35:04 -0700, nigelk@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 initscripts have been modified to ensure > that this directory exists on startup. It is no longer necessary to > set rundir explicitly in /etc/puppet/puppet.conf, and you should ensure > that you have no explicit rundir setting in your puppet.conf unless you > want to use a custom rundir setting for your own local purposes." > > Keith > > > >-- Nigel Kersten nigelk@google.com System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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 <http://www.skurfer.com/> --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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 realize that instll package- doesn''t remove all the associated files. My mistake. Still not getting stop to work thought. $ sudo start-stop-daemon --stop --verbose --pidfile /var/run/puppet/ puppet.pid No process in pidfile `/var/run/puppet/puppet.pid'' found running; none killed. $ ps aux | grep -i pupp root 27804 0.0 0.8 25492 14732 ? Ssl 18:50 0:00 ruby / usr/sbin/puppetd --verbose --listen -w 120 trevor 27941 0.0 0.0 2860 692 pts/0 R+ 19:02 0:00 grep - i pupp so puppetd is not running, its sleeping. Not sure if this is the correct behavior or not. puppetd may be sleeping because it is failing to recieve a proper cert. see my other thread http://groups.google.com/group/puppet-users/browse_thread/thread/fc325274736e2500 as a side note, after apt-get install puppet-, i still head to manually rm -rf /var/lib/puppet , /etc/init.d/puppet, /etc/puppet. And after apt-get install puppet/experimental /etc/puppet/puppet.conf did not exist. if I /bin/vi /var/run/puppet/puppet.pid it contains "27804". however a /bin/cat of /var/run/puppet/puppet.pid does not print in ascii. On Apr 1, 8:54 am, Nigel Kersten <nig...@google.com> wrote:> Ah. I misread the thread. Ta. > > > > On Wed, Apr 1, 2009 at 8:52 AM, Keith Edmunds <k...@midnighthax.com> 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 of the rundir setting has been changed; we now store PID files > > in /var/run/puppet, and the initscripts have been modified to ensure > > that this directory exists on startup. It is no longer necessary to > > set rundir explicitly in /etc/puppet/puppet.conf, and you should ensure > > that you have no explicit rundir setting in your puppet.conf unless you > > want to use a custom rundir setting for your own local purposes." > > > Keith > > -- > Nigel Kersten > nig...@google.com > System Administrator > Google, Inc.--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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 your apparent lack of familiarity with Linux/Debian.> if I /bin/vi /var/run/puppet/puppet.pid it contains "27804". however > a /bin/cat of /var/run/puppet/puppet.pid does not print in ascii.I''m sorry, but that''s just rubbish. If the file contains "27804" then "cat file" will print 27804. 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. Keith --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Rob McBroom <puppet@skurfer.com> 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 can install the package from Debian unstable directly on stable, which has always been the case, it''s against the policy of backports.org to accept an upload. There''s more information on backports.org. -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/> --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Nigel Kersten <nigelk@google.com> 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 this! -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/> --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
2009/4/1 Keith Edmunds <kae@midnighthax.com>> > 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.Keith I didn''t raise this issue, but I''m seeing what might be a similar behaviour: glaw@dv01:~ $ ps -ef | grep [p]uppetd root 32599 1 0 Mar26 ? 00:33:23 ruby /usr/sbin/puppetd -w 5 glaw@dv01:~ $ sudo /etc/init.d/puppet stop Stopping puppet configuration management tool. glaw@dv01:~ $ ps -ef | grep [p]uppetd root 32599 1 0 Mar26 ? 00:33:23 ruby /usr/sbin/puppetd -w 5 glaw@dv01:~ $ ls /var/run/puppet/ glaw@dv01:~ $ cat /etc/puppet/puppet.conf [puppetd] server=sxvx01.garylaw.net glaw@dv01:~ $ sudo killall ruby glaw@dv01:~ $ ls /var/run/puppet/ glaw@dv01:~ $ ps -ef | grep [p]uppetd glaw@dv01:~ $ sudo /etc/init.d/puppet start Starting puppet configuration management tool. glaw@dv01:~ $ ls /var/run/puppet/ glaw@dv01:~ $ ps -ef | grep [p]uppetd root 22693 1 12 21:56 ? 00:00:03 ruby /usr/sbin/puppetd -w 5 glaw@dv01:~ $ puppet --version 0.24.5 Basically, the stop argument doesn''t seem to work, and AFAIK nothing gets written to /var/run/puppet. Start works OK. Debian version is Lenny. I''m not a total Debian newbie, but frankly it''s not really my comfort zone either, so I might be the problem here, not the package. Gary -- Gary Law Email: garylaw@garylaw.net Chat googletalk/messenger: gary.law@gmail.com iChat/jabber/AIM: gary.law@mac.com --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Thu, 2 Apr 2009 22:06:22 +0100, gary.law@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 --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
2009/4/2 Keith Edmunds <kae@midnighthax.com>> > On Thu, 2 Apr 2009 22:06:22 +0100, gary.law@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 >glaw@dv01:~ $ dpkg -l | grep puppet ii puppet 0.24.5-3 centralised configuration management for net rc puppetmaster 0.24.5-3 centralised configuration management control glaw@dv01:~ $ cat /etc/puppet/puppet.conf [puppetd] server=sv01.garylaw.net -- Gary Law Email: garylaw@garylaw.net Chat googletalk/messenger: gary.law@gmail.com iChat/jabber/AIM: gary.law@mac.com --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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 be
running.
Once they''ve all stopped, start puppet ("/etc/init.d/puppet
start") and
see if you have a /var/run/puppet/puppetd.pid file.
Keith
--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
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 PM, Keith Edmunds <kae@midnighthax.com> wrote:> > 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 be running. > Once they''ve all stopped, start puppet ("/etc/init.d/puppet start") and > see if you have a /var/run/puppet/puppetd.pid file. > > Keith > > > >--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
2009/4/2 Keith Edmunds <kae@midnighthax.com>> > 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 be running. > Once they''ve all stopped, start puppet ("/etc/init.d/puppet start") and > see if you have a /var/run/puppet/puppetd.pid file. >Here''s some more detailed debugging. Stop still isn''t working, but there is a pid file and it seems to have the right pid in it:- glaw@dv01:/ $ ls -ld /var/puppet/run drwxrwxrwt 2 root root 4096 2009-04-03 17:52 /var/puppet/run glaw@dv01:/ $ ps -ef | grep [p]uppet root 30545 1 5 17:52 ? 00:00:04 ruby /usr/sbin/puppetd -w 5 glaw@dv01:/ $ sudo killall ruby glaw@dv01:/ $ ps -ef | grep [p]uppet glaw@dv01:/ $ sudo /etc/init.d/puppet start Starting puppet configuration management tool. glaw@dv01:/ $ ps -ef | grep [p]uppet root 30642 1 24 17:53 ? 00:00:00 ruby /usr/sbin/puppetd -w 5 glaw@dv01:/ $ sudo /etc/init.d/puppet stop Stopping puppet configuration management tool. glaw@dv01:/ $ ps -ef | grep [p]uppet root 30642 1 7 17:53 ? 00:00:02 ruby /usr/sbin/puppetd -w 5 glaw@dv01:/ $ ls -l /var/puppet/run total 4 -rw-r--r-- 1 root root 5 2009-04-03 17:53 puppetd.pid glaw@dv01:/ $ cat /var/puppet/run/puppetd.pid 30642glaw@dv01:/ $ sudo kill $(cat /var/puppet/run/puppetd.pid ) glaw@dv01:/ $ ps -ef | grep [p]uppet glaw@dv01:/ $ I can''t see any obvious reason why this isn''t working Gary -- Gary Law Email: garylaw@garylaw.net Chat googletalk/messenger: gary.law@gmail.com iChat/jabber/AIM: gary.law@mac.com --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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/templates [puppetd] server=puppetmaster.domain.co.uk environments=production,testing,development Regards Martin On Fri, Apr 3, 2009 at 9:05 AM, Martin Wheldon <mwheldon@googlemail.com> wrote:> 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 PM, Keith Edmunds <kae@midnighthax.com> wrote: >> >> 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 be running. >> Once they''ve all stopped, start puppet ("/etc/init.d/puppet start") and >> see if you have a /var/run/puppet/puppetd.pid file. >> >> Keith >> >> >> >> >--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Fri, Apr 03, 2009 at 05:58:45PM +0100, Gary Law wrote:> glaw@dv01:/ $ sudo /etc/init.d/puppet stop[...]> I can''t see any obvious reason why this isn''t workingsudo bash -x /etc/init.d/puppet stop might be enlightening.. -- Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
2009/4/4 Marcin Owsiany <marcin@owsiany.pl>> > On Fri, Apr 03, 2009 at 05:58:45PM +0100, Gary Law wrote: > > glaw@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.... glaw@dv01:~ $ ps -ef | grep [p]uppet root 6774 1 0 Apr04 ? 00:06:49 ruby /usr/sbin/puppetd -w 5 glaw@dv01:~ $ sudo bash -x /etc/init.d/puppet stop + PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin + DAEMON=/usr/sbin/puppetd + DAEMON_OPTS+ NAME=puppetd + DESC=''puppet configuration management tool'' + test -x /usr/sbin/puppetd + ''['' -r /etc/default/puppet '']'' + . /etc/default/puppet ++ START=yes ++ DAEMON_OPTS=''-w 5'' + . /lib/lsb/init-functions ++ FANCYTTY++ ''['' -e /etc/lsb-base-logging.sh '']'' ++ true + ''['' ''!'' -d /var/run/puppet '']'' + chown puppet:puppet /var/run/puppet + case "$1" in + log_begin_msg ''Stopping puppet configuration management tool'' + ''['' -z ''Stopping puppet configuration management tool'' '']'' + echo -n ''Stopping puppet configuration management tool'' Stopping puppet configuration management tool+ stop_puppet + start-stop-daemon --stop --quiet --pidfile /var/run/puppet/puppetd.pid + log_end_msg 0 + ''['' -z 0 '']'' + retval=0 + log_end_msg_pre 0 + : + log_use_fancy_output + TPUT=/usr/bin/tput + EXPR=/usr/bin/expr + ''['' -t 1 '']'' + ''['' xxterm-color ''!='' '''' '']'' + ''['' xxterm-color ''!='' xdumb '']'' + ''['' -x /usr/bin/tput '']'' + ''['' -x /usr/bin/expr '']'' + /usr/bin/tput hpa 60 + FANCYTTY=0 + case "$FANCYTTY" in + false + RED+ YELLOW+ NORMAL+ ''['' 0 -eq 0 '']'' + echo . . + log_end_msg_post 0 + : + return 0 + exit 0 glaw@dv01:~ $ glaw@dv01:~ $ ps -ef | grep [p]uppet root 6774 1 0 Apr04 ? 00:06:49 ruby /usr/sbin/puppetd -w 5 Hope you can make sense of that... Gary -- Gary Law Email: garylaw@garylaw.net Chat googletalk/messenger: gary.law@gmail.com iChat/jabber/AIM: gary.law@mac.com --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Mon, Apr 06, 2009 at 10:50:17AM +0100, Gary Law wrote:> + start-stop-daemon --stop --quiet --pidfile /var/run/puppet/puppetd.pid[...]> glaw@dv01:~ $ ps -ef | grep [p]uppet > root 6774 1 0 Apr04 ? 00:06:49 ruby /usr/sbin/puppetd -w 5Try: start-stop-daemon --stop --pidfile /var/run/puppet/puppetd.pid --verbose Maybe it will be more helpful. Manual page start-stop-daemon(8): -K, --stop Checks for the existence of a specified process. If such a pro‐ cess exists, start-stop-daemon sends it the signal specified by --signal, and exits with error status 0. If such a process does not exist, start-stop-daemon exits with error status 1 (0 if --oknodo is specified). If --retry is specified then start-stop-daemon will check that the process(es) have termi‐ nated. -p, --pidfile pid-file Check whether a process has created the file pid-file. My guess would be that you need more arguments, perhaps "--name"? -- Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
2009/4/6 Marcin Owsiany <marcin@owsiany.pl>> > On Mon, Apr 06, 2009 at 10:50:17AM +0100, Gary Law wrote: > > + start-stop-daemon --stop --quiet --pidfile /var/run/puppet/puppetd.pid > [...] > > glaw@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 /var/run/puppet/puppetd.pid --verbose >dv01:~# ps -ef | grep [p]uppet root 28518 1 0 18:52 ? 00:00:16 ruby /usr/sbin/puppetd -w 5 dv01:~# cat /var/puppet/run/puppetd.pid 28518dv01:~# dv01:~# start-stop-daemon --stop --pidfile /var/run/puppet/puppetd.pid --verbose No process in pidfile `/var/run/puppet/puppetd.pid'' found running; none killed. dv01:~# cat /var/puppet/run/puppetd.pid 28518dv01:~# dv01:~# kill $(!cat) kill $(cat /var/puppet/run/puppetd.pid ) dv01:~# ps -ef | grep [p]uppet dv01:~# so it seems the start-stop-daemon doesn''t like the pid file for reasons I cannot explain. Missing trailing CR? But that''s very common in pid files AFAIK. Gary -- Gary Law Email: garylaw@garylaw.net Chat googletalk/messenger: gary.law@gmail.com iChat/jabber/AIM: gary.law@mac.com --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Wed, Apr 08, 2009 at 07:44:07PM +0100, Gary Law wrote:> 2009/4/6 Marcin Owsiany <marcin@owsiany.pl> > > > > > On Mon, Apr 06, 2009 at 10:50:17AM +0100, Gary Law wrote: > > > + start-stop-daemon --stop --quiet --pidfile /var/run/puppet/puppetd.pid > > [...] > > > glaw@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 /var/run/puppet/puppetd.pid --verbose > > > > dv01:~# ps -ef | grep [p]uppet > root 28518 1 0 18:52 ? 00:00:16 ruby /usr/sbin/puppetd -w 5 > dv01:~# cat /var/puppet/run/puppetd.pid > 28518dv01:~# > dv01:~# start-stop-daemon --stop --pidfile /var/run/puppet/puppetd.pid > --verbose > No process in pidfile `/var/run/puppet/puppetd.pid'' found running; none > killed. > dv01:~# cat /var/puppet/run/puppetd.pid > 28518dv01:~# > dv01:~# kill $(!cat) > kill $(cat /var/puppet/run/puppetd.pid ) > dv01:~# ps -ef | grep [p]uppet > dv01:~# > > so it seems the start-stop-daemon doesn''t like the pid file for reasons I > cannot explain. Missing trailing CR?A quick look at the source code shows it does not pay attention to line termination at all. However looking at the utils/start-stop-daemon.c:check(pid_t pid) function, it seems that just --pidfile should be enough, unless this is debian on something else than Linux, HP-UX, HURD, FreeBSD or NetBSD? (As in that case the function would simply be a no-op). Please try with --test, it might print more useful debugging info. -- Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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 this is happening.
from the init script:
start_puppet() {
start-stop-daemon --start --quiet --pidfile
/var/run/puppet/$NAME.pid \
--startas $DAEMON -- $DAEMON_OPTS
}
This is on a freshly built machine with latest puppet from apt-get.
Any thoughts Marcin? Anyone?
Cheers
Gary
--
Gary Law
Email: garylaw@garylaw.net
Chat googletalk/messenger: gary.law@gmail.com
iChat/jabber/AIM: gary.law@mac.com
--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
Gary Law <gary.law@gmail.com> 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 \ > --startas $DAEMON -- $DAEMON_OPTS > }That flag doesn''t say where to write the PID file. It tells start-stop-daemon where puppetd *will* write the PID file. You still have to configure puppetd elsewhere (in puppet.conf, specifically) to put the PID file there. Everyone seems to get confused about what the --pidfile option to start-stop-daemon does. It doesn''t create anything at all. It just says where to find something that the daemon is creating. -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/> --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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.> You still > have to configure puppetd elsewhere (in puppet.conf, specifically) to > put the PID file there.Exactly. I''d expect that the packager has taken care about such details as configuring puppet and the init script to look in the same place. I''d file a bug if that has not been done properly. -- Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
2009/5/3 Russ Allbery <rra@stanford.edu>> > Gary Law <gary.law@gmail.com> 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 \ > > --startas $DAEMON -- $DAEMON_OPTS > > } > > That flag doesn''t say where to write the PID file. It tells > start-stop-daemon where puppetd *will* write the PID file. You still > have to configure puppetd elsewhere (in puppet.conf, specifically) to > put the PID file there. > > Everyone seems to get confused about what the --pidfile option to > start-stop-daemon does. It doesn''t create anything at all. It just > says where to find something that the daemon is creating. >Guess my Debian newbiness shining through there :) Thanks for the explanation. Gary -- Gary Law Email: garylaw@garylaw.net Chat googletalk/messenger: gary.law@gmail.com iChat/jabber/AIM: gary.law@mac.com --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---