-
1. Re: is it possible to add timeout or sleep function in the discovery.runCommand()?
Andrew Waters
Mar 11, 2016 2:36 AM
2 of 2 people found this helpfulNo - you cannot provide a timeout to the runCommand.
-
2. Re: is it possible to add timeout or sleep function in the discovery.runCommand()?
Bob Anderson
Mar 11, 2016 11:03 AM
What command are you running that takes more than 2 minutes to complete?
Why are you running that command?
1 of 1 people found this helpful -
-
3. Re: is it possible to add timeout or sleep function in the discovery.runCommand()?
Two command were used to get Oracle RAC VIP and Scan IP:
VIP：srvctl config nodeapps
SCANIP：srvctl config scan
The command cannot return before TPL was timeout, therefore we cannot get any results.
-
4. Re: is it possible to add timeout or sleep function in the discovery.runCommand()?
We have a scenario where we are pulling the installation date/time using systeminfo | find /i "original install date" to pull this information and for some hosts it works and others it does not. Running the command locally the value is present, but not during discovery so assuming that it is a timing issue. It shouldn't take that long to retrieve the information, but it does. I'm up for alternatives or extending the response time, whichever makes sense.
-
5. Re: is it possible to add timeout or sleep function in the discovery.runCommand()?
Andrew Waters
Jan 4, 2018 1:41 AM
4 of 4 people found this helpfulWhat is reported on the DiscoveredCommandResult node for the command. That should indicate what went wrong.
-
6. Re: is it possible to add timeout or sleep function in the discovery.runCommand()?
Thanks Andrew, good place to start!
