Terminated the probe because the max timeout was reached: 610 seconds.

[Henrik Jutterst]

I have been googeling for an answer to this but havent found anything that can help me.

I'm doing discovery on a set of IPs but I cant seem to classify any of the objects. I'm expecting Windows Servers but the most detailed message I get is "Terminated the probe because the max timeout was reached: 610 seconds."

Here is the information I collected:

Discovery -> Status -> Clicking on the latest scan

State:

Completed

Started

178

Completed

178

Clicking on Devices Tab: "Devices (177)"

-------------------------------------------------------

175 rows with this info:

Completed activity:

Active, couldn't classify: No WMI connec

On Issues column, clicking "Details" link.

-------------------------------------------------------

Level:

Warning

Short Message:

Terminated the probe because the max timeout was reached: 610 seconds.

ECC queue input:

WMIRunner

Source:

Windows Classify

-------------------------------------------------------

The account used on the MID server is domain account with local admin.

First I thought this was an credential issue, but as I understand it a domain account with local admin should be enough to classify a CI right?

The main question is regarding this message: "Terminated the probe because the max timeout was reached: 610 seconds." what does that mean and how to solve it?

Kind Regards

/Henrik

[sergiu_panaite]

Hi Henrik,

There are two known problems opened in ServiceNow related to this error message:

- PRB663995 fixed in GP3HF7, GP6 and Helsinki. This one can happen if MID server is waiting on SSH connections part of discovery and timeout value occurs. In case of timeout we should just close the connection

- PRB673176 fixed in Istanbul

What release are you on?

[Henrik Jutterst]

Hello Sergiu and thanks for the reply!

Here's info on what I'm running:

Build name: Helsinki

Build date: 03-22-2017_2340

Build tag: glide-helsinki-03-16-2016__patch9-hotfix0a-03-17-2017

I'm using a behavior to only discover wmi and ssh.

In Discovery log I have two rows not using WMI, and these are Linux servers. I get this message for those:

Level: Warning

Message: "SSHCommand: No credential found for types [SSH Password,SSH Private Key]"

Source: UNIX Classify

ECC Queue Input: MultiProbe

This is purely a credential issue, but will this affect WMI probe to create timeout issues? OR is this WMI-issue just because I don't have credentials for the servers to go on with Exploration phase?

I tried to discover the MID server where the account running MID server is local admin. But I get this short message in discovery history > details then:

"Authentication failure with the local MID server service credential."

Any idea on what is happening?

Thank you

/Henrik

[Henrik Jutterst]

Thanks for the reply.. I ran a new discovery but only for WMI and I get the same result then.. Any idea on what is going on or if there is a way to see more details on what the issue might be?

Kind Regards

/Henrik

[Henrik Jutterst · Accepted solution]

I just wanted to post an update to this case. It seems that this was the issue:

WMI classification probe timeout

Issue was resolved by setting down the threads on MID server to standard 25