Jira (PUP-5232) Problem of pidfile with the mcollective service

[Francois Lafont (JIRA)]

Title: Message Title

Francois Lafont created an issue   Puppet / PUP-5232 Problem of pidfile with the mcollective service Issue Type: Bug Affects Versions: puppet-agent 1.2.2 Assignee: Unassigned Components: AIO, Platform Created: 2015/09/13 6:27 AM Environment: Ubuntu Trusty 14.02 Labels: AIO puppet-agent package Priority: Normal Reporter: Francois Lafont Hi, It's not a problem really concerning mcollective but rather its packaging in the AIO package puppet-agent. Here is the easy way to reproduce the problem on Ubuntu Trusty. It just consists in a quick and basic installation: # Basic installation root@client-trusty:~# wget http://apt.puppetlabs.com/puppetlabs-release-pc1-trusty.deb root@client-trusty:~# dpkg -i puppetlabs-release-pc1-trusty.deb root@client-trusty:~# apt-get update && apt-get install puppet-agent -y   # mcollective service and puppet service are enabled. root@client-trusty:~# ls /etc/rc?.d | grep -E '(mcollective|puppet)' K20mcollective K20puppet K20mcollective K20puppet S20mcollective S20puppet S20mcollective S20puppet S20mcollective S20puppet S20mcollective S20puppet K20mcollective K20puppet root@client-trusty:~#   # mcollective service and puppet service are currently "not running". root@client-trusty:~# ps aux | grep -E '(mcollectiv[e]|agen[t])' root@client-trusty:~#   # Now I reboot... root@client-trusty:~# reboot && exit After the reboot: # Now mcollective service and puppet service are currently "running". root@client-trusty:~# ps aux | grep -E '(mcollectiv[e]|agen[t])' root 763 0.1 3.6 234664 18108 ? Sl 14:12 0:00 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived --pid=/var/run/puppetlabs/mcollectived.pid --config=/etc/puppetlabs/mcollective/server.cfg --daemonize root 787 3.0 7.5 215004 38044 ? Ssl 14:12 0:01 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent root@client-trusty:~#   root@client-trusty:~# service puppet status * agent is running root@client-trusty:~#     # But there is something wrong with the "mcollective" service. root@client-trusty:~# service mcollective status * mcollective is not running root@client-trusty:~#   # The pid file is empty. root@client-trusty:~# echo -n 'pid=['; cat /var/run/puppetlabs/mcollectived.pid; echo ']' pid=[] root@client-trusty:~# I have a similar problem if I want to disable the puppet service and keep the mcollective service enabled: # Now, I want to disable the "puppet" service and keep enabled the mcollective service. root@client-trusty:~# update-rc.d puppet disable   root@client-trusty:~# reboot && exit And after the reboot: # Now just "mcollective" is just running. root@client-trusty:~# ps aux | grep -E '(mcollectiv[e]|agen[t])' root 777 0.0 3.6 234664 18072 ? Sl 14:18 0:00 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived --pid=/var/run/puppetlabs/mcollectived.pid --config=/etc/puppetlabs/mcollective/server.cfg --daemonize root@client-trusty:~#   # But already a problem with the "mcollective" daemon. root@client-trusty:~# service mcollective status touch: cannot touch '/var/run/puppetlabs/mcollectived.pid': No such file or directory * mcollective is not running root@client-trusty:~#   # The /var/run/puppetlabs directory no longer exists so # the pid file /var/run/puppetlabs/mcollectived.pid doesn't exist. root@client-trusty:~# ls -la /var/run/puppetlabs ls: cannot access /var/run/puppetlabs: No such file or directory root@client-trusty:~# Currently, I use this workaround which works well. I edit the file /etc/default/mcollective like this: #START=true #DAEMON_OPTS="--pid ${pidfile}" pidfile="/var/run/mcollectived-puppetlabs.pid" daemonopts="--pid=${pidfile} --config=/etc/puppetlabs/mcollective/server.cfg" By the way, it seems to me that the content of the file /etc/default/mcollective provided by the puppet-agent package is irrelevant. Here is the content by default (out of the box from the package): START=true DAEMON_OPTS="--pid ${pidfile}" It seems to me irrelevant because the START and DAEMON_OPTS variables don't exist at all in the file /etc/init.d/mcollective. Regards. François Lafont Add Comment   This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.