Jira (PUP-911) Puppet silent about inability to acquire pidlock

[Eric Sorenson (JIRA)]

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)

[Eric Sorenson (JIRA)]

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

[Sean McDonald (JIRA)]

Sean McDonald updated an issue

Puppet / PUP-911

Puppet silent about inability to acquire pidlock

Change By: Sean McDonald Labels: triaged

Add Comment

[Moses Mendoza (JIRA)]

Moses Mendoza updated an issue

Puppet / PUP-911 Puppet silent about inability to acquire pidlock

Change By: Moses Mendoza Labels: triaged

Add Comment

[Josh Cooper (JIRA)]

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)

[Josh Cooper (JIRA)]

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

[Michael Speth (JIRA)]

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 root 1593 0.0 1.2 347544 49536 ? Ssl Feb19 1:19 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent --no-daemonize sudo apt list puppet-agent Listing... Done puppet-agent/xenial,now 6.13.0-1xenial amd64 [installed] Is this related to the issue here? Any ideas how to solve as all of my vms agents are stuck due to this issue.

Add Comment