With the revert in #237071 we're back where we started in #218071: * Starting puppet ... * start-stop-daemon: /usr/bin/puppetd is a script * start-stop-daemon: and should be started, stopped or signalled with * start-stop-daemon: --exec /usr/bin/ruby18 /usr/bin/puppetd * start-stop-daemon: or you should specify a pidfile or process name * Failed to start puppet [ !! ] * ERROR: puppet failed to 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
You're using OpenRC - could you test OpenRC-9999 please? I'm sure this error should now be fixed. Also, see if --quiet can be removed from the s-s-d call - it should only be used if the daemon is chatty and there is no other way of quieting it.
fixed again.
