Bug #6023

puppetmasterd init.d does not create PID file causes failure on status & stop

Added by Chip Schweiss over 1 year ago. Updated 4 months ago.

Status:Accepted Start date:01/26/2011
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:Red Hat
Target version:2.7.x
Affected Puppet version:2.6.4 Branch:
Keywords:
Votes: 0

Description

From the tar.gz in conf/redhat/server.init line number 60:

daemon $daemonopts $PUPPETMASTER $PUPPETMASTER_OPTS

should be

daemon $PUPPETMASTER $PUPPETMASTER_OPTS $daemonopts

History

#1
Updated by Nigel Kersten over 1 year ago

  • Target version changed from 2.6.5 to 2.6.x

#2
Updated by Nigel Kersten over 1 year ago

  • Status changed from Unreviewed to Accepted

#3
Updated by James Turnbull over 1 year ago

  • Target version changed from 2.6.x to 2.6.6

#4
Updated by Todd Zullinger about 1 year ago

Hi Chip,

$daemonopts is in the right place. It holds options that are passed to the daemon function from /etc/init.d/functions, so it belongs before $PUPPETMASTER $PUPPETMASTER_OPTS. Perhaps you can show us the output you get so we can help find the source of your issue? First, just the output of service puppetmaster status would be good. For more copious output, sh -x /etc/init.d/puppetmaster status may be helpful.

Thanks.

#5
Updated by James Turnbull about 1 year ago

  • Target version changed from 2.6.6 to 2.6.x

#6
Updated by Michael Stahnke 4 months ago

  • Target version changed from 2.6.x to 2.7.x

2.6.x is closed. Moving to 2.7.x

#7
Updated by Todd Zullinger 4 months ago

Without input from Chip or someone else seeing a problem, I’d be inclined to close this one. Odds are good that if there is a problem, it’s due to bugs in an older initscripts package. Chip, can you provide more details as to what the problem is (perhaps including some output per comment 4)?

Also available in: Atom PDF