1 2 Previous Next 24 Replies Latest reply on Mar 25, 2016 10:25 AM by Mike Reider

    BLDeploy error

    Jim Campbell

      On a few servers we see an issue where deploy jobs stop working with a similar error.  Most of the time this occurs on servers we use a BLPackage to reboot frequently (mostly once a day).  The package is just a simple windows command to log the time and then a 'reboot after item deployment'.

       

      The entry in the transaction log (repeated many times):

       

      04/24/12 08:20:42.915 DEBUG    bldeploy - AcquireLock failed: C:\Program Files\BMC Software\BladeLogic\8.0\RSCD\Transactions\locks\writer.lck in use: Will wait and attempt again

      04/24/12 08:20:42.915 ERROR    bldeploy - BlLock::ValidatePIDActive: Cannot check validity of process. OpenProcess error="Access is denied.

      04/24/12 08:20:43.445 DEBUG    bldeploy - _bl_get_proc_list did not return a valid list. User permissions may not allow access, switching to ValidatePIDActive(PID) function

       

      The agents are 8.1sp3patchlevel1 but this has occurred in the past with 8.1sp1 and 8.0sp7 agents as well.  Restarting the rscd service does not help and the only thing that seems to 'fix' the problem is a server reboot.  After a reboot the problem does not seem to occur and deploy packages continue to work without issue.

        • 1. Re: BLDeploy error

          I can just add that I had same problem on a critical production server, that was surpose to up again 08:00.

           

          RSCD Version 8.1.0.295

           

          Info Sep 11, 2012 7:52:08 AM Deploy Dry Run Job (Pre-Execute):WSUS_Reboot; Server:xxxartjp1.xxx.yyyyyy.zzz;  PkgID:"WSUS_NoBo-2001246.1-2003013.5"; UUID:ba90aebaa7823b2f8fba02db123190db 

          Info Sep 11, 2012 7:52:08 AM Started running the deploy step job 'WSUS_Reboot->WSUS_Reboot' on application server 'xxxblapp1p'(2,000,000) against target server 'xxxartjp1.xxx.yyyyyy.zzz' 

          Info Sep 11, 2012 7:52:09 AM Reboot is not allowed

          Info Sep 11, 2012 7:52:10 AM Package "WSUS_NoBo" UUID(ba90aebaa7823b2f8fba02db123190db) started 

          Warning Sep 11, 2012 7:54:12 AM WaitForLock exiting wait because of TimeCheck exceeded

          Error Sep 11, 2012 7:54:12 AM BlLock::ValidatePIDActive: Cannot check validity of process. OpenProcess error="Access is denied.

          Error Sep 11, 2012 7:54:12 AM "

          Error Sep 11, 2012 7:54:13 AM BlLock::ValidatePIDActive: Cannot check validity of process. OpenProcess error="Access is denied.

          Error Sep 11, 2012 7:54:13 AM "

          Info Sep 11, 2012 7:54:13 AM Package "WSUS_NoBo" UUID(ba90aebaa7823b2f8fba02db123190db) initialized, entering wait queue for processing 

          Error Sep 11, 2012 7:55:13 AM BlLock::ValidatePIDActive: Cannot check validity of process. OpenProcess error="Access is denied.

          Error Sep 11, 2012 7:55:13 AM "

          Error Sep 11, 2012 7:55:14 AM BlLock::ValidatePIDActive: Cannot check validity of process. OpenProcess error="Access is denied.

          Error Sep 11, 2012 7:55:14 AM "

          Error Sep 11, 2012 7:56:14 AM BlLock::ValidatePIDActive: Cannot check validity of process. OpenProcess error="Access is denied.

          • 2. Re: BLDeploy error

            Essentially this may happen for deploy jobs that reboot the server in the middle of the job.

            Deploy Job starts executing and bldeploy.exe is assigned some pid; this pid info is written to locks/writer.lck file. The deploy job reboots the server in the middle of the job. Once the server is rebooted, the job wants to resume, and it sees the write.lck file. If the file is present, then the deploy job needs to validate if the .exe with the pid number in the file is already running or not. If after the reboot, there was another system process started that happened to pick up this pid for itself (which is possible), then bladelogic agent does not have the rights and cannot determine the process name for this pid. the job cannot proceed until this information is obtained, so you end up with a failure.

            ERROR    bldeploy - BlLock::ValidatePIDActive: Cannot check validity of process. OpenProcess error="Access is denied."

            DEBUG    bldeploy - AcquireLock: waiting: validated lock file C:\Program Files\BMC Software\BladeLogic\8.1\RSCD\Transactions\locks\writer.lck

             

            This is an active issue ISS03949265. We'll try to update this thread when solution or hotfix is released.

            1 of 1 people found this helpful
            • 3. Re: BLDeploy error
              Johannes Richter

              Hi all,

               

              We are running into the exact same issue. While BLPackage deployment one item needs a restart and after the restart the job doesn't continue. Instead we see the error in the bltargetmanager log all the time.

               

              Is there a solution for that problem?

               

              Thanks,
              Johannes

              • 4. Re: BLDeploy error
                Bill Robinson

                what is initiating a restart ?  the package item itself?  or did you flag the item as require a reboot in the blpackage ?

                • 5. Re: BLDeploy error
                  Johannes Richter

                  the reboot is set in the BLPackage item. "Reboot after Item Deployment"

                  • 6. Re: BLDeploy error
                    Bill Robinson

                    And the item self (whatever is running) doesn’t initiate the reboot right ?  and the deploy job has the ‘use item defined reboot’ ?

                    • 7. Re: BLDeploy error
                      Johannes Richter

                      Thats correct!

                      Addition: The deployed BLPackage and job are generated by a Compliance Job (Auto-Remediation)

                      • 8. Re: BLDeploy error
                        Jim Campbell

                        If you delete writer.lck in the 'locks' folder jobs will start working.  I think this has been fixed in some recent versions of the agent but am not sure which.

                         

                        What I was told is that the agent writes the PID of the bldeploy process to this file prior to rebooting.  It reads the process name for this PID whenever the file exists to make sure it is the 'bldeploy' process.  After the reboot, the file still remains when it shouldn't, and if the PID in the file has been assigned randomly to a protected system process of some kind then the agent cant' read the name of that process and it throws the error listed.

                        • 9. Re: BLDeploy error
                          Naveen Anne

                          I am seeing the same error on 8.5.01.218.

                          The deploy package has 3 manual reboots. I am seeing this error message randomly i.e. sometimes the the job runs don't have this error message while some runs have this error. In all cases, my job shows as successfull.

                           

                          1.  Has this issue (ISS03949265) been fixed?

                          2. If the job run shows as successful even when the error message occurs in the job run log, does that mean the deploy job completed successfully?

                           

                          Thanks

                          • 10. Re: BLDeploy error
                            Bill Robinson

                            is the agent 8.5.01.218?  this is an agent side fix i think.

                            • 11. Re: BLDeploy error
                              Naveen Anne

                              yes, the agent version is 8.5.01.218

                              • 12. Re: BLDeploy error
                                Steve Cupp

                                Hey Naveen. . . did anything ever come from this?

                                We are seeing this randomly, seems to happen during attempted reboots: Agent version is 8.5.01.231

                                 

                                Error    02/26/2015 16:13:36    BlLock::ValidatePIDActive: Cannot check validity of process. OpenProcess error="Access is denied. (Time in agent's deploy log:: 02/26/2015 16:13:19)       

                                • 13. Re: BLDeploy error
                                  russ mcdowell

                                  I'm seeing the same issue in 8.6.0.

                                  bldeploy - AcquireLock failed: C:\Program Files\BMC Software\BladeLogic\RSCD\\Transactions\locks\writer.lck in use: Will wait and attempt again

                                   

                                  The job was set to initiate reboot by Ignoring item defined reboot settings and reboot at end of job.  The log entry is at the time of BLPackage creation but the commit and reboot time are more than an hour later.  What I am finding is patching doesn't execute and the reboot doesn't happen.

                                  • 14. Re: BLDeploy error
                                    Bill Robinson

                                    was the job set to 'single job mode' ?

                                    1 2 Previous Next