Ad Widget

Collapse

Windows Zabbix Agent

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • whitz3nd
    Junior Member
    • Oct 2013
    • 2

    #1

    Windows Zabbix Agent

    Hello eveyrone,
    I am new to working with Zabbix and have seemed to run into a bit of a snag.
    I have installed the Zabbix agent on a windows box, made the setting changes to the config file as needed and started up the agent.
    I checked the log file to make sure everyone is working as needed and i am getting the following error:

    6048:20131008:143914.351 active check configuration update from [10.10.8.12:10051] started to fail (bind() failed: [0x00002741] The requested address is not valid in its context.)

    I went back and checked my config file and it seems to be right, I could be wrong, but would like to see if yall out there who are far more knowledgeable in Zabbix could give me some pointers on what i might be missing or configured improperly.

    Thank you for any and all help.

    # This is a config file for the Zabbix agent daemon (Windows)
    # To get more information about Zabbix, go to http://www.zabbix.com

    ############ GENERAL PARAMETERS #################

    ### Option: LogFile
    # Name of log file.
    # If not set, Windows Event Log is used.
    #
    # Mandatory: no
    # Default:
    # LogFile=

    LogFile=c:\zabbix\zabbix_agentd.log

    ### Option: LogFileSize
    # Maximum size of log file in MB.
    # 0 - disable automatic log rotation.
    #
    # Mandatory: no
    # Range: 0-1024
    # Default:
    # LogFileSize=1

    ### Option: DebugLevel
    # Specifies debug level
    # 0 - no debug
    # 1 - critical information
    # 2 - error information
    # 3 - warnings
    # 4 - for debugging (produces lots of information)
    #
    # Mandatory: no
    # Range: 0-4
    # Default:
    # DebugLevel=3

    ### Option: SourceIP
    # Source IP address for outgoing connections.
    #
    # Mandatory: no
    # Default:
    SourceIP=10.10.8.12

    ### Option: EnableRemoteCommands
    # Whether remote commands from Zabbix server are allowed.
    # 0 - not allowed
    # 1 - allowed
    #
    # Mandatory: no
    # Default:
    EnableRemoteCommands=1

    ### Option: LogRemoteCommands
    # Enable logging of executed shell commands as warnings.
    # 0 - disabled
    # 1 - enabled
    #
    # Mandatory: no
    # Default:
    LogRemoteCommands=1

    ##### Passive checks related

    ### Option: Server
    # List of comma delimited IP addresses (or hostnames) of Zabbix servers.
    # Incoming connections will be accepted only from the hosts listed here.
    # No spaces allowed.
    # If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally.
    #
    # Mandatory: no
    # Default:
    # Server=

    Server=10.10.8.12

    ### Option: ListenPort
    # Agent will listen on this port for connections from the server.
    #
    # Mandatory: no
    # Range: 1024-32767
    # Default:
    ListenPort=10050

    ### Option: ListenIP
    # List of comma delimited IP addresses that the agent should listen on.
    # First IP address is sent to Zabbix server if connecting to it to retrieve list of active checks.
    #
    # Mandatory: no
    # Default:
    # ListenIP=0.0.0.0

    ### Option: StartAgents
    # Number of pre-forked instances of zabbix_agentd that process passive checks.
    # If set to 0, disables passive checks and the agent will not listen on any TCP port.
    #
    # Mandatory: no
    # Range: 0-100
    # Default:
    StartAgents=3

    ##### Active checks related

    ### 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=10.10.8.12

    ### 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=

    ### Option: HostnameItem
    # Item used for generating Hostname if it is undefined.
    # Ignored if Hostname is defined.
    #
    # Mandatory: no
    # Default:
    HostnameItem=system.hostname

    ### Option: RefreshActiveChecks
    # How often list of active checks is refreshed, in seconds.
    #
    # Mandatory: no
    # Range: 60-3600
    # Default:
    # RefreshActiveChecks=120
    RefreshActiveChecks=60

    ### Option: BufferSend
    # Do not keep data longer than N seconds in buffer.
    #
    # Mandatory: no
    # Range: 1-3600
    # Default:
    # BufferSend=5

    ### Option: BufferSize
    # Maximum number of values in a memory buffer. The agent will send
    # all collected data to Zabbix server or Proxy if the buffer is full.
    #
    # Mandatory: no
    # Range: 2-65535
    # Default:
    # BufferSize=100

    ### Option: MaxLinesPerSecond
    # Maximum number of new lines the agent will send per second to Zabbix Server
    # or Proxy processing 'log', 'logrt' and 'eventlog' active checks.
    # The provided value will be overridden by the parameter 'maxlines',
    # provided in 'log', 'logrt' or 'eventlog' item keys.
    #
    # Mandatory: no
    # Range: 1-1000
    # Default:
    # MaxLinesPerSecond=100

    ############ ADVANCED PARAMETERS #################

    ### Option: Alias
    # Sets an alias for parameter. It can be useful to substitute long and complex parameter name with a smaller and simpler one.
    # For example, if you wish to retrieve paging file usage in percents from the server,
    # you may use parameter "perf_counter[\Paging File(_Total)\% Usage]", or you may define an alias by adding the following line to configuration file
    # Alias = pg_usageerf_counter[\Paging File(_Total)\% Usage]
    # After that you can use parameter name "pg_usage" to retrieve the same information.
    # You can specify as many "Alias" records as you wish.
    # Aliases cannot be used for parameters defined in "PerfCounter" configuration file records.
    #
    # Mandatory: no
    # Range:
    # Default:

    ### Option: Timeout
    # Spend no more than Timeout seconds on processing
    #
    # Mandatory: no
    # Range: 1-30
    # Default:
    # Timeout=3

    ### Option: PerfCounter
    # Syntax: <parameter_name>,"<perf_counter_path>",<period>
    # 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).
    # 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:
    # PerfCounter = interrupts,"\Processor(0)\Interrupts/sec",60
    # Please note double quotes around performance counter path.
    # Samples for calculating average value will be taken every second.
    # You may run "typeperf -qx" to get list of all performance counters available in Windows.
    #
    # Mandatory: no
    # Range:
    # Default:

    ### Option: Include
    # You may include individual files in the configuration file.
    #
    # Mandatory: no
    # Default:
    # Include=

    # Include=c:\zabbix\zabbix_agentd.userparams.conf

    ####### USER-DEFINED MONITORED PARAMETERS #######

    ### Option: UnsafeUserParameters
    # Allow all characters to be passed in arguments to user-defined parameters.
    # 0 - do not allow
    # 1 - allow
    #
    # Mandatory: no
    # Range: 0-1
    # Default:
    # UnsafeUserParameters=0

    ### Option: UserParameter
    # User-defined parameter to monitor. There can be several user-defined parameters.
    # Format: UserParameter=<key>,<shell command>
    #
    # Mandatory: no
    # Default:
    # UserParameter=
  • richlv
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Oct 2005
    • 3112

    #2
    that system does not have an interface with address "10.10.8.12". you probably should simply comment out that option.
    Zabbix 3.0 Network Monitoring book

    Comment

    • whitz3nd
      Junior Member
      • Oct 2013
      • 2

      #3
      Originally posted by richlv
      that system does not have an interface with address "10.10.8.12". you probably should simply comment out that option.

      Yep, when I commented out the "Source IP" address, that did it.
      Yep, needed that extra pair of eyes to catch something I missed.
      Thank you much!

      Comment

      • steveboyson
        Senior Member
        • Jul 2013
        • 582

        #4
        SourceIP=10.10.8.12

        This cannot be correct. It seems to be the address of your server, not the source address of your agent.

        Comment

        Working...