Ad Widget

Collapse

Windows Zabbix Agent unreachable

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • TheBigK
    Junior Member
    • Feb 2009
    • 1

    #1

    Windows Zabbix Agent unreachable

    on one Server my zabbix agent is unreachable. Its not accessable with telnet and in the logs are full of this:

    22148:20090212:100859 Values in the buffer 0 Max 100
    22148:20090212:100900 Sleeping for 1 seconds
    58068:20090212:100900 In collect_cpustat()
    22148:20090212:100901 In send_buffer('88.80.x.x','10051')
    22148:20090212:100901 Values in the buffer 0 Max 100
    22148:20090212:100901 Sleeping for 1 seconds
    58068:20090212:100901 In collect_cpustat()
    22148:20090212:100902 In send_buffer('88.80.x.x','10051')
    22148:20090212:100902 Values in the buffer 0 Max 100
    22148:20090212:100902 Sleeping for 1 seconds
    58068:20090212:100902 In collect_cpustat()

    Netstat tells me this:

    TCP 88.80.x.x:10050 88.80.x.x:33016 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:34126 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:35231 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:35492 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:36354 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:37473 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:38734 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:39622 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:39900 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:40844 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:41982 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:43075 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:44200 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:44237 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:45309 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:48808 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:48835 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:48881 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:49234 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:49571 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:49917 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:51039 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:52152 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:53247 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:54392 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:54606 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:55485 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:56784 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:57914 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:59003 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:59172 CLOSE_WAIT
    TCP 88.80.x.x:10050 88.80.x.x:60140 CLOSE_WAIT

    any ideas to solve this ?
  • vinny
    Senior Member
    • Jan 2008
    • 145

    #2
    If your server is not accessible via telnet, the problem is not the agent but certainly the network.

    Are the ports 10050 & 10051 opened between agent & server zabbix ?

    vinny
    -------
    Zabbix 1.8.3, 1200+ Hosts, 40 000+ Items...zabbix's everywhere

    Comment

    Working...