Ad Widget

Collapse

{basetech-postgr:agent.ping.nodata(5m)}=1

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • bryanyork
    Junior Member
    • Oct 2013
    • 3
    #1

    {basetech-postgr:agent.ping.nodata(5m)}=1

    Newbie Question
    I have the Windows agent installed on four virtual hosted servers. The Zabbix server is a dedicated server. I am getting source unreachable. At times it does work. I allowed port 10051 (port I chose) through Windows firewall. Below you will find the log file and my config file. Any help is greatly appreciated!!!

    Zabbix Server Internal Interface: 10.177.141.161
    Windows monitored internal interface: 198.101.161.6
    Mointored server name: basetech-pstgr

    3880:20131014:234742.529 Starting Zabbix Agent [basetech-postgr]. Zabbix 2.0.9 (revision 39075).
    3780:20131014:234742.576 agent #0 started [collector]
    2968:20131014:234742.576 agent #1 started[listener]
    1012:20131014:234742.576 agent #2 started[listener]
    1996:20131014:234742.576 agent #3 started[listener]
    3836:20131014:234742.576 agent #4 started [active checks]
    3836:20131014:234742.576 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: [0x00002741] The requested address is not valid in its context.)


    # 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_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.179.4.60

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

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

    ##### 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.177.141.161

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

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

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

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

    ### 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=
    Tags: agent config question, agentd.userparams.con, unavailable, unreachable
    • steveboyson
      Senior Member
      • Jul 2013
      • 582
      #2
      Code:
      ServerActive=127.0.0.1
      should point to your zabbix server.

        Comment

        • bryanyork
          Junior Member
          • Oct 2013
          • 3
          #3
          Active Server

          Thank You for that information. After changing the ip to my Zabbix server I found this in the logs:

          11088:20131016:163319.360 Starting Zabbix Agent [TRAPEZE-RDP]. Zabbix 2.0.8 (revision 38015).
          8088:20131016:163319.376 agent #0 started [collector]
          1680:20131016:163319.376 agent #3 started[listener]
          10792:20131016:163319.391 agent #1 started[listener]
          10804:20131016:163319.391 agent #4 started [active checks]
          10984:20131016:163319.391 agent #2 started[listener]
          10804:20131016:163319.423 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:163519.119 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:163719.782 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:163919.415 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:164119.049 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:164319.712 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:164519.345 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:164719.993 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:164919.855 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:165119.496 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:165319.147 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:165519.812 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:165719.462 No active checks on server: host [TRAPEZE-RDP] not found
          10804:20131016:165919.098 No active checks on server: host [TRAPEZE-RDP] not found

          Here is my latest config file:

          # 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_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.176.160.66

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

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

          ##### 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.177.14.161

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

          ### 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.177.14.161

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

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

            Comment

            • steveboyson
              Senior Member
              • Jul 2013
              • 582
              #4
              Code:
              Hostname=basetech-postgr
              in your agent's conf does not correspond to TRAPEZE-RDP as mentioned in the log.

              This is the LOGICAL name under which this system appears in zabbix and not neccessarily a DNS name.

              Pls. RTFM.

                Comment

                • bryanyork
                  Junior Member
                  • Oct 2013
                  • 3
                  #5
                  Zabbix Windows Agent

                  My apologies...I am trying to use Zabbix on 15 servers. The second config file was for another server but still having the same issue. I'm looking through the forums now trying to find an answer. Yes on RTFM.

                    Comment

                    • steveboyson
                      Senior Member
                      • Jul 2013
                      • 582
                      #6
                      Via the zabbix frontend just create the systems to be monitored:
                      s1, s2, s3, ... (whatever name you like).

                      Then configure these either by defining a zabbix agentd connection or a snmp connection by specifying their FQDN or IP address (recommended).

                      In each of your (zabbix) agent's config file specify "s1", "s2", "s3" according your definitions previously done in the "Hostname =" parameter. There you also specify the address of your zabbix server.

                      In a later step, you may define hostgroups and assign templates to your freshly defined systems, also via the frontend. The items in the templates get "autopopulated" to your agents config.

                      And that is all.
                      Last edited by steveboyson; 17-10-2013, 20:37.

                        Comment

                        Previous template Next
                        Working...