Ad Widget

Collapse

Zabbix Agent Log

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • angel_of_devil
    Junior Member
    • Sep 2011
    • 29

    #1

    Zabbix Agent Log

    Dear All,

    All of my Windows hosts (Windows Server 2008 R2 & Windows Server 2012) both have no zabbix_agentd.log file at all. I don't know why. Below is configuration of one host:
    # This is a config file for Zabbix Agent (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:\Program Files\Zabbix Agent\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
    DebugLevel=0

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

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

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

    ### 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
    # Include=c:\zabbix\zabbix_agentd\

    ####### 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>
    # Note that shell command must not return empty string or EOL only.
    # Example: UserParameter=system.test,echo 1
    #UserParameter=system.test,echo 1
  • tchjts1
    Senior Member
    • May 2008
    • 1605

    #2
    Believe it or not, Zabbix is case sensitive, even on Windows. So your log directory and file name: C:\Program Files\Zabbix Agent\Zabbix_agentd.log need to be cased appropriately.

    I don't know if that is your issue or not, but I ran into that when I was first starting out with Zabbix.

    And you have DebugLevel=0 Put that at 3 and you will start seeing a log, I suspect.
    Last edited by tchjts1; 18-06-2013, 07:27.

    Comment

    • angel_of_devil
      Junior Member
      • Sep 2011
      • 29

      #3
      Originally posted by tchjts1
      Believe it or not, Zabbix is case sensitive, even on Windows. So your log directory and file name: C:\Program Files\Zabbix Agent\Zabbix_agentd.log need to be cased appropriately.

      I don't know if that is your issue or not, but I ran into that when I was first starting out with Zabbix.

      And you have DebugLevel=0 Put that at 3 and you will start seeing a log, I suspect.
      Thanks. The problem is solved with set value for parameter DebugLevel

      Comment

      Working...