Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-5914

Can not monitor Windows 7

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Incomplete
    • Icon: Major Major
    • None
    • 2.0.3
    • Agent (G)
    • windows 7 zabbix 2.0.3 on linux

      zabbix_agentd.log--------------------------

      9532:20121130:171559.041 Starting Zabbix Agent [10.85.29.45]. Zabbix 2.0.3 (revision 30483).
      1072:20121130:171559.057 agent #1 started [listener]
      9156:20121130:171559.057 agent #0 started [collector]
      7848:20121130:171559.058 agent #2 started [listener]
      7628:20121130:171559.058 agent #3 started [listener]
      9460:20121130:171559.059 agent #4 started [active checks]

      My server is 10.85.160.83

      config--------------

      1. This is a config file for Zabbix Agent (Windows)
      2. To get more information about Zabbix, go to http://www.zabbix.com
                            1. GENERAL PARAMETERS #################
          1. Option: LogFile
      2. Name of log file.
      3. If not set, Windows Event Log is used.
        #
      4. Mandatory: no
      5. Default:
      6. LogFile=

      LogFile=c:\zabbix\zabbix_agentd.log

          1. Option: LogFileSize
      2. Maximum size of log file in MB.
      3. 0 - disable automatic log rotation.
        #
      4. Mandatory: no
      5. Range: 0-1024
      6. Default:
      7. LogFileSize=1
          1. Option: DebugLevel
      2. Specifies debug level
      3. 0 - no debug
      4. 1 - critical information
      5. 2 - error information
      6. 3 - warnings
      7. 4 - for debugging (produces lots of information)
        #
      8. Mandatory: no
      9. Range: 0-4
      10. Default:
      11. DebugLevel=3
          1. Option: SourceIP
      2. Source IP address for outgoing connections.
        #
      3. Mandatory: no
      4. Default:
      5. SourceIP=
          1. Option: EnableRemoteCommands
      2. Whether remote commands from Zabbix server are allowed.
      3. 0 - not allowed
      4. 1 - allowed
        #
      5. Mandatory: no
      6. Default:
      7. EnableRemoteCommands=0
          1. Option: LogRemoteCommands
      2. Enable logging of executed shell commands as warnings.
      3. 0 - disabled
      4. 1 - enabled
        #
      5. Mandatory: no
      6. Default:
      7. LogRemoteCommands=0
              1. Passive checks related
          1. Option: Server
      2. List of comma delimited IP addresses (or hostnames) of Zabbix servers.
      3. Incoming connections will be accepted only from the hosts listed here.
      4. No spaces allowed.
      5. If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally.
        #
      6. Mandatory: no
      7. Default:
      8. Server=

      Server=10.85.160.83

          1. Option: ListenPort
      2. Agent will listen on this port for connections from the server.
        #
      3. Mandatory: no
      4. Range: 1024-32767
      5. Default:
      6. ListenPort=10050
          1. Option: ListenIP
      2. List of comma delimited IP addresses that the agent should listen on.
      3. First IP address is sent to Zabbix server if connecting to it to retrieve list of active checks.
        #
      4. Mandatory: no
      5. Default:
        ListenIP=10.85.29.45
          1. Option: StartAgents
      2. Number of pre-forked instances of zabbix_agentd that process passive checks.
      3. If set to 0, disables passive checks and the agent will not listen on any TCP port.
        #
      4. Mandatory: no
      5. Range: 0-100
      6. Default:
      7. StartAgents=3
        StartAgents=5
              1. Active checks related
          1. Option: ServerActive
      2. List of comma delimited IP:port (or hostname:port) pairs of Zabbix servers for active checks.
      3. If port is not specified, default port is used.
      4. IPv6 addresses must be enclosed in square brackets if port for that host is specified.
      5. If port is not specified, square brackets for IPv6 addresses are optional.
      6. If this parameter is not specified, active checks are disabled.
      7. Example: ServerActive=127.0.0.1:20051,zabbix.domain,[::1]:30051,::1,[12fc::1]
        #
      8. Mandatory: no
      9. Default:
      10. ServerActive=

      #ServerActive=10.85.160.83:10051

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

      Hostname=10.85.29.45

          1. Option: HostnameItem
      2. Item used for generating Hostname if it is undefined.
      3. Ignored if Hostname is defined.
        #
      4. Mandatory: no
      5. Default:
      6. HostnameItem=system.hostname
          1. Option: RefreshActiveChecks
      2. How often list of active checks is refreshed, in seconds.
        #
      3. Mandatory: no
      4. Range: 60-3600
      5. Default:
      6. RefreshActiveChecks=120
          1. Option: BufferSend
      2. Do not keep data longer than N seconds in buffer.
        #
      3. Mandatory: no
      4. Range: 1-3600
      5. Default:
      6. BufferSend=5
          1. Option: BufferSize
      2. Maximum number of values in a memory buffer. The agent will send
      3. all collected data to Zabbix server or Proxy if the buffer is full.
        #
      4. Mandatory: no
      5. Range: 2-65535
      6. Default:
      7. BufferSize=100
          1. Option: MaxLinesPerSecond
      2. Maximum number of new lines the agent will send per second to Zabbix Server
      3. or Proxy processing 'log', 'logrt' and 'eventlog' active checks.
      4. The provided value will be overridden by the parameter 'maxlines',
      5. provided in 'log', 'logrt' or 'eventlog' item keys.
        #
      6. Mandatory: no
      7. Range: 1-1000
      8. Default:
      9. MaxLinesPerSecond=100
                            1. ADVANCED PARAMETERS #################
          1. Option: Alias
      2. Sets an alias for parameter. It can be useful to substitute long and complex parameter name with a smaller and simpler one.
      3. For example, if you wish to retrieve paging file usage in percents from the server,
      4. you may use parameter "perf_counter[\Paging File(_Total)\% Usage]", or you may define an alias by adding the following line to configuration file
      5. Alias = pg_usage:perf_counter[\Paging File(_Total)\% Usage]
      6. After that you can use parameter name "pg_usage" to retrieve the same information.
      7. You can specify as many "Alias" records as you wish.
      8. Aliases cannot be used for parameters defined in "PerfCounter" configuration file records.
        #
      9. Mandatory: no
      10. Range:
      11. Default:
          1. Option: Timeout
      2. Spend no more than Timeout seconds on processing
        #
      3. Mandatory: no
      4. Range: 1-30
      5. Default:
        Timeout=30
          1. Option: PerfCounter
      2. Syntax: <parameter_name>,"<perf_counter_path>",<period>
      3. Defines new parameter <parameter_name> which is an average value for system performance counter <perf_counter_path> for the specified time period <period> (in seconds).
      4. For example, if you wish to receive average number of processor interrupts per second for last minute, you can define new parameter "interrupts" as following:
      5. PerfCounter = interrupts,"\Processor(0)\Interrupts/sec",60
      6. Please note double quotes around performance counter path.
      7. Samples for calculating average value will be taken every second.
      8. You may run "typeperf -qx" to get list of all performance counters available in Windows.
        #
      9. Mandatory: no
      10. Range:
      11. Default:
          1. Option: Include
      2. You may include individual files in the configuration file.
        #
      3. Mandatory: no
      4. Default:
      5. Include=
      1. Include=c:\zabbix\zabbix_agentd.userparams.conf
                  1. USER-DEFINED MONITORED PARAMETERS #######
          1. Option: UnsafeUserParameters
      2. Allow all characters to be passed in arguments to user-defined parameters.
      3. 0 - do not allow
      4. 1 - allow
        #
      5. Mandatory: no
      6. Range: 0-1
      7. Default:
      8. UnsafeUserParameters=0
          1. Option: UserParameter
      2. User-defined parameter to monitor. There can be several user-defined parameters.
      3. Format: UserParameter=<key>,<shell command>
        #
      4. Mandatory: no
      5. Default:
      6. UserParameter=

      -------------------------------------------------------------------
      C:\Users\ >netstat -an

      ????

      ?? ???? ???? ??
      TCP 0.0.0.0:23 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:5800 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:5900 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:9535 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:9593 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:9594 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:9595 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:17000 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:20100 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:33354 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:49207 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:49232 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:49238 0.0.0.0:0 LISTENING
      TCP 0.0.0.0:49319 0.0.0.0:0 LISTENING
      TCP 10.85.29.45:139 0.0.0.0:0 LISTENING
      TCP 10.85.29.45:10050 0.0.0.0:0 LISTENING
      TCP 10.85.29.45:49339 10.72.129.104:445 ESTABLISHED
      TCP 10.85.29.45:54665 172.18.32.221:8080 CLOSE_WAIT
      TCP 10.85.29.45:54700 10.82.19.175:1352 ESTABLISHED
      TCP 10.85.29.45:54721 10.82.20.253:1352 ESTABLISHED
      TCP 10.85.29.45:54729 10.82.19.175:1352 ESTABLISHED
      TCP 10.85.29.45:54979 172.19.64.37:8080 CLOSE_WAIT
      TCP 10.85.29.45:54980 172.19.64.37:8080 CLOSE_WAIT
      TCP 10.85.29.45:54981 172.19.64.37:8080 CLOSE_WAIT
      TCP 10.85.29.45:54983 172.19.64.37:8080 CLOSE_WAIT
      TCP 10.85.29.45:54984 172.19.64.37:8080 CLOSE_WAIT
      TCP 10.85.29.45:55069 10.82.134.104:135 TIME_WAIT
      TCP 10.85.29.45:55070 10.82.134.104:1025 TIME_WAIT
      TCP 10.85.29.45:55071 10.85.160.83:80 ESTABLISHED
      TCP 10.85.29.45:55074 172.19.6.47:8080 ESTABLISHED
      TCP 10.85.29.45:55075 172.19.6.47:8080 ESTABLISHED
      TCP 10.85.29.45:55076 172.19.6.47:8080 ESTABLISHED
      TCP 10.85.29.45:55077 172.19.6.47:8080 ESTABLISHED
      TCP 10.85.29.45:55078 172.19.6.47:8080 ESTABLISHED
      TCP 10.85.29.45:55079 10.85.28.78:139 TIME_WAIT
      TCP 10.85.29.45:55086 172.19.6.47:8080 ESTABLISHED
      TCP 10.85.29.45:55088 10.82.128.49:7080 TIME_WAIT
      TCP 10.85.29.45:55089 172.19.64.37:8080 ESTABLISHED
      TCP 10.85.29.45:55090 172.19.64.37:8080 ESTABLISHED
      TCP 10.85.29.45:55096 10.85.160.83:80 CLOSE_WAIT
      TCP 10.85.29.45:55097 10.85.160.83:80 CLOSE_WAIT
      TCP 10.85.29.45:55098 10.85.160.83:80 CLOSE_WAIT
      TCP 10.85.29.45:55099 10.85.160.83:80 CLOSE_WAIT
      TCP 10.85.29.45:55100 10.85.160.83:80 ESTABLISHED
      TCP 10.85.29.45:55101 10.82.128.49:7080 TIME_WAIT
      TCP 10.85.29.45:55102 10.85.160.83:80 ESTABLISHED
      TCP 10.85.29.45:55103 176.34.252.58:80 SYN_SENT
      TCP 10.85.29.45:55104 74.125.128.105:443 SYN_SENT
      TCP 10.85.29.45:55105 176.34.252.58:80 SYN_SENT
      TCP 10.85.29.45:55106 74.125.128.105:443 SYN_SENT
      TCP 127.0.0.1:7887 0.0.0.0:0 LISTENING
      TCP 127.0.0.1:9535 127.0.0.1:49300 ESTABLISHED
      TCP 127.0.0.1:9592 0.0.0.0:0 LISTENING
      TCP 127.0.0.1:9966 0.0.0.0:0 LISTENING
      TCP 127.0.0.1:9966 127.0.0.1:49333 ESTABLISHED
      TCP 127.0.0.1:9966 127.0.0.1:54000 ESTABLISHED
      TCP 127.0.0.1:9966 127.0.0.1:54173 ESTABLISHED
      TCP 127.0.0.1:9966 127.0.0.1:54322 ESTABLISHED
      TCP 127.0.0.1:9966 127.0.0.1:54394 ESTABLISHED
      TCP 127.0.0.1:21584 0.0.0.0:0 LISTENING
      TCP 127.0.0.1:49156 0.0.0.0:0 LISTENING
      TCP 127.0.0.1:49163 0.0.0.0:0 LISTENING
      TCP 127.0.0.1:49187 0.0.0.0:0 LISTENING
      TCP 127.0.0.1:49201 0.0.0.0:0 LISTENING
      TCP 127.0.0.1:49242 0.0.0.0:0 LISTENING
      TCP 127.0.0.1:49300 127.0.0.1:9535 ESTABLISHED
      TCP 127.0.0.1:49333 127.0.0.1:9966 ESTABLISHED
      TCP 127.0.0.1:54000 127.0.0.1:9966 ESTABLISHED
      TCP 127.0.0.1:54173 127.0.0.1:9966 ESTABLISHED
      TCP 127.0.0.1:54322 127.0.0.1:9966 ESTABLISHED
      TCP 127.0.0.1:54394 127.0.0.1:9966 ESTABLISHED
      TCP [::]:23 [::]:0 LISTENING
      TCP [::]:80 [::]:0 LISTENING
      TCP [::]:135 [::]:0 LISTENING
      TCP [::]:445 [::]:0 LISTENING
      TCP [::]:3389 [::]:0 LISTENING
      TCP [::]:49152 [::]:0 LISTENING
      TCP [::]:49153 [::]:0 LISTENING
      TCP [::]:49154 [::]:0 LISTENING
      TCP [::]:49207 [::]:0 LISTENING
      TCP [::]:49232 [::]:0 LISTENING
      TCP [::]:49238 [::]:0 LISTENING
      TCP [::]:49319 [::]:0 LISTENING
      TCP [::1]:49243 [::]:0 LISTENING
      UDP 0.0.0.0:123 :
      UDP 0.0.0.0:161 :
      UDP 0.0.0.0:500 :

            Unassigned Unassigned
            davidfwz davidfwz
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: