CIM discovery fails with "5 000 milliseconds timeout on connection http-outgoing"

[Ricky S Larsson]

The last week we've noticed that our IBM SVC discovery have started to fail. The problem is at the CIM classification. In the CIM - Classify input payload the following result is returned:

<results error="5 000 milliseconds timeout on connection http-outgoing-5 [ACTIVE]" probe_time="10141" result_code="900000">
<result/>

The http-outgoing have had other numbers like 1 or 3. I have tried changing the value of CIM probe parameters "connection_timeout" and "socket_timeout" without any different result.

I have confirmed that the wbem port is opened, both by telnet from the MID server and in the shazzam input

<scanner name="GenericTCP" port="5989" portprobe="wbem" protocol="tcp" result="open" service="wbem_https"/>

The SVC discovery was working about 1-2 weeks ago. Sadly the ECC queue records are now gone so it's hard to compare and see what has changed.

Anyone else that encountered this issue?

EDIT: By advice from ServiceNow Support I added credentials for SSH to complete the UNIX Classify. This didn't solve the 5000 milliseconds timeout issue And another warning message now appears as well:

No shell detected and probe parameter 'allow_unsupported_shells' is set to 'false'

[S_R_KHAN]

What response did you get from HI?

Or how did you resolve this issue?

[Ricky S Larsson]

I don't remember the response from HI but it didn't include a solution. We decided to not continue with this as we couldn't solve this.

[AnkushD]

Hey @Ricky S Larsson Did you found any solution on this it would be helpful if you could share any inputs.

[Ricky S Larsson]

Sorry, we never solved this and now years later it is no longer relevant for the client