Ad Widget

Collapse

unreachable issues, also issues with agent on server

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • cbiggins
    Junior Member
    • Apr 2009
    • 4

    #1

    unreachable issues, also issues with agent on server

    Hi Guys,

    I have two issues that I have searched for answers for and come up empty handed, so I am now asking for help.

    1. The agent on the same box as the server is not responding. The server runs fine and connects to the other boxes fine, just not itself. I can telnet to itself using 127.0.0.1 10051 but not 127.0.0.1 10050 - not sure what to do about that. It was working perfectly until I tried to add an item which failed, but I have since removed the item and commented out the conf changes for the item but the agent will still not respond.

    2. One of the boxes is constantly sending 'is unreachable' emails when the box is alive and well. Is there a way to change the sensitivity of the unreachable item or another way to test it?

    Thanks very VERY much in advance, I really appreciate any help I get.

    Christian
  • richlv
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Oct 2005
    • 3112

    #2
    1. verify that zabbix_agentd is running, that there are no local firewall rules, make sure agent is listening on localhost, make sure server in agentd config file is set to localhost.

    2. depending on the trigger, you can make it less sensitive, yes. i'd suggest finding out why it trips, though - maybe some data fails to be retrieved ? if so, there could be multiple causes - zabbix server overload, some data gathering timeouting on agent etc.
    if you absoletly are sure you just want to turn the sensitivity down, you'll have to either show trigger expression with the description of what you want to achieve, or i'll have to refer you to the manual
    Zabbix 3.0 Network Monitoring book

    Comment

    • cbiggins
      Junior Member
      • Apr 2009
      • 4

      #3
      Originally posted by richlv
      1. verify that zabbix_agentd is running, that there are no local firewall rules, make sure agent is listening on localhost, make sure server in agentd config file is set to localhost.

      2. depending on the trigger, you can make it less sensitive, yes. i'd suggest finding out why it trips, though - maybe some data fails to be retrieved ? if so, there could be multiple causes - zabbix server overload, some data gathering timeouting on agent etc.
      if you absoletly are sure you just want to turn the sensitivity down, you'll have to either show trigger expression with the description of what you want to achieve, or i'll have to refer you to the manual
      1. zabbix_agentd is definitely running
      Code:
      root@eomer:/var/log# ps aux | grep -i zabbix_agentd
      zabbix   11843  0.0  0.0   2892   500 ?        SN   Apr24   0:00 zabbix_agentd
      zabbix   11844  0.0  0.0   2892   884 ?        SN   Apr24   0:08 zabbix_agentd
      zabbix   11845  0.0  0.0   2960   744 ?        SN   Apr24   0:00 zabbix_agentd
      zabbix   11846  0.0  0.0   2960   744 ?        SN   Apr24   0:00 zabbix_agentd
      zabbix   11847  0.0  0.0   2960   744 ?        SN   Apr24   0:00 zabbix_agentd
      zabbix   11848  0.0  0.0   2960   744 ?        SN   Apr24   0:00 zabbix_agentd
      zabbix   11849  0.0  0.0   2960   744 ?        SN   Apr24   0:00 zabbix_agentd
      zabbix   11850  0.0  0.0   2968   764 ?        SN   Apr24   0:00 zabbix_agentd
      I'll double check those other suggestions.

      As for no. 2: This is logged at the time that the other server becomes unreachable.
      Code:
      agent.ping] error: Get value from agent failed: ZBX_TCP_READ() failed [Interrupted system call]
      Look like this is a known issue and I'll have a search on the forums and see if I can resolve it.

      Thanks.

      Comment

      Working...