Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vsphere Client.Timeout exceeded while awaiting headers #5133

Closed
ragonlan opened this issue Dec 11, 2018 · 9 comments
Closed

vsphere Client.Timeout exceeded while awaiting headers #5133

ragonlan opened this issue Dec 11, 2018 · 9 comments
Labels
area/vsphere bug unexpected problem or unintended behavior waiting for response waiting for response from contributor

Comments

@ragonlan
Copy link

Relevant telegraf.conf:

file telegraf.d/manu010.vm.conf

[[inputs.vsphere]]
   ## List of vCenter URLs to be monitored. These three lines must be uncommented
   ## and edited for the plugin to work.
   vcenters = [ "https://manu010.vm/sdk"]
   username = "xxxx@DOM1.priv"
   password = "XXXXX"

   ## VMs
   ## Typical VM metrics (if omitted or empty, all metrics are collected)
   vm_metric_include = []
   vm_metric_exclude = ["*"] ## Nothing is excluded by default
   vm_instances = false ## true by default

   ## Hosts
   ## Typical host metrics (if omitted or empty, all metrics are collected)
   host_metric_include = []
   host_metric_exclude = ["*"] ## Nothing excluded by default
   host_instances = false ## true by default

   ## Clusters
   cluster_metric_include = [] ## if omitted or empty, all metrics are collected
   cluster_metric_exclude = [] ## Nothing excluded by default
   cluster_instances = true ## true by default

   ## Datastores
   datastore_metric_include = [] ## if omitted or empty, all metrics are collected
   datastore_metric_exclude = ["*"] ## Nothing excluded by default
   datastore_instances = false ## false by default for Datastores only

   ## Datacenters
   datacenter_metric_include = [] ## if omitted or empty, all metrics are collected
   datacenter_metric_exclude = [] ## Datacenters are not collected by default.
   datacenter_instances = true ## false by default for Datastores only

   max_query_objects = 100
   max_query_metrics = 100
   collect_concurrency = 30
   discover_concurrency = 10
   force_discover_on_init = false
   object_discovery_interval = "1600s"
   insecure_skip_verify = true

file telegraf.d/manu001.vm.conf

[[inputs.vsphere]]
   vcenters = [ "https://manu001.vm/sdk"]
   username = "XXXX@XXX.dom2.priv"
   password = "XXXXX"

   ## VMs
   ## Typical VM metrics (if omitted or empty, all metrics are collected)
   vm_metric_include = []
   vm_metric_exclude = ["*"] ## Nothing is excluded by default
   vm_instances = false ## true by default

   ## Hosts
   ## Typical host metrics (if omitted or empty, all metrics are collected)
   host_metric_include = []
   host_metric_exclude = ["*"] ## Nothing excluded by default
   host_instances = false ## true by default

   ## Clusters
   cluster_metric_include = [] ## if omitted or empty, all metrics are collected
   cluster_metric_exclude = [] ## Nothing excluded by default
   cluster_instances = true ## true by default

   ## Datastores
   datastore_metric_include = [] ## if omitted or empty, all metrics are collected
   datastore_metric_exclude = ["*"] ## Nothing excluded by default
   datastore_instances = false ## false by default for Datastores only

   ## Datacenters
   datacenter_metric_include = [] ## if omitted or empty, all metrics are collected
   datacenter_metric_exclude = [] ## Datacenters are not collected by default.
   datacenter_instances = true ## false by default for Datastores only

   max_query_objects = 100
   max_query_metrics = 1000
   collect_concurrency = 30
   discover_concurrency = 10
   force_discover_on_init = false
   object_discovery_interval = "1600s"
   insecure_skip_verify = true

### System info:
OS: Debian 8.11
ii  telegraf                                              1.9.0-1                         amd64                           Plugin-driven server agent for reporting metrics into InfluxDB.

Inmediately after telegraf stars manu100.vm outputs this error:

