Ad Widget

Collapse

"Timeout=" in AIX agent

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • crlf
    Junior Member
    • Mar 2013
    • 13

    #1

    "Timeout=" in AIX agent

    Hi,

    I have some AIX agents where I need to increase the timeout for UserParameters. These connect to a DB2 database to perform a simple query to check if the database is alive, but the "db2" command line client always takes a few seconds to establish the connection (although the rest is quite fast) and the script is killed by the agent.

    I've tried to set "Timeout=10" in "zabbix_agentd.conf", but this seems to do nothing.

    Am I missing something here? I'm fairly new to Zabbix...

    (These are all configured as active checks, BTW.)
  • tchjts1
    Senior Member
    • May 2008
    • 1605

    #2
    Did you restart your agent after you made that adjustment?
    And when you set it to Timeout=10, you either uncommented that line, or made a new line that wasn't commented, right?

    On your Zabbix App server, in zabbix_server.conf is also this setting... although I don't know if it will help or not.

    ### Option: Timeout
    # Specifies how long we wait for agent, SNMP device or external check (in seconds).
    #
    # Mandatory: no
    # Range: 1-30
    # Default:
    # Timeout=3

    if you make changes to that, be sure to restart your Zabbix server process.
    Last edited by tchjts1; 14-03-2013, 22:15.

    Comment

    • crlf
      Junior Member
      • Mar 2013
      • 13

      #3
      Actually, the problem was somewhere else... a typo in the "Hostname=" that was preventing all active checks on the agent from running.

      After fixing this, the checks now run. Interestingly enough, the timeout is still ignored: this time with the opposite effect (the checks aren't killed even if they run for longer than the specified timeout). This has no impact in my case, because my scripts have their own timeouts, but I wonder what would happen if they didn't and just hung forever.

      But your reply answers another thing that I was wondering about...

      At first I configured some of these DB2 checks as passive, and not only did they stuck in the queue, but (again) the "Timeout=" on the agent seemed to be completely ignored.

      Now I understand, it's not the agent that was killing the checks, but the server that was giving up on waiting for a reply.

      I guess I understand a bit more about how this works. Thanks.

      Comment

      Working...