Your message dated Fri, 19 Oct 2012 11:09:54 +0900
with message-id
<cam0xxk_vzu4d03ce6rc5k7d1qtkygwznkkxr9nfaoqjvvbh...@mail.gmail.com>
and subject line Re: Bug#685347: puppet: init script fails starting when puppet
already started.
has caused the Debian Bug report #685347,
regarding puppet: init script fails starting when puppet already started.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
685347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685347
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: puppet
Version: 2.7.18-1
Severity: normal
Dear Maintainer,
When managing puppet under puppet, service puppet fails to start
because start-stop-daemon returns 1(process already runniing) instead of 0.
It could be fixed by adding "--oknodo" to the commandline of start-stop-daemon.
# I wonder why "stop" has "--oknodo", while "start" doesn't have.
regards,
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-11-pve (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages puppet depends on:
ii dpkg 1.16.8
ii puppet-common 2.7.18-1
ii ruby1.8 1.8.7.358-4
Versions of packages puppet recommends:
ii ruby [rdoc] 4.9
Versions of packages puppet suggests:
pn etckeeper <none>
pn puppet-el <none>
pn vim-puppet <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
hi,
On Sun, Sep 30, 2012 at 5:52 AM, Micah Anderson <[email protected]> wrote:
> Your service definition for puppet should not be run if puppet is already
> running. Can you provide me with your service definition? I suspect you do not
> have the 'hasstatus => true' set.
Yes, I haven't have the 'hasstatus',
>> It could be fixed by adding "--oknodo" to the commandline of
>> start-stop-daemon.
>> # I wonder why "stop" has "--oknodo", while "start" doesn't have.
>
> If you are running the puppet agent, and the puppet daemon is not running, and
> --oknodo is set in the initscript for start, and you have a service definition
> that attempts to start puppet, all that will happen is you will get a zero
> result code when the service definition starts and puppet wont be run a second
> time.
And I understand the problem when adding oknodo, so I close this bts.
I'm sorry for bothering you.
regards,
--
KURASHIKI Satoru
--- End Message ---
