The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
mcollective does not honor identity setting
|Assignee:||Matthaus Owens||% Done:|
|Target version:||Commercial edition - PE 2.5.x|
|Keywords:||mcollective service init script identity quality||Affected URL:|
|Branch:||Affected PE version:||2.5.1|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.
Resetting the identity setting option does not cause MCollective in Puppet Enterprise to identify itself using the new name.
2.7.12 (Puppet Enterprise 2.5.1)
- Debian 6.0.5 Squeeze
I think this is a problem with the service startup script. The restart actions takes a LONG time but doesn’t appear to actually restart the daemon since the identity does not change.
In addition, the stop action simply fails:
root@gw-jeff:~# /etc/init.d/pe-mcollective stop Stopping mcollective daemon failed!
Manually killing the PID and then issuing /etc/init.d/pe-mcollective start appears to fix the identity issue.
So, I think this is just an issue with the service script being broken.
#2 Updated by Jeff McCune almost 2 years ago
Does not restart¶
I just verified that
/etc/init.d/pe-mcollective restart doesn’t actually restart the daemon.
root@gw-nan:~# ps auxww | grep ruby root 1572 0.0 4.5 113020 11304 ? Sl 15:08 0:01 /opt/puppet/bin/ruby /opt/puppet/sbin/mcollectived --pid /var/run/pe-mcollective.pid root 1627 0.2 26.6 184600 66820 ? Ss 15:08 0:02 /opt/puppet/bin/ruby1.8 /opt/puppet/bin/puppet agent root 4594 0.0 0.3 7548 860 pts/0 S+ 15:28 0:00 grep ruby root@gw-nan:~# /etc/init.d/pe-mcollective restart Restarting mcollective daemon. root@gw-nan:~# ps auxww | grep ruby root 1572 0.0 4.5 113020 11304 ? Sl 15:08 0:01 /opt/puppet/bin/ruby /opt/puppet/sbin/mcollectived --pid /var/run/pe-mcollective.pid root 1627 0.2 26.7 184600 66952 ? Ss 15:08 0:02 /opt/puppet/bin/ruby1.8 /opt/puppet/bin/puppet agent root 4613 0.0 0.3 7548 856 pts/0 R+ 15:29 0:00 grep ruby
#3 Updated by Jeff McCune almost 2 years ago
- Keywords changed from mcollective service init script identity to mcollective service init script identity quality
Is there a way we track looping issues? This seems to come up a lot with the debian style init scripts, but I’m not sure if that’s actually true or not.
#4 Updated by Matthaus Owens almost 2 years ago
- Status changed from Unreviewed to Needs More Information
We updated the init script in 2.5.2 to
start-stop-daemon -K -q -R -TERM/30/KILL/5 -o -p $PIDFILE from
start-stop-daemon -K -q -R -TERM/30 -o -p $PIDFILE, so I’m pretty sure that will resolve this issue. I’ve had trouble reproducing such a hung state for pe-mcollective as a test case, although I have seen it many times.
Jeff, can you see if the init script from the updated pe-mcollective package still has that problem (https://github.com/puppetlabs/pe-deb-mcollective/blob/debian/debian/pe-mcollective.init)?