2018-12-11T11:25:14Z D! [input.vsphere]: Starting plugin
2018-12-11T11:25:14Z D! [input.vsphere]: Starting plugin
2018-12-11T11:25:14Z D! [input.vsphere]: Creating client: manu010.vm
2018-12-11T11:25:14Z D! [input.vsphere]: Creating client: manu001.vm
2018-12-11T11:25:14Z E! [input.vsphere]: Error in discovery for manu010.vm: ServerFaultCode: Permission to perform this operation was denied.
2018-12-11T11:25:14Z D! [input.vsphere] vCenter maxQueryMetrics is defined: -1
2018-12-11T11:25:14Z D! [input.vsphere] vCenter says max_query_metrics should be 10000
2018-12-11T11:25:14Z D! [input.vsphere]: Discover new objects for manu001.vm
2018-12-11T11:25:14Z D! [input.vsphere] Discovering resources for datacenter
2018-12-11T11:25:14Z D! [input.vsphere]: No parent found for Folder:group-d1 (ascending from Folder:group-d1)
2018-12-11T11:25:15Z D! [input.vsphere] Discovering resources for cluster
2018-12-11T11:25:15Z D! [input.vsphere] Discovering resources for host
2018-12-11T11:25:16Z D! [input.vsphere] Discovering resources for vm
2018-12-11T11:25:16Z D! [input.vsphere] Discovering resources for datastore

No metrics is stored in influxdb for manu010.vm.

From time to time appears errors for the other vcenter, manu001.vm:

2018-12-11T11:31:00Z E! [inputs.vsphere]: Error in plugin: Post https://manu001.vm/sdk: context deadline exceeded
2018-12-11T11:31:00Z E! [inputs.vsphere]: Error in plugin: Post https://manu001.vm/sdk: context deadline exceeded

There is metrics for manu001 but not continually. Fails for an hour and after that continues getting metrics again.

@prydin
Copy link
Contributor

prydin commented Dec 11, 2018

Add timeout = "60s" to the config!

@danielnelson
Copy link
Contributor

@prydin Can you help me understand this recommendation better, isn't the default already timeout 60s in 1.9.0?

@prydin
Copy link
Contributor

prydin commented Dec 12, 2018

I sas assuming this was 1.8.x, but maybe not.

@ragonlan
Copy link
Author

Yes, I run telegraf 1.9:
telegraf 1.9.0-1 amd64
in a Debian 9.6

I set the value 60 but the timeouts keep coming. Actually I putted it to 120s and nothing changed. A pity that debug mode does not show what is doing when timeouts occur or the SeverFaultCode.

@prydin
Copy link
Contributor

prydin commented Mar 9, 2019

Try this with version 1.10 of telegraf. There's been some improvement of the timeout handling.

@danielnelson danielnelson added bug unexpected problem or unintended behavior area/vsphere need more info labels Mar 11, 2019
@Venopsis
Copy link

Venopsis commented May 5, 2019

Hi,
For info, got same issue and the problem was coming from configuration I copied-pasted from website. In timeout the guy forgot the "s" at the end of timeout ="1800s".
image

Good evening!

@rwaffen
Copy link

rwaffen commented May 14, 2019

tried with 1.10.3 and timeout = "1800s" ... the messages are still comming ...

@sspaink
Copy link
Contributor

sspaink commented Mar 22, 2022

There has been a lot of changes to the vsphere plugin since this bug report was opened, is this still an issue with the latest version of Telegraf? If it is please post config and logs and we can investigate this problem.

@sspaink sspaink added the waiting for response waiting for response from contributor label Mar 22, 2022
@telegraf-tiger
Copy link
Contributor

telegraf-tiger bot commented Apr 6, 2022

Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Page. Thank you!

@telegraf-tiger telegraf-tiger bot closed this as completed Apr 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vsphere bug unexpected problem or unintended behavior waiting for response waiting for response from contributor
Projects
None yet
Development

No branches or pull requests

6 participants