Jira (PUP-5264) Agent service status wrong on CentOS 6
Title: Message Title Matthaus Owens commented on PUP-5264 Re: Agent service status wrong on CentOS 6 So the service provider on centos 6 relies on the status command to decide if the service is running. Because your puppet service is returning 2, puppet thinks it isn't running and tries to start it. So figuring out why the status command is returning 2 here is the key. Dead but subsys locked probably means the pidfile is empty. What are the contents of /var/run/puppetlabs/agent.pid ? 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.
Jira (PUP-5264) Agent service status wrong on CentOS 6
Title: Message Title Dirk Heinrichs commented on PUP-5264 Re: Agent service status wrong on CentOS 6 That was the right hint. Looks like I have the PID in /var/run/puppet/agent.pid, not in /var/run/puppetlabs/agent.pid. Short investigation showed that puppet.conf had the wrong paths for some dirs. 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.
Jira (PUP-5264) Agent service status wrong on CentOS 6
Title: Message Title Matthaus Owens commented on PUP-5264 Re: Agent service status wrong on CentOS 6 Dirk Heinrichs I'm unable to reproduce this on a fresh centos 6 install. Can you add the output of `service puppet status` (as well as the return code) please? Also a run of `/opt/puppetlabs/bin/puppet resource service puppet ensure=running enable=true --verbose --trace --debug` would be helpful to see what's going on. 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.
Jira (PUP-5264) Agent service status wrong on CentOS 6
Title: Message Title Dirk Heinrichs commented on PUP-5264 Re: Agent service status wrong on CentOS 6 Works fine on Ubuntu 14.04, though. 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.
Jira (PUP-5264) Agent service status wrong on CentOS 6
Title: Message Title Dirk Heinrichs created an issue Puppet / PUP-5264 Agent service status wrong on CentOS 6 Issue Type: Bug Affects Versions: puppet-agent 1.2.4 Assignee: Unassigned Created: 2015/09/17 1:23 AM Environment: CentOS Linux 6 Priority: Normal Reporter: Dirk Heinrichs A service resource for managing the Puppet agent service tries to change it from stopped to running, although it already runs: # ps -ef|grep [Pp]uppet root 20951 1 0 10:06 ?00:00:00 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent
