Ad Widget

Collapse

Active Checks on Mac OSX

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • WillemR
    Member
    • Oct 2015
    • 30

    #1

    Active Checks on Mac OSX

    Hi,

    I'm monitoring mac OSX servers successfully via passive checks of Zabbix using the default template.

    However, the question comes from upper to monitor a particular log file (/usr/local/aw/lexxsrv.log)

    I've create the extra active item via a extra template (so far so good)

    However, in the latest data tab, I'm waiting patiently to get me some logs, i don't get any error or warning.
    I'm successfully using active checks on centos 7 and Windows.

    I've checked the conf file and active server with the correct hostname (=same as web interface).

    i've used some debugging and the proxy does get the active check.
    On the client however, I'm getting this error:

    56856:20161115:182907.815 active check configuration update from [192.168.10.44:10051] started to fail (ZBX_TCP_READ() failed: [54] Connection reset by peer)


    with tcpdump at the same time on the proxy:


    9078, win 28960, options [mss 1460,sackOK,TS val 182494162 ecr 1224623682,nop,wscale 7], length 0
    0x0000: 406c 8fb8 63e8 0800 2748 a891 0800 4500 @l..c...'H....E.
    0x0010: 003c 0000 4000 4006 a53e c0a8 0a2c c0a8 .<..@.@..>...,..
    0x0020: 0a01 2743 ca38 1e7a aa81 9842 1ad6 a012 ..'C.8.z...B....
    0x0030: 7120 95ac 0000 0204 05b4 0402 080a 0ae0 q...............
    0x0040: a3d2 48fe 4642 0103 0307 ..H.FB....
    19:48:42.128793 IP zabbix.local.zabbix-trapper > fileserver.51768: Flags [.], ack 77, win 227, options [nop,nop,TS val 182494162 ecr 1224623683], length 0
    0x0000: 406c 8fb8 63e8 0800 2748 a891 0800 4500 @l..c...'H....E.
    0x0010: 0034 0950 4000 4006 9bf6 c0a8 0a2c c0a8 .4.P@.@......,..
    0x0020: 0a01 2743 ca38 1e7a aa82 9842 1b22 8010 ..'C.8.z...B."..
    0x0030: 00e3 95a4 0000 0101 080a 0ae0 a3d2 48fe ..............H.
    0x0040: 4643 FC
    19:48:42.164707 IP zabbix.local.zabbix-trapper > fileserver.51768: Flags [R.], seq 1, ack 77, win 227, options [nop,nop,TS val 0 ecr 1224623683], length 0
    0x0000: 406c 8fb8 63e8 0800 2748 a891 0800 4500 @l..c...'H....E.
    0x0010: 0034 0951 4000 4006 9bf5 c0a8 0a2c c0a8 .4.Q@.@......,..
    0x0020: 0a01 2743 ca38 1e7a aa82 9842 1b22 8014 ..'C.8.z...B."..
    0x0030: 00e3 95a4 0000 0101 080a 0000 0000 48fe ..............H.
    0x0040: 4643 FC




    Config file of the mac osx server:

    ### Option: ServerActive
    # List of comma delimited IPort (or hostnameort) pairs of Zabbix servers for active checks.
    # If port is not specified, default port is used.
    # IPv6 addresses must be enclosed in square brackets if port for that host is specified.
    # If port is not specified, square brackets for IPv6 addresses are optional.
    # If this parameter is not specified, active checks are disabled.
    # Example: ServerActive=127.0.0.1:20051,zabbix.domain,[::1]:30051,::1,[12fc::1]
    #
    # Mandatory: no
    # Default:
    # ServerActive=

    ServerActive=192.168.10.44

    ### Option: Hostname
    # Unique, case sensitive hostname.
    # Required for active checks and must match hostname as configured on the server.
    # Value is acquired from HostnameItem if undefined.
    #
    # Mandatory: no
    # Default:
    # Hostname=

    Hostname=fileserver


    The fileserver is being monitored as follow:
    Zabbix Server --> Zabbix Active Proxy --> fileserver (passive and active)

    what else can i do to debug?
  • andris
    Zabbix developer
    • Feb 2012
    • 228

    #2
    Hi!

    56856:20161115:182907.815 active check configuration update from [192.168.10.44:10051] started to fail (ZBX_TCP_READ() failed: [54] Connection reset by peer)
    For some reason proxy closes connection when the agent on Mac OSX connects to obtain a list of active checks.
    Try to look into proxy log.
    Reasons why proxy refuses connection include:
    - unknown host (can be caused by not yet synchronized configuration between server DB and proxy),
    - misconfigured encryption settings (in Zabbix 3.x) - settings in frontend for that host do not match settings in agent configuration,
    - some firewall between agent and proxy blocking connections.
    - or something else ?

    Comment

    • WillemR
      Member
      • Oct 2015
      • 30

      #3
      it seems that the problem was that port 10051 was already in use by another program.
      stopped the program and restarted proxy, all is fine.

      Strange that the zabbixproxy still started, altough the port number was already taken.

      Comment

      Working...