HMC Import fails due to timeout

[gblansteen]

The "nmon2influxdb hmc import" operation is failing during execution due to timeout.

$ nmon2influxdb hmc import
2018/08/28 13:05:16 Using configuration file /home//.nmon2influxdb.cfg
2018/08/28 13:05:16 Creating InfluxDB database hmc_influxdb
2018/08/28 13:05:16 Updating retention policy to keep only the last 45d0h0m0s days. Timestamp based.
2018/08/28 13:05:17 Fetching latest 2 hours performance metrics. See hmc_samples parameter.
2018/08/28 13:05:17 Getting list of managed systems
2018/08/28 13:05:47 Get https://***:12443/rest/api/uom/ManagedSystem: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

I performed the same operation from Google Chrome with success. The amount of time it took to return was greater than 60s.

Perhaps a option in the configuration to set the timeout would be beneficial?

[gblansteen]

I downloaded the source, located the hmc/hmc.go file and changed the "const timeout = 30" line to "const timeout = 120", compiled and executed the hmc import. There was no change in the timeout period. The amount of time for the failure to occur remained 30 seconds.

[adejoux]

Hello,

Sorry. I missed this issue. I think you changed exactly the good parameter for the timeout. Unfortunately I don't have HMC with this kind of response time. I will try to test it anyway.

Regards,

Alain

[kpaxindustries]

Hi, we were having the same issue, but I changed the timeout value, recompiled and it's working now. Strange.

[adejoux]

Thanks @kpaxindustries . I will add a new configuration parameter for this timeout value.

[julfur]

Hi,

I've just had the same problem.
We have many HMCs, some of which can get really slow.

(edit : correcting myself since 2.1.5 release date was in 2017, I trust that I should modify and recompile :))

Thanks for your help

[adejoux]

Hello :)

Sorry I need to push some modifications and release a new version. Planning to do it in the following days.

Thanks

[cybrnook]

Thanks for this! Would you still be pushing a new update?

[adejoux]

Hello @cybrnook,

Did you test the new version ? It should be ok no?

[pentiumoverdrive]

same problem, found out when checking the source code that the parameter is: hmc_timeout

hmc_timeout=120 would do it for me.
Noticed that v2.1.8 still says 2.1.7 :)