Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title Michael Speth commented on PUP-911 Re: Puppet silent about inability to acquire pidlock Josh Cooper I am having this problem since migrating from puppet 5 to puppet 6. Issuing the following command: sudo puppet agent --noop --debug --verbose Results in Error: Could not run: Could not create PID file: /var/run/puppetlabs/agent.pid And doing a sudo service puppet status results in Feb 26 16:08:25 jira-test-03 puppet-agent[1593]: Shutdown/restart in progress (:restart_requested); skipping run Addition information: ll /var/run/puppetlabs/agent.pid -rw-r--r-- 1 root root 4 Feb 19 15:39 /var/run/puppetlabs/agent.pid ps auwx | grep puppet
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title Josh Cooper commented on PUP-911 Re: Puppet silent about inability to acquire pidlock Puppet no longer attempts to acquire the lock when reporting the version, closing this: root@yellow-outrage:~# systemctl start puppet root@yellow-outrage:~# puppet agent --version 6.12.0 root@yellow-outrage:~# echo $? 0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title Josh Cooper updated an issue Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Moses Mendoza Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title Sean McDonald updated an issue Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Sean McDonald Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title Eric Sorenson commented on PUP-911 Re: Puppet silent about inability to acquire pidlock I'm triaging old bugs and came across this one. Assigning to Agent & Platform for further investigation. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Eric Sorenson Team: Agent & Platform Support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title
Daniel Dreier commented on an issue
Re: Puppet silent about inability to acquire pidlock
Scratch that - my approach to fixing it won't work. Marking the issue open again.
Add Comment
Puppet / PUP-911
Puppet silent about inability to acquire pidlock
The {{--verbose}} flag does tell the user that something has happened, but without it there isn't any indication. I would expect the error to always show up (even without verbose) and a non-zero exit status. {noformat} root@debian-607-x64-vf503-nocm:~# puppet agent --verbose Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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-911) Puppet silent about inability to acquire pidlock
Title: Message Title Daniel Dreier assigned an issue to Daniel Dreier Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Daniel Dreier Assignee: DanielDreier Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-911) Puppet silent about inability to acquire pidlock
Title: Message Title
Daniel Dreier commented on an issue
Re: Puppet silent about inability to acquire pidlock
It looks like the cause of this is that in daemon.rb, create_pidfile gets called after the daemon forks. As a result, the exit code you'll get is always 0 because the exception happened in the forked process and not the one that you're getting a return code from.
I'm working on a pull request; it looks like simply re-ordering the two works but I need to figure out how to test for this issue.
Add Comment
Puppet / PUP-911
Puppet silent about inability to acquire pidlock
The {{--verbose}} flag does tell the user that something has happened, but without it there isn't any indication. I would expect the error to always show up (even without verbose) and a non-zero exit status. {noformat} root@debian-607-x64-vf503-nocm:~# puppet agent --verbose Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title
Josh Cooper commented on an issue
Re: Puppet silent about inability to acquire pidlock
Pretty sure there is a ticket already about how some failures don't get logged prior to the agent daemonizing. Don't know the ticket offhand, Joshua Partlow might remember.
Add Comment
Puppet / PUP-911
Puppet silent about inability to acquire pidlock
The {{--verbose}} flag does tell the user that something has happened, but without it there isn't any indication. I would expect the error to always show up (even without verbose) and a non-zero exit status. {noformat} root@debian-607-x64-vf503-nocm:~# puppet agent --verbose Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title
Daniel Dreier commented on an issue
Re: Puppet silent about inability to acquire pidlock
I've submitted pull request 2774 to try and fix this. I wasn't able to find other tickets on similar topics but I'd be very curious if somebody can dig them up. In the meantime, the fix is to move one line up so we really might as well.
Add Comment
Puppet / PUP-911
Puppet silent about inability to acquire pidlock
The {{--verbose}} flag does tell the user that something has happened, but without it there isn't any indication. I would expect the error to always show up (even without verbose) and a non-zero exit status. {noformat} root@debian-607-x64-vf503-nocm:~# puppet agent --verbose Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Daniel Dreier Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-911) Puppet silent about inability to acquire pidlock
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Daniel Dreier Priority: Normal Minor Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-911) Puppet silent about inability to acquire pidlock
Title: Message Title
Daniel Dreier commented on an issue
Re: Puppet silent about inability to acquire pidlock
I've confirmed this behavior on puppet 3.6.2 on Centos 6.5.
[root@centos-65-latest ~]# service puppet stop
Stopping puppet agent: [ OK ]
[root@centos-65-latest ~]# service puppet start
Starting puppet agent: [ OK ]
[root@centos-65-latest ~]# puppet agent --verbose
Warning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
(at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1095:in `issue_deprecations')
Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid
[root@centos-65-latest ~]# echo $?
0
[root@centos-65-latest ~]# puppet --version
3.6.2
Add Comment
Puppet / PUP-911
Puppet silent about inability to acquire pidlock
The {{--verbose}} flag does tell the user that something has happened, but without it there isn't any indication. I would expect the error to always show up (even without verbose) and a non-zero exit status. {noformat} root@debian-607-x64-vf503-nocm:~# puppet agent --verbose Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Daniel Dreier Affects Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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.
