UCMDB and UD Practitioners Forum (Previously CMS)
Showing results for 
Search instead for 
Do you mean 

Scan job failing with "Node was already locked" message

Trusted Contributor

Scan job failing with "Node was already locked" message

I'm getting this error message from an Inventory scanner job I'm trying to run.  I've stopped / started, cleared the probe cache on both jobs and even restarted the probe in question. and still get this error.  

Where is the lock file mentioned here located? 

Can it be deleted somehow?

<log start="12:27:34" severity="debug">Extracting lock from Probe255\\\___\\\0\\\___\\\MZ_Big_Inventory Scanner_Inventory Discovery by Scanner Copy\\\___\\\1461700975662\\\___\\\1461787375662</log>
<log start="12:27:34" severity="debug">Node was already locked:probe Probe255, jobType 0, jobIdMZ_Big_Inventory Scanner_Inventory Discovery by Scanner Copy, lock time 1461700975662, lock expiration 1461787375662</log>
<log start="12:27:34" severity="debug">Checking lock expiration. Lock expiration time:1461787375662, compare time:1461778054135</log>
<log start="12:27:34" severity="debug">Comparing locks.</log>
<log start="12:27:34" severity="debug">This lock:Probe255\\\___\\\0\\\___\\\Inventory Discovery by Scanner Copy Dev\\\___\\\1461778054119\\\___\\\1461864454119</log>
<log start="12:27:34" severity="debug">Compared lock:Probe255\\\___\\\0\\\___\\\MZ_Big_Inventory Scanner_Inventory Discovery by Scanner Copy\\\___\\\1461700975662\\\___\\\1461787375662</log>
<log start="12:27:34" severity="debug">Found valid lock is of different job/probe, will try next time</log>
<log start="12:27:34" severity="debug">Found existing lock on remote machine, lock scanner node failed.</log>
<log start="12:27:34" severity="debug">Step [Lock Scanner Node] finished.</log>

2 REPLIES
Neighborhood Admin

Re: Scan job failing with "Node was already locked" message

Hi,

 

We have an expert day going on today in our entitled forum which is only accessible and viewable for customers with a valid SAID (Support Agreement ID) in your profile. I see that you have access. so if you want you can submit your question to this forum:

UCMDB and UD Support Customer Forum 

You need to be logged in to see and access this forum. Also outside of the expert day we always have support engineers in this forum that can address your questions.

Greetings,

Bill

Respected Contributor

Re: Scan job failing with "Node was already locked" message

First, make sure that your UD DEV server is not still running a job against this host. The lock looks like it was initiated by the DEV server.

Second, the lock key is SCANNER_EXCLUSIVE_LOCK and is stored in the registry in Windows and in a file on *NIX:

  • Windows x86 - HKLM\SOFTWARE\Hewlett-Packard\Universal Discovery\V1\Options
  • Windows x64 - HKLM\SOFTWARE\Wow6432Node\Hewlett-Packard\Universal Discovery\V1\Options
  • *NIX - ~/.discagnt/aioptionrc
  • Mac- /var/root/.discagnt/aioptionrc

These are the OOB settings but location of aioptionrc file could be changed by changing basedir in the AgentsConfigurationByPlatform.xml and ScannersConfigurationByPlatform.xml files so check your setup for correct location. of the

//Add this to "OnDomLoad" event