SUSE - Problems polling drive(s)

[Sieran]

Hello,

I was wondering if anyone would be able to give me a hand with this. I am new to Linux (mainly been using CentOS) and even newer to SUSE.

I manage to get the agent installed on one of our servers here running SUSE, but it does not seem to be polling the hard drives or space on them. I am not sure if this is a config issue, compatibility issue, or just me being an idiot (very possible).

Is there anything I can do to correct this? I thought it was possibly the way I installed the agent manually, so I removed everything and re-installed using a repository I found in YAST.

See below (no drives polled even after several hours):



Some details of the OS and template:







Thank you.

[f.koch]

Hi,

which filesystem do you use? (is this in the Global FS regex?) Are errors in the agentd log?

PS: You should Update yor Server to 2.0.9 for Security Reasons https://www.zabbix.com/forum/showthread.php?t=42586


regards

[Sieran]

Hi,

which filesystem do you use? Are errors in the agentd log?

PS: You should Update yor Server to 2.0.9 for Security Reasons https://www.zabbix.com/forum/showthread.php?t=42586


regards

For the file system: riserfs

As far as the logs go:

24130:20131009:134607.353 Starting Zabbix Agent [Zabbix server]. Zabbix 2.0.8 (revision 38017).
24131:20131009:134607.354 agent #0 started [collector]
24132:20131009:134607.354 agent #1 started[listener]
24133:20131009:134607.354 agent #2 started[listener]
24134:20131009:134607.354 agent #3 started[listener]
24135:20131009:134607.354 agent #4 started [active checks]
zabbix_agentd [27039]: Is this process already running? Could not lock PID file [/tmp/zabbix_agentd.pid]: [11] Resource temporarily unavailable
zabbix_agentd [27317]: Is this process already running? Could not lock PID file [/tmp/zabbix_agentd.pid]: [11] Resource temporarily unavailable
zabbix_agentd [27372]: Is this process already running? Could not lock PID file [/tmp/zabbix_agentd.pid]: [11] Resource temporarily unavailable
24131:20131009:155424.397 Got signal [signal:15(SIGTERM),sender_pid:23686,sender_uid:0,r eason:0]. Exiting ...
24130:20131009:155424.397 Got signal [signal:15(SIGTERM),sender_pid:23686,sender_uid:0,r eason:0]. Exiting ...
24132:20131009:155424.397 Got signal [signal:15(SIGTERM),sender_pid:23686,sender_uid:0,r eason:0]. Exiting ...
24135:20131009:155424.397 Got signal [signal:15(SIGTERM),sender_pid:23686,sender_uid:0,r eason:0]. Exiting ...
24133:20131009:155424.397 Got signal [signal:15(SIGTERM),sender_pid:23686,sender_uid:0,r eason:0]. Exiting ...
24134:20131009:155424.397 Got signal [signal:15(SIGTERM),sender_pid:23686,sender_uid:0,r eason:0]. Exiting ...
24130:20131009:155426.397 Zabbix Agent stopped. Zabbix 2.0.8 (revision 38017).
27954:20131009:160426.268 Starting Zabbix Agent [Zabbix server]. Zabbix 2.0.6 (revision 35158).
27955:20131009:160426.269 agent #0 started [collector]
27956:20131009:160426.269 agent #1 started[listener]
27957:20131009:160426.269 agent #2 started[listener]
27958:20131009:160426.269 agent #3 started[listener]
27959:20131009:160426.269 agent #4 started [active checks]
zabbix_agentd [28609]: Is this process already running? Could not lock PID file [/tmp/zabbix_agentd.pid]: [11] Resource temporarily unavailable
27955:20131009:162933.246 Got signal [signal:15(SIGTERM),sender_pid:23686,sender_uid:0,r eason:0]. Exiting ...
27954:20131009:162933.246 Got signal [signal:15(SIGTERM),sender_pid:23686,sender_uid:0,r eason:0]. Exiting ...
27959:20131009:162933.246 Got signal [signal:15(SIGTERM),sender_pid:23686,sender_uid:0,r eason:0]. Exiting ...
27957:20131009:162933.246 Got signal [signal:15(SIGTERM),sender_pid:23686,sender_uid:0,r eason:0]. Exiting ...
27956:20131009:162933.246 Got signal [signal:15(SIGTERM),sender_pid:23686,sender_uid:0,r eason:0]. Exiting ...
27958:20131009:162933.246 Got signal [signal:15(SIGTERM),sender_pid:23686,sender_uid:0,r eason:0]. Exiting ...
27954:20131009:162935.247 Zabbix Agent stopped. Zabbix 2.0.6 (revision 35158).
2121:20131010:095608.043 Starting Zabbix Agent [Zabbix server]. Zabbix 2.0.6 (revision 35158).
2122:20131010:095608.044 agent #0 started [collector]
2123:20131010:095608.046 agent #1 started[listener]
2124:20131010:095608.046 agent #2 started[listener]
2125:20131010:095608.046 agent #3 started[listener]
2126:20131010:095608.046 agent #4 started [active checks]

