Jim N wrote:
> I was getting this when starting puppetmasterd (puppet-
> server-0.25.5-1.el6.noarch RPM install):
>
> $ sudo /etc/init.d/puppetmaster start
> Starting puppetmaster: Could not run: Could not create PID file: /var/
> lib/puppet/run/puppetmasterd.pid
>
>
> This change in the init scrip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> This change in the init script fixed the problem:
>
> #pidfile=/var/run/puppet/puppetmasterd.pid
> pidfile=/var/lib/puppet/run/puppetmasterd.pid
>
> Is that a bug worth reporting?
I would, at least somebody can then decide if it's really a bug or
I've seen a few conflicts between RPM and Source installations relating to
path ... on an Ubuntu server, for example, the binaries landing in /usr/bin
rather than /usr/sbin. Really gets frustrating when distro / repository
maintainers move everything around "to suit their distro" -- it seems like
i
I was getting this when starting puppetmasterd (puppet-
server-0.25.5-1.el6.noarch RPM install):
$ sudo /etc/init.d/puppetmaster start
Starting puppetmaster: Could not run: Could not create PID file: /var/
lib/puppet/run/puppetmasterd.pid
This change in the init script fixed the problem:
#pidf