Ad Widget

Collapse

Web scenario fails

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • yousan
    Junior Member
    • Aug 2013
    • 5

    #1

    Web scenario fails

    Hello.

    Web scenario fails.
    ---
    Error: Timeout was reached
    ---

    I can access to the target web URL with wget or curl on zabbix server host.

    ---
    shell> wget -O /dev/null http://www.example.com
    ...
    200 OK
    ...
    ---

    I guess DNS lookup or something bad.
    I found same message on zabbix/zabbix_server.log.
    I want to more information about the failing. How can I get the debug info?

    Thanks.
  • jan.garaj
    Senior Member
    Zabbix Certified Specialist
    • Jan 2010
    • 506

    #2
    Increase your step parameter Timeout:


    Set value regarding of your current load time:
    shell> time wget -O /dev/null http://www.example.com
    Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.
    My DevOps stack: Docker / Kubernetes / Mesos / ECS / Terraform / Elasticsearch / Zabbix / Grafana / Puppet / Ansible / Vagrant

    Comment

    • yousan
      Junior Member
      • Aug 2013
      • 5

      #3
      Hi jan.garaj. Thank you for your reply.

      I understand how to set timeout value, thanks.

      Now it is set 15 seconds, default value. It looks enough time to reach the servers (web hosts).

      Comment

      • yousan
        Junior Member
        • Aug 2013
        • 5

        #4
        this is the test at the zabbix server host.
        I added google.com web scenario as test but it failed in this case.

        Code:
        Saving to: `/dev/null'
        
            [ <=>                                   ] 11,265      --.-K/s   in 0.001s
        
        2014-01-16 08:54:54 (16.6 MB/s) - `/dev/null' saved [11265]
        
        wget -O /dev/null http://www.google.com  0.00s user 0.01s system 3% cpu 0.212 total
        /**
        In case google.com, google returns 302 alter to 200.
        I have set 200 as expected value in web scenario, but it's not problem.
        It successes correctly in other zabbix host.
        Just I want to get debug information.
        */

        Comment

        • jan.garaj
          Senior Member
          Zabbix Certified Specialist
          • Jan 2010
          • 506

          #5
          If you have some devel skill you can check it in source code level:
          Join the friendly and open Zabbix community on our forums and social media platforms.

          If not, enable Zabbix server DebugLevel=4 and then check log file.
          Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.
          My DevOps stack: Docker / Kubernetes / Mesos / ECS / Terraform / Elasticsearch / Zabbix / Grafana / Puppet / Ansible / Vagrant

          Comment

          Working...