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

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-26-2021 05:18 AM
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'
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-05-2023 09:34 AM
What response did you get from HI?
Or how did you resolve this issue?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-15-2023 01:10 AM
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.