Agile Central - HPQC: LOCK.tmp file is not removed

Document ID : KB000117562
Last Modified Date : 15/10/2018
Show Technical Document Details
Issue:
When the job runs, it creates a LOCK.tmp file but the lock file is never removed so the next job cannot be executed.

When attempting to run the next job, the following error is seen in the log:
[2018-10-15 17:44:19 Z]  WARN : RallyEIF::WRK::ConnectorRunner.acquire_lock - A LOCK.tmp file exists
[2018-10-15 17:44:19 Z] ERROR : RallyEIF::WRK::ConnectorRunner.acquire_lock - Another connector process (6608) is still running, unable to proceed
[2018-10-15 17:44:19 Z] ERROR : RallyEIF::WRK::ConnectorRunner.initialize - Unable to proceed with this invocation of the connector
[2018-10-15 17:44:19 Z] ERROR : Object.exception - Message Unable to proceed with this invocation of the connector
Cause:
This is caused when there is another connector that is currently running from the directory where the next connector config needs to also be run from.
Resolution:
Ensure there are no actively running connectors.  Sometimes, a connector can be launched without the '-1' parameter on the command line:
ruby ca_agile_central2_hpalm_connector.rb config.xml

This will cause the connector to run continuously instead of running a single time and then exiting.  Look for any open command prompt windows where this command may have been issued.

It is possible that there are no visible command prompts running this command due to another user launching it or the job being run as a scheduled job in the background.

If this is a case of the scheduled job being specified without a '-1', you'll need to edit the jobs and ensure that the command has included a '-1' on the command line:
ruby ca_agile_central2_hpalm_connector.rb config.xml -1

Additionally, you'll need to end the existing job that is currently executing.  This will vary depending on the operating system.
Windows
  1. Open Task Manager
  2. Click the Details tab
  3. Add the "Command Line" column
  4. Look for the ruby.exe process that includes the command line that references your XML configuration file
  5. Right click that line
  6. Choose End Task
 
Linux
  1. Open a command line
  2. Run: ps -ef | grep ruby
  3. Note the PID for the ruby process that includes the command line that references your XML configuration file
  4. Run: kill -9 <PID>

Now you may delete the LOCK.tmp file and try rerunning your jobs.