Jira (PUP-3914) Intermittent lock file left after reboot.

[David (JIRA)]

Title: Message Title

David created an issue   Puppet / PUP-3914 Intermittent lock file left after reboot. Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Kylo Ginsberg Components: Client Created: 2015/01/27 8:14 AM Environment: Windows 2008 Server R2 (Datacentre) Fix Versions: PUP 3.7.4 Labels: windows puppet-agent Priority: Normal Reporter: David We have our own module that can trigger a reboot of the windows client. This basically boils down to this; c:\\windows\\system32\\shutdown.exe /r /t 15 /c ..... After the reboot has completed we sometimes see the puppet (agent) lock file remains and the agent process is not started/aborts. Error message; Run of Puppet configuration client already in progress; skipping (C:/ProgramData/PuppetLabs/puppet/var/state/agent_catalog_run.lock exists) In the example I'm looking at I can see a different unrelated process occupying the pid of the original (pre reboot) puppet agent process. So I suspect that is preventing the automatic cleanup of the lock file. And hence is the explanation of the intermittent nature of the bug. I am new to this project and I am not a ruby coder, but I can have a go. But I would appreciate validation of the bug and also some pointers to where in the code base I can find where the lock file clean up is done. Add Comment   This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.