Ad Widget

Collapse

SNMP Timeout but SNMPWalk is OK

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • still_at_work
    Junior Member
    • Jul 2023
    • 9

    #1

    SNMP Timeout but SNMPWalk is OK

    Hello,

    I have a Zabbix 6.4.16 server, deployed via Docker following the Zabbix documentation.

    Since last week, my Zabbix SNMP probes are no longer working, and I get messages saying "Timeout while connecting to '1.2.3.4:161'".

    What I don't understand is that my Zabbix server is able to perform an SNMP Walk correctly. I even tested doing the snmpwalk from my container:

    Code:
    docker exec -it --user=root zabbix-docker-zabbix-server-1 /bin/sh
    
    /var/lib/zabbix # snmpwalk -v2c -c public 1.2.3.4
    
    SNMPv2-MIB::sysDescr.0 = STRING: SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.674.10892.5
    DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (587764066) 68 days, 0:40:40.66
    Do you have any idea?
  • vijayk
    Senior Member
    • May 2023
    • 305

    #2
    You can check with increase the value of Timeout in config file of server as well as agent.
    ### Option: Timeout
    # Specifies timeout for communications (in seconds).
    #
    # Mandatory: no
    # Range: 1-30
    # Default:
    Timeout=30

    Comment

    • still_at_work
      Junior Member
      • Jul 2023
      • 9

      #3
      Hi,

      I just try with Timeout=30, no change.

      Do you have another idea ?

      Comment

      • Markku
        Senior Member
        Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
        • Sep 2018
        • 1781

        #4
        Check the log file, increase the logging level as needed. Take a packet capture and see what the Zabbix poller it attempting, if anything.

        Markku

        Comment

        • still_at_work
          Junior Member
          • Jul 2023
          • 9

          #5
          I found my problem. In my host, I set SNMP Community with a global macro, {$SNMP_COMMUNITY}, wich have been deleted for an unknow reason.

          Recreate this global macro with the correct value does the job !

          Comment

          Working...