Probe timeouts - Discovery

[Jason Stephens]

We are seeing a lot of WMI probe timeouts when we run discovery - mostly the "Installed Software" probe. I have messed with the "wmi_timeout" parameter (both more and less timeout), and I can't seem to get rid of these warnings.

As always thanks for the help!

Jason

[dvientos]

Where? I dont know what to change and where it is located.

Domenic

[Jason Stephens]

I still do not see much difference in the error/warning count. We may be getting into local machine issues now, but increasing the timeouts didn't get rid of the errors, it only prolonged them to the new timeout period....

Thanks for the help!

Jason

[layi_egbeyemi]

Hello

We are just starting out with Service Now in my organisation and we are also experiencing intermittent timeout issues with the Installed Software probe. First of all, I should state that we are running Calgary and it seems to me that the configured timeout is 2 minutes and not 10 mins as is stated both in this thread and on the wiki page for Discovery.

Second, I have not been able to alter this timeout value by adding wmi_timeout property to the "WMI: Installed Software" Probe. It has no effect.

From my investigations so far, all I can infer is that the further the location of the computer is from the MID server, the higher the likelihood of failure. We are running scans against computers in three regions. For those computers that reside in the same region as the MID Server, We get a 100% success rate. With another region, which is approximately half the distance of the third region from the MID Server's region, we get roughly a 50% success rate. With the third region, failure is almost 100%. All failures come back as the probe script being terminated at between 122 and 123 secs for exceeding configured timeout ( See attached).

Given the fact that we have several executions that complete around the 100, 110 secs mark, it would be great to experiment with increasing this timeout value to something like 3 or 5 mins, before considering the creation of additional MID servers in our various regions.

Thus my questions are
1. Why the disparity between the published default timeout value (15 mins) and our actual experience(2 mins, see attached).
2. How do we get the wmi_timeout property to take effect( We are running Calgary version)?


Regards
Layi Egbeyemi