[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Incorrect start script for ruby193-mcollective



In /etc/init.d/ruby193-mcollective.  See the start function.  I modified line 53 to be

daemon ${daemonopts} ${mcollectived} --pidfile "${pidfile}" --config "/opt/rh/ruby193/root/etc/mcollective/server.cfg"


On Wed, Jul 30, 2014 at 12:52 PM, N. Harrison Ripps <hripps redhat com> wrote:

> On Jul 30, 2014, at 12:48, Kevin Conaway <kevin conaway gmail com> wrote:
>
> After installing mcollective on my node host, I noticed that the status for mcollective would always show "stopped" when I queried it with service ruby193-mcollective status.
>
> There are 2 problems with the start script:
>
> 1.) The pid file argument is currently "pid", it should be "pidfile"

Where specifically? Can you paste the content?

> 2.) The pid file gets created in /opt/rh/ruby193/root/var/run/.  On my system, the run directory did not exist in /opt/rh/ruby193/root/var/ so I had to create it for this to work right.

That is a problem that has been fixed in the latest puppet module. However, the root cause is not known, as this directory is part of the RPM manifest for ruby193-mcollective.

>
> Making those 2 changes fixed the issue.
> _______________________________________________
> dev mailing list
> dev lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]