$ sudo /etc/init.d/puppetmaster start * Starting puppetmaster ... * start-stop-daemon: /usr/bin/puppetmasterd is a script * start-stop-daemon: and should be started, stopped or signalled with * start-stop-daemon: --exec /usr/bin/ruby18 /usr/bin/puppetmasterd * start-stop-daemon: or you should specify a pidfile or process name * Failed to start puppetmaster [ !! ] * ERROR: puppetmaster failed to start
Added upsteam ticket.
@Tais: Sorry, but the patch you reported to upstream doesn't fix anything. The problem is that /usr/bin/puppetmasterd is a script and the exec-line should therefore be: "--exec /usr/bin/ruby /usr/bin/puppetmasterd" instead of just "--exec /usr/bin/puppetmasterd"
Due to no activity I pushed my patch (without rev.bump) to the tree. I've tested it with baselayout-1 as well.
(In reply to comment #2) > @Tais: Sorry, but the patch you reported to upstream doesn't fix anything. > The problem is that /usr/bin/puppetmasterd is a script and the exec-line should > therefore be: "--exec /usr/bin/ruby /usr/bin/puppetmasterd" instead of just > "--exec /usr/bin/puppetmasterd" The patch did actually fix the problem: "* start-stop-daemon: or you should specify a pidfile or process name" Which is exactly what the patch did. Added a pidfile. And as you can see in bug #237071 - your patch broke it again.
