Uncategorised

Zabbix Errors and Solution Database

March 22, 2022 Leave a Comment

Error 1 – Maria DB issues

root@ip-172-31-10-159:/usr/share/zabbix-proxy-mysql# zcat /usr/share/zabbix-proxy-mysql/schema.sql.gz | mysql -u zabbix zabbix -p
Enter password:
ERROR 1118 (42000) at line 1278: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.
root@ip-172-31-10-159:/usr/share/zabbix-proxy-mysql#

Solution – 1

Mysql-server or mysql client was installed and both cannot at the same time. uninstalled mysql and start from fresh.

 18  dpkg-query -l | grep mysql
   19  mysql
   20  dpkg-query -l | grep mysql-server
   21  dpkg-query -l | grep mysql
   22  apt-get remove mysql-client
   23  dpkg-query -l | grep mysql
   24  apt-get remove mysql-client-8.0
   25  dpkg-query -l | grep mysql
   26  apt-get remove mysql-common
   27  dpkg-query -l | grep mysql
   28  apt-get remove mysql-client-core-8.0
   29  dpkg-query -l | grep
   30  dpkg-query -l | grep mysql
   31  apt-get remove mysql-common
   32  dpkg-query -l | grep mysql

Error 2 – mariadb

root@ip-172-31-25-144:/home/ubuntu# sudo apt -y install mariadb-common mariadb-server mariadb-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mariadb-client : Depends: mariadb-client-10.3 (>= 1:10.3.29-0ubuntu0.20.04.1) but it is not going to be installed
 mariadb-server : Depends: mariadb-server-10.3 (>= 1:10.3.29-0ubuntu0.20.04.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root@ip-172-31-25-144:/home/ubuntu#

Solution 2 

Mysql-server was installed and both cannot at the same time. uninstalled mysql and mariadb could then be.

 18  dpkg-query -l | grep mysql
   19  mysql
   20  dpkg-query -l | grep mysql-server
   21  dpkg-query -l | grep mysql
   22  apt-get remove mysql-client
   23  dpkg-query -l | grep mysql
   24  apt-get remove mysql-client-8.0
   25  dpkg-query -l | grep mysql
   26  apt-get remove mysql-common
   27  dpkg-query -l | grep mysql
   28  apt-get remove mysql-client-core-8.0
   29  dpkg-query -l | grep
   30  dpkg-query -l | grep mysql
   31  apt-get remove mysql-common
   32  dpkg-query -l | grep mysql

Error – 3 – libpcre2-8.so.0()(64bit) is needed

[root@ip-172-31-23-45 centos]# rpm -ivh zabbix-agent-6.0.0-1.el7.x86_64.rpm
warning: zabbix-agent-6.0.0-1.el7.x86_64.rpm: Header V4 RSA/SHA512 Signature, key ID a14fe591: NOKEY
error: Failed dependencies:
        libpcre2-8.so.0()(64bit) is needed by zabbix-agent-6.0.0-1.el7.x86_64

Solution 3 

$ yum install pcre2-devel.x86_64
$ yum install pcre.x86_64

Error – 4 – Zabbix Host Not available

Received empty response from Zabbix Agent at [13.233.206.103]. Assuming that agent dropped connection because of access permissions.

Solution – 4 

This issues i faced in AWS server due to confusion of Public IP address and pvt IP add address. I noticed that Zabbix server request the agent using PUBLIC ip address thus in zabbix_agentd.conf

Server=3.110.176.72 [ RIGHT with Public IP address ]
Server=172.31.10.229 [ WRONG with PVT IP address ]

Error 5 – Unable to connect to [127.0.0.1]:10051

$ more /var/log/zabbix/zabbix_agentd.log
  6072:20220322:013622.093 Got signal [signal:15(SIGTERM),sender_pid:6323,sender_uid:997,reason:0]. Exiting ...
  6072:20220322:013622.097 Zabbix Agent stopped. Zabbix 6.0.0 (revision 5203d2ea7d).
  6327:20220322:013622.112 Starting Zabbix Agent [Zabbix server]. Zabbix 6.0.0 (revision 5203d2ea7d).
  6327:20220322:013622.112 **** Enabled features ****
  6327:20220322:013622.113 IPv6 support:          YES
  6327:20220322:013622.113 TLS support:           YES
  6327:20220322:013622.113 **************************
  6327:20220322:013622.113 using configuration file: /etc/zabbix/zabbix_agentd.conf
  6327:20220322:013622.113 agent #0 started [main process]
  6331:20220322:013622.118 agent #4 started [listener #3]
  6332:20220322:013622.120 agent #5 started [active checks #1]
  6328:20220322:013622.122 agent #1 started [collector]
  6329:20220322:013622.123 agent #2 started [listener #1]
  6330:20220322:013622.124 agent #3 started [listener #2]
  6332:20220322:013622.126 Unable to connect to [127.0.0.1]:10051 [cannot connect to [[127.0.0.1]:10051]: [111] Connection ref
used]
  6332:20220322:013622.126 Active check configuration update started to fail
  6330:20220322:013631.949 failed to accept an incoming connection: connection from "3.110.176.72" rejected, allowed hosts: "1

Solution – 5


### Option: ServerActive
#       List of comma delimited IP addresses or DNS names (address:port) pairs or clusters (address:port;address2:port) of Zabbix servers and Zabbix proxies for active checks.
#       If port is not specified, default port is used.
#       Cluster nodes need be separated by semicolon.
#       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 for multiple servers:
#               ServerActive=127.0.0.1:20051,zabbix.domain,[::1]:30051,::1,[12fc::1]
#       Example for HA:
#               ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3
#       Example for HA with two clusters and one server:
#               ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain
#
# Mandatory: no
# Default:
# ServerActive=

ServerActive=172.31.10.229

libpcre2-8.so.0()(64bit) is needed by zabbix-agent2-6.0.2-1.el7.x86_64

[root@ip-172-31-31-191 centos]# rpm -Uvh https://repo.zabbix.com/zabbix/6.0/rhel/7/x86_64/zabbix-agent2-6.0.2-1.el7.x86_64.rpm
Retrieving https://repo.zabbix.com/zabbix/6.0/rhel/7/x86_64/zabbix-agent2-6.0.2-1.el7.x86_64.rpm
warning: /var/tmp/rpm-tmp.n6142w: Header V4 RSA/SHA512 Signature, key ID a14fe591: NOKEY
error: Failed dependencies:
        libpcre2-8.so.0()(64bit) is needed by zabbix-agent2-6.0.2-1.el7.x86_64

Solution

$ yum update
$ yum install pcre2-devel.x86_64
$ yum install pcre.x86_64

zabbix50-agent-5.0.21-1.el7.x86_64 conflicts with file from package zabbix-agent-6

Transaction check error:
  file /etc/logrotate.d/zabbix-agent from install of zabbix50-agent-5.0.21-1.el7.x86_64 conflicts with file from package zabbix-agent-6.0.0-1.el7.x86_64
  file /var/log/zabbix from install of zabbix50-agent-5.0.21-1.el7.x86_64 conflicts with file from package zabbix-agent-6.0.0-1.el7.x86_64
  file /usr/lib/systemd/system/zabbix-agent.service from install of zabbix50-agent-5.0.21-1.el7.x86_64 conflicts with file from package zabbix-agent-6.0.0-1.el7.x86_64
  file /usr/sbin/zabbix_agentd from install of zabbix50-agent-5.0.21-1.el7.x86_64 conflicts with file from package zabbix-agent-6.0.0-1.el7.x86_64
  file /usr/share/man/man8/zabbix_agentd.8.gz from install of zabbix50-agent-5.0.21-1.el7.x86_64 conflicts with file from package zabbix-agent-6.0.0-1.el7.x86_64

Solution

$ yum remove zabbix_agent
$ rpm -qa
$ rpm -qa | grep zabbix
$ rpm -e zabbix50-5.0.21-1.el7.x86_64
$ rpm -e zabbix-agent-6.0.0-1.el7.x86_64
Rajesh Kumar
Follow me
Latest posts by Rajesh Kumar (see all)
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x