Ad Widget

Collapse

VMWARE "Timeout was reached"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rockandstone
    Junior Member
    • Mar 2021
    • 24

    #1

    VMWARE "Timeout was reached"

    Hello!
    I am using good template for VMware Hypervisor but after 3-4 months I have a problem: "Timeout was reached" in all my vcenter's item.
    We updated Virtual Center to V.7.0.2 Update 2 - Build release 17694817 and then problem starts to appear.

    I edited settings in zabbix_proxy.conf three months ago:
    Code:
    ### Option: StartVMwareCollectors
    StartVMwareCollectors=5
    VMwareFrequency=60
    VMwarePerfFrequency=60
    VMwareCacheSize=256M
    VMwareTimeout=40
    In zabbix_server.log I found continuous errors (every 10-20min):
    Code:
    "Numbers here":item "host:item_key[...]" became not supported: Timeout was reached
    "Numbers here":item "host:item_key[...]" became not supported: became supported
    "Numbers here" error reason for "host:item_key[...]" changed: Performance counter data is not available.
    I hope that someone has encountered this kind of problem before ...

    Thank you for your help
    Last edited by rockandstone; 22-03-2021, 16:25.
  • gofree
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2017
    • 400

    #2
    hi

    try to increase timeout ( up to 300s ), see last line on link bellow

    Comment


    • rockandstone
      rockandstone commented
      Editing a comment
      Ok I appreciate your idea and I think it will work, but would it be a "polished" workaround? I mean... 300 second of timeout will be too much since every minute I get data?
  • rockandstone
    Junior Member
    • Mar 2021
    • 24

    #3
    Ok I appreciate your idea and I think it will work, but would it be a "polished" workaround? I mean... 300 second of timeout will be too much since every minute I get data?
    Sorry I replied in a bad way, I am new in zabbix forum ^^
    Last edited by rockandstone; 22-03-2021, 17:16.

    Comment

    • gofree
      Senior Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • Dec 2017
      • 400

      #4
      Originally posted by rockandstone
      Ok I appreciate your idea and I think it will work, but would it be a "polished" workaround? I mean... 300 second of timeout will be too much since every minute I get data?
      up to 300s means it can be 300 max ( it can be also 59 )

      P.S. 1 min interval could the cause ( not saying it is ) that it timeouts - if you have plenty VM it can cause it ( personally I consider interval 1min with zabbix in large quantities a road to hell )

      Comment


      • rockandstone
        rockandstone commented
        Editing a comment
        Ok thank you for your explanation...
        I wonder if I should rise update interval value, even if I need them every minute (cpu usage, latency, ram, disk usage, ...). You called 1m interval a road to hell and this scared me, because we have 35+vm monitored. I will update you with fresh news asap!


      • gofree
        gofree commented
        Editing a comment
        I mean its road to hell if you have thousands items with 1 minute interval without measures like throttling, db partitioning, preprocessing.
    • rockandstone
      Junior Member
      • Mar 2021
      • 24

      #5
      Thank you for your help!

      I have edited proxy config file:
      StartVMwareCollectors=5
      VMwareFrequency=60
      VMwarePerfFrequency=60
      VMwareCacheSize=256M
      VMwareTimeout=60

      And it worked like a charm... I increased refresh rate too (from 1m to 5m), but I have to be careful because of housekeeper...
      Last edited by rockandstone; 01-04-2021, 12:43.

      Comment

      Working...