Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-3914

Intermittent lock file left after reboot.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Duplicate
    • Affects Version/s: PUP 3.7.3
    • Fix Version/s: None
    • Component/s: None
    • Environment:

      Windows 2008 Server R2 (Datacentre)

    • Template:
    • Epic Link:
    • Team:
      Coremunity

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              crazydave David Chute
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support