[Sieran]

In regards to the upgrade... I had a hell of a time installing zabbix (never used linux before setting this up). Trying to upgrade will be a treat.

[f.koch]

In regards to the upgrade... I had a hell of a time installing zabbix (never used linux before setting this up). Trying to upgrade will be a treat.

Hm how do you installed Zabbix? and on wich Distribution?




regards

[Sieran]

Hm how do you installed Zabbix? and on wich Distribution?

Honestly I don't remember which method I used to install it. I think I added the rpm path and did a yum install. I had more problems configuring it to work since I wasn't familiar with a lot of the commands. It wasn't that difficult once i figured out basic navigation and how to edit the config files (when someone tells you "Now edit this file and change these values"... and you never used VI before... it gets frustrating). I was basically following a walk through I found on a forum somewhere word for word.

CentOS 6.4

[Sieran]

Hm how do you installed Zabbix? and on wich Distribution?


Hm in the log, we can see you have 2 versions of agentd 2.0.6 and 2.0.8, which one do you use?

can you post your agentd conf?

regards

I had originally tried the 2.0.8 agent since it was the newest one. When it wasn't pulling the drives I thought it might be a compatibility issues since I was running an older server version so I rolled it back. Didn't make a difference.

Config:

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

### Option: PidFile
# Name of PID file.
#
# Mandatory: no
# Default:
# PidFile=/tmp/zabbix_agentd.pid

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

LogFile=/tmp/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=

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

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

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

### 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' and 'logrt' active checks.
# The provided value will be overridden by the parameter 'maxlines',
# provided in 'log' or 'logrt' item keys.
#
# Mandatory: no
# Range: 1-1000
# Default:
# MaxLinesPerSecond=100

### Option: AllowRoot
# Allow the agent to run as 'root'. If disabled and the agent is started by 'root', the agent
# will try to switch to user 'zabbix' instead. Has no effect if started under a regular user.
# 0 - do not allow
# 1 - allow
#
# Mandatory: no
# Default:
# AllowRoot=0

############ 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.
#
# Mandatory: no
# Range:
# Default:

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

### Option: Include
# You may include individual files or all files in a directory in the configuration file.
# Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.
#
# Mandatory: no
# Default:
# Include=

# Include=/usr/local/etc/zabbix_agentd.userparams.conf
# Include=/usr/local/etc/zabbix_agentd.conf.d/

####### 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>
# See 'zabbix_agentd' directory for examples.
#
# Mandatory: no
# Default:
# UserParameter=

[f.koch]

If you used rpms, the update is easy, you only need to update the rpm

Hm in the log, we can see you have 2 versions of agentd 2.0.6 and 2.0.8, which one do you use?

can you post your agentd conf?

[f.koch]

Hostname=Zabbix server

is this the hostname of the server? this must be set to the real hostname , you can get the hostname/fqdn with the command

hostname -f

[Sieran]

is this the hostname of the server? this must be set to the real hostname , you can get the hostname/fqdn with the command

hostname -f

Corrected that, but does not seem to make a difference in the drives.

I am going to try and upgrade Zabbix this weekend when I can have enough free time to tinker with this.

[f.koch]

i do not think the update solves your problem...

can you set the LLD interval to 30s and run the agent in debug mode, and show the log

regards