Ad Widget

Collapse

Web monitoring: Connection Timeout

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Mun
    Member
    • Sep 2016
    • 67

    #1

    Web monitoring: Connection Timeout

    Hi,

    Can someone help me with this issue (as attached image)?
    Thank You.
    Last edited by Mun; 07-06-2017, 04:02.
  • ovas
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Apr 2017
    • 138

    #2
    Hello Mun!

    There is one way of troubleshooting: try to run curl request with the same parameters as you configure in Zabbix web interface from zabbix user in terminal. Does it succeed?
    Which position does Zabbix http poller process has on Zabbix Server -> Zabbix data gathering process busy % graph?
    Besides that, only DebugLevel=4 for zabbix_server.log can shed some light.

    Comment

    • Mun
      Member
      • Sep 2016
      • 67

      #3
      Web monitoring: Connection Timeout

      Originally posted by ovas
      Hello Mun!

      There is one way of troubleshooting: try to run curl request with the same parameters as you configure in Zabbix web interface from zabbix user in terminal. Does it succeed?
      Which position does Zabbix http poller process has on Zabbix Server -> Zabbix data gathering process busy % graph?
      Besides that, only DebugLevel=4 for zabbix_server.log can shed some light.

      Dear Ovas,

      I have increase the poller as well as changing the DebugLevel=4 but then it remains same. Timeout connection issue. When I run curl request to that websites, I found the error as attached. Do you have any idea, why?

      Thank You.
      Last edited by Mun; 07-06-2017, 04:02.

      Comment

      • ovas
        Senior Member
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • Apr 2017
        • 138

        #4
        DebugLevel would be helpful only if direct curl succeeded, so it's better to lower it down to 3, because 4 can eat up resources pretty fast.

        No idea why would timeout error occur at this stage, but running curl -Lv <link> can provide more details on the issue's roots.

        I could connect to both of these URLs successfully. Have you tried accessing it from other locations?

        Comment

        Working...