you should be able to solve timeout problems by first insuring the ports are open.
If the ports are closed from your host you're executing this command on, then that will cause a "timeout" or "connection refused".
You can verify with openssl:
openssl s_client -connect https://yourSH:8089
if that opens a connection and reads a bunch of details about cryptography to you, you're good... if it fails with timeout or connection refused, the ports are blocked / or you cant otherwise route to "yourSH:8089".
If you're in a resource constrained environment and you absolutely must increase this timeout setting, then you do so by editing the following configuration item in web.conf:
so we need to edit web.conf:
[settings]
...
splunkdConnectionTimeout = <integer>
* The amount of time, in seconds, to wait before timing out when communicating with
splunkd.
* Must be at least 30.
* Values smaller than 30 will be ignored, resulting in the use of the
default value
* Default: 30
...
...and dont forget to restart!
I hope this helps!
