Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..
256 views

Help with Scanner Locks and jobs that just don't complete

I've stopped/started the job, the agent and killed off any scan processes on the target node and I still can't seem to get this scan to complete.

What exactly is happening here?  Lookslike there's some ZOMBIE lock out there that just don't want to go away.

 

<log start="10:43:36" severity="debug">Extracting lock from DVW0196\\\___\\\0\\\___\\\MZ_Development_Inventory Scanner_Inventory Discovery by Scanner ERCOT\\\___\\\1454013590364\\\___\\\1454099990364</log>
<log start="10:43:36" severity="debug">Node was already locked:probe DVW0196, jobType 0, jobIdMZ_Development_Inventory Scanner_Inventory Discovery by Scanner ERCOT, lock time 1454013590364, lock expiration 1454099990364</log>
<log start="10:43:36" severity="debug">Checking lock expiration. Lock expiration time:1454099990364, compare time:1454085816749</log>
<log start="10:43:36" severity="debug">Comparing locks.</log>
<log start="10:43:36" severity="debug">This lock:DVW0196\\\___\\\0\\\___\\\Inventory Discovery by Scanner ERCOT testing\\\___\\\1454085816733\\\___\\\1454172216733</log>
<log start="10:43:36" severity="debug">Compared lock:DVW0196\\\___\\\0\\\___\\\MZ_Development_Inventory Scanner_Inventory Discovery by Scanner ERCOT\\\___\\\1454013590364\\\___\\\1454099990364</log>
<log start="10:43:36" severity="debug">Found valid lock is of different job/probe, will try next time</log>
<log start="10:43:36" severity="debug">Found existing lock on remote machine, lock scanner node failed.</log>
<log start="10:43:36" severity="debug">Step [Lock Scanner Node] finished.</log>
<log start="10:43:36" severity="debug">Step [Lock Scanner Node] failed, going to release connection</log>
<DISCONNECT start="10:43:36" duration="31" CMD="client_disconnect" RESULT="" IS_NULL="Y" type="uda" credentialsId="22_1_CMS" />
<log start="10:43:36" severity="workflow-debug">step Lock Scanner Node finished execution with status: FAILURE. triggerCI: a9be0ca8d994a06a7272d97fa85b57c3</log>
<log start="10:43:36" severity="workflow-debug">step Lock Scanner Node execution failed. triggerCI: a9be0ca8d994a06a7272d97fa85b57c3</log>
<log start="10:43:36" severity="workflow-debug">Calculated timeout for retry number 13 is 600000</log>
<log start="10:43:36" severity="workflow-debug">step Lock Scanner Node execution failed - go to TIMEOUT parking to:600000 millis, on retry:14. triggerCI: a9be0ca8d994a06a7272d97fa85b57c3, state properties:{[STATE_PROPERTY_CONNECTED_MAC=[B@24c90b36],[STATE_PROPERTY_PLATFORM_CONFIGFILE=[B@7a7d3e47],[STATE_PROPERTY_ORIGINAL_BASEDIR=[B@3483e624],[loggingPolicy=[B@3f7a606b],[STATE_PROPERTY_RESOLVED_CONFIGURED_BASEDIR=[B@7b50315b],[STATE_PROPERTY_CONNECTED_SHELL_PROTOCOL_NAME=[B@aff1918],[STATE_PROPERTY_CONNECTED_SHELL_CODEPAGE=[B@71c87c4b],[STATE_PROPERTY_CONNECTED_SHELL_CREDENTIAL=[B@21585a49],[STATE_PROPERTY_CONNECTED_SHELL_IP=[B@2f8f7fb9],[PLATFORM=[B@760a6313],[STATE_PROPERTY_RESOLVED_BASEDIR=[B@57d0326b],[ARCHITECTURE=[B@23eeb0f0],[STATE_PROPERTY_ERROR_LEVEL=[B@ba26efe],[STATE_PROPERTY_CONNECTED_SHELL_PROTOCOL=[B@5524eba9]}</log>
<log start="10:43:36" severity="workflow-debug">step Lock Scanner Node execution failed. triggerCI: a9be0ca8d994a06a7272d97fa85b57c3, state properties:{[STATE_PROPERTY_CONNECTED_MAC=[B@24c90b36],[STATE_PROPERTY_PLATFORM_CONFIGFILE=[B@7a7d3e47],[STATE_PROPERTY_ORIGINAL_BASEDIR=[B@3483e624],[loggingPolicy=[B@3f7a606b],[STATE_PROPERTY_RESOLVED_CONFIGURED_BASEDIR=[B@7b50315b],[STATE_PROPERTY_CONNECTED_SHELL_PROTOCOL_NAME=[B@aff1918],[STATE_PROPERTY_CONNECTED_SHELL_CODEPAGE=[B@71c87c4b],[STATE_PROPERTY_CONNECTED_SHELL_CREDENTIAL=[B@21585a49],[STATE_PROPERTY_CONNECTED_SHELL_IP=[B@2f8f7fb9],[PLATFORM=[B@760a6313],[STATE_PROPERTY_RESOLVED_BASEDIR=[B@57d0326b],[ARCHITECTURE=[B@23eeb0f0],[STATE_PROPERTY_ERROR_LEVEL=[B@ba26efe],[STATE_PROPERTY_CONNECTED_SHELL_PROTOCOL=[B@5524eba9]}</log>
<log start="10:43:36" severity="workflow-debug">onStepFinish -&gt; triggerCi:a9be0ca8d994a06a7272d97fa85b57c3 next step:[Lock Scanner Node] with step status:FAILURE set workflow status to: PARKING</log>
<log start="10:43:36" severity="workflow-debug">workflow execution finish running with status:PARKING. triggerCI: a9be0ca8d994a06a7272d97fa85b57c3</log>
<log start="10:43:36" severity="info">Execution current time:2016/01/29 10:43:36</log>

0 Likes
2 Replies
Highlighted
Super Contributor.
Super Contributor.

Re: Help with Scanner Locks and jobs that just don't complete

Hi Ken

Have you tried to restart your target? or clear the probe cache? I think you'd better open a support ticket for deeply investigation. It not easy to identify the cause through part of the log.

BR
dong-xu

0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: Help with Scanner Locks and jobs that just don't complete

I have opened a case, I always forget about the probe cache......  thanks!

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.