zabbix模板文件导入提示版本过低。可以考虑升级zabbix版本解决
wget https://mirrors.tuna.tsinghua.edu.cn/zabbix/zabbix/2.2/rhel/7/x86_64/zabbix-release-2.2-1.el7.noarch.rpm
下载解压zabbix的rpm包
[root@myserver_3 ~]# rpm -ivh zabbix-release-2.2-1.el7.noarch.rpm
warning: zabbix-release-2.2-1.el7.noarch.rpm: Header V4 DSA/SHA1 Signature, key ID 79ea5ed4: NOKEY
Preparing... ################################# [100%]
Updating / installing...
1:zabbix-release-2.2-1.el7 ################################# [100%]
[root@myserver_3 ~]#
查看yum源的路径并修改yum源的默认网址
[root@myserver_3 ~]# rpm -ql zabbix-release
/etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX
/etc/yum.repos.d/zabbix.repo
/usr/share/doc/zabbix-release-2.2
/usr/share/doc/zabbix-release-2.2/GPL
[root@myserver_3 ~]# vim /etc/yum.repos.d/zabbix.repo
末行模式下替换
:%s#http://repo.zabbix.com#https://mirrors.tuna.tsinghua.edu.cn/zabbix#g
安装zabbix-web-mysql和zabbix-server-mysql和mariadb
[root@myserver_3 ~]# systemctl start mariadb.service
[root@myserver_3 ~]# systemctl enable mariadb.service
Created symlink from /etc/systemd/system/multi-user.target.wants/mariadb.service to /usr/lib/systemd/system/mariadb.service.
[root@myserver_3 ~]#
数据库初始化设置
[root@myserver_3 ~]# mysql_secure_installation
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
Enter current password for root (enter for none):
OK, successfully used password, moving on...
Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.
Set root password? [Y/n] n
... skipping.
By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n] y
... Success!
Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n] y
... Success!
By default, MariaDB comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n] y
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n] y
... Success!
Cleaning up...
All done! If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!
[root@myserver_3 ~]#
建库
MariaDB [(none)]> create database zabbix character set utf8 collate utf8_bin;
Query OK, 1 row affected (0.001 sec)
MariaDB [(none)]> grant all on zabbix.* to zabbix@localhost identified by '123456';
Query OK, 0 rows affected (0.002 sec)
MariaDB [(none)]> flush privileges;
Query OK, 0 rows affected (0.000 sec)
MariaDB [(none)]> set innodb_strict_mode=0;
Query OK, 0 rows affected (0.000 sec)
MariaDB [(none)]> exit
Bye
[root@myserver my.cnf.d]# systemctl restart mariadb.service
[root@myserver my.cnf.d]# zcat /usr/share/doc/zabbix-server-mysql*/create.sql.gz|mysql -uzabbix
-p123456 zabbix
[root@myserver my.cnf.d]#
导数据
查看文件的内容有哪些(rpm -ql zabbix-server-mysql)
[root@myserver_3 ~]# rpm -ql zabbix-server-mysql
/usr/sbin/zabbix_server_mysql
/usr/share/doc/zabbix-server-mysql-2.2.23
/usr/share/doc/zabbix-server-mysql-2.2.23/create
/usr/share/doc/zabbix-server-mysql-2.2.23/create/data.sql
/usr/share/doc/zabbix-server-mysql-2.2.23/create/images.sql
/usr/share/doc/zabbix-server-mysql-2.2.23/create/schema.sql
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches/1.6
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches/1.6/mysql
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches/1.6/mysql/patch.sql
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches/1.8
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches/1.8/mysql
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches/1.8/mysql/patch.sql
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches/1.8/mysql/upgrade
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches/2.0
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches/2.0/mysql
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches/2.0/mysql/patch.sql
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches/2.0/mysql/rc4_rc5.sql
/usr/share/doc/zabbix-server-mysql-2.2.23/upgrades/dbpatches/2.0/mysql/upgrade
[root@myserver_3 ~]#
进到这个目录下 /usr/share/doc/zabbix-server-mysql-2.2.23/create/
[root@myserver_3 create]# pwd
/usr/share/doc/zabbix-server-mysql-2.2.23/create
[root@myserver_3 create]# ls
data.sql images.sql schema.sql
[root@myserver_3 create]# mysql -uzabbix -p123456 zabbix <schema.sql
[root@myserver_3 create]# mysql -uzabbix -p123456 zabbix <images.sql
[root@myserver_3 create]# mysql -uzabbix -p123456 zabbix <data.sql
[root@myserver_3 create]#
编辑zabbix-server的配置文件
[root@myserver_3 create]# vim /etc/zabbix/zabbix_server.conf
[root@myserver_3 create]# egrep -v '#|^$' /etc/zabbix/zabbix_server.conf
LogFile=/var/log/zabbix/zabbix_server.log
LogFileSize=0
PidFile=/var/run/zabbix/zabbix_server.pid
DBHost=localhost
DBName=zabbix
DBUser=zabbix
DBPassword=123456
DBSocket=/var/lib/mysql/mysql.sock
SNMPTrapperFile=/var/log/snmptt/snmptt.log
AlertScriptsPath=/usr/lib/zabbix/alertscripts
ExternalScripts=/usr/lib/zabbix/externalscripts
[root@myserver_3 create]#
启动zabbix-server更改时区
systemctl restart zabbix-server.service
改zabbix-server的时区
vim /etc/httpd/conf.d/zabbix.conf
<IfModule mod_php5.c>
php_value max_execution_time 300
php_value memory_limit 128M
php_value post_max_size 16M
php_value upload_max_filesize 2M
php_value max_input_time 300
php_value always_populate_raw_post_data -1
php_value date.timezone Asia/Shanghai
</IfModule>
启动httpd 登录前台页面查看
systemctl start httpd
http://192.168.1.40/zabbix/dashboard.php
(1)卸载zabbix-release
[root@myserver_3 ~]# rpm -e zabbix-release
(2)下载安装zabbix-release4.0
[root@myserver_3 ~]# wget https://mirrors.tuna.tsinghua.edu.cn/zabbix/zabbix/4.0/rhel/7/x86_64/zabbix-release-4.0-2.el7.noarch.rpm
--2021-01-02 15:38:36-- https://mirrors.tuna.tsinghua.edu.cn/zabbix/zabbix/4.0/rhel/7/x86_64/zabbix-release-4.0-2.el7.noarch.rpm
Resolving mirrors.tuna.tsinghua.edu.cn (mirrors.tuna.tsinghua.edu.cn)... 101.6.8.193, 2402:f000:1:408:8100::1
Connecting to mirrors.tuna.tsinghua.edu.cn (mirrors.tuna.tsinghua.edu.cn)|101.6.8.193|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13800 (13K) [application/x-redhat-package-manager]
Saving to: ‘zabbix-release-4.0-2.el7.noarch.rpm’
100%[=================================================>] 13,800 --.-K/s in 0s
2021-01-02 15:38:36 (457 MB/s) - ‘zabbix-release-4.0-2.el7.noarch.rpm’ saved [13800/13800]
[root@myserver_3 ~]# rpm -ivh zabbix-release-4.0-2.el7.noarch.rpm
warning: zabbix-release-4.0-2.el7.noarch.rpm: Header V4 RSA/SHA512 Signature, key ID a14fe591: NOKEY
Preparing... ################################# [100%]
Updating / installing...
1:zabbix-release-4.0-2.el7 ################################# [100%]
[root@myserver_3 ~]#
(3)修改yum源的配置的源
vim编辑器打开后 末行模式
:%s#http://repo.zabbix.com#https://mirrors.tuna.tsinghua.edu.cn/zabbix#g
(4)安装zabbix-server和zabbix-web
[root@myserver_3 ~]# yum install -y zabbix-server-mysql zabbix-web-mysql
(5)重启zabbix-server
查看升级日志
[root@myserver_3 ~]# tail -f /var/log/zabbix/zabbix_server.log
7867:20210102:154325.147 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reason:0]. Exiting ...
7869:20210102:154325.147 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reason:0]. Exiting ...
7870:20210102:154325.147 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reason:0]. Exiting ...
7872:20210102:154325.148 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reason:0]. Exiting ...
7849:20210102:154325.148 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reason:0]. Exiting ...
7843:20210102:154327.136 syncing history data...
7843:20210102:154327.136 syncing history data done
7843:20210102:154327.136 syncing trends data...
7843:20210102:154327.136 syncing trends data done
7843:20210102:154327.137 Zabbix Server stopped. Zabbix 2.2.23 (revision 83227).
8707:20210102:154611.029 Starting Zabbix Server. Zabbix 4.0.27 (revision ff3187cec7).
8707:20210102:154611.029 ****** Enabled features ******
8707:20210102:154611.029 SNMP monitoring: YES
8707:20210102:154611.029 IPMI monitoring: YES
8707:20210102:154611.029 Web monitoring: YES
8707:20210102:154611.029 VMware monitoring: YES
8707:20210102:154611.029 SMTP authentication: YES
8707:20210102:154611.029 Jabber notifications: YES
8707:20210102:154611.029 Ez Texting notifications: YES
8707:20210102:154611.029 ODBC: YES
8707:20210102:154611.029 SSH support: YES
8707:20210102:154611.029 IPv6 support: YES
8707:20210102:154611.029 TLS support: YES
8707:20210102:154611.029 ******************************
8707:20210102:154611.029 using configuration file: /etc/zabbix/zabbix_server.conf
8707:20210102:154611.033 current database version (mandatory/optional): 02020000/02020001
8707:20210102:154611.033 required mandatory version: 04000000
8707:20210102:154611.033 optional patches were found
8707:20210102:154611.033 starting automatic database upgrade
8707:20210102:154611.033 completed 0% of database upgrade
8707:20210102:154611.105 completed 1% of database upgrade
8707:20210102:154611.119 completed 2% of database upgrade
8707:20210102:154611.131 completed 3% of database upgrade
8707:20210102:154611.179 completed 4% of database upgrade
8707:20210102:154611.187 completed 5% of database upgrade
8707:20210102:154611.195 completed 6% of database upgrade
8707:20210102:154611.199 completed 7% of database upgrade
8707:20210102:154611.202 completed 8% of database upgrade
8707:20210102:154611.205 completed 9% of database upgrade
8707:20210102:154611.215 completed 10% of database upgrade
8707:20210102:154611.244 completed 11% of database upgrade
8707:20210102:154611.270 completed 12% of database upgrade
8707:20210102:154611.291 completed 13% of database upgrade
8707:20210102:154611.326 completed 14% of database upgrade
8707:20210102:154611.343 completed 15% of database upgrade
8707:20210102:154611.370 completed 16% of database upgrade
8707:20210102:154611.380 completed 17% of database upgrade
8707:20210102:154611.391 completed 18% of database upgrade
8707:20210102:154611.412 completed 19% of database upgrade
8707:20210102:154611.422 completed 20% of database upgrade
8707:20210102:154611.448 completed 21% of database upgrade
8707:20210102:154611.468 completed 22% of database upgrade
8707:20210102:154611.489 completed 23% of database upgrade
8707:20210102:154611.501 completed 24% of database upgrade
8707:20210102:154611.511 completed 25% of database upgrade
8707:20210102:154611.558 completed 26% of database upgrade
8707:20210102:154611.573 completed 27% of database upgrade
8707:20210102:154611.589 completed 28% of database upgrade
8707:20210102:154611.598 completed 29% of database upgrade
8707:20210102:154611.617 completed 30% of database upgrade
8707:20210102:154611.627 completed 31% of database upgrade
8707:20210102:154611.642 completed 32% of database upgrade
8707:20210102:154611.653 completed 33% of database upgrade
8707:20210102:154611.671 completed 34% of database upgrade
8707:20210102:154611.687 completed 35% of database upgrade
8707:20210102:154611.704 completed 36% of database upgrade
8707:20210102:154611.715 completed 37% of database upgrade
8707:20210102:154611.716 Action "Report problems to Zabbix administrators" condition "Trigger value = PROBLEM" will be removed during database upgrade: this type of condition is not supported anymore
8707:20210102:154611.736 completed 38% of database upgrade
8707:20210102:154611.756 completed 39% of database upgrade
8707:20210102:154611.766 completed 40% of database upgrade
8707:20210102:154611.786 completed 41% of database upgrade
8707:20210102:154611.799 completed 42% of database upgrade
8707:20210102:154611.813 completed 43% of database upgrade
8707:20210102:154611.827 completed 44% of database upgrade
8707:20210102:154611.837 completed 45% of database upgrade
8707:20210102:154611.868 completed 46% of database upgrade
8707:20210102:154611.886 completed 47% of database upgrade
8707:20210102:154611.949 completed 48% of database upgrade
8707:20210102:154611.984 completed 49% of database upgrade
8707:20210102:154612.095 completed 50% of database upgrade
8707:20210102:154612.119 completed 51% of database upgrade
8707:20210102:154612.137 completed 52% of database upgrade
8707:20210102:154612.150 completed 53% of database upgrade
8707:20210102:154612.167 completed 54% of database upgrade
8707:20210102:154612.178 completed 55% of database upgrade
8707:20210102:154612.187 completed 56% of database upgrade
8707:20210102:154612.196 completed 57% of database upgrade
8707:20210102:154612.206 completed 58% of database upgrade
8707:20210102:154612.308 completed 59% of database upgrade
8707:20210102:154612.448 completed 60% of database upgrade
8707:20210102:154612.460 completed 61% of database upgrade
8707:20210102:154612.475 completed 62% of database upgrade
8707:20210102:154612.490 completed 63% of database upgrade
8707:20210102:154612.504 completed 64% of database upgrade
8707:20210102:154612.517 completed 65% of database upgrade
8707:20210102:154612.538 completed 66% of database upgrade
8707:20210102:154612.557 completed 67% of database upgrade
8707:20210102:154612.574 completed 68% of database upgrade
8707:20210102:154612.593 completed 69% of database upgrade
8707:20210102:154612.616 completed 70% of database upgrade
8707:20210102:154612.629 completed 71% of database upgrade
8707:20210102:154612.642 completed 72% of database upgrade
8707:20210102:154612.685 completed 73% of database upgrade
8707:20210102:154612.688 completed 74% of database upgrade
8707:20210102:154612.699 completed 75% of database upgrade
8707:20210102:154612.716 completed 76% of database upgrade
8707:20210102:154612.724 completed 77% of database upgrade
8707:20210102:154612.737 completed 78% of database upgrade
8707:20210102:154612.742 completed 79% of database upgrade
8707:20210102:154612.755 completed 80% of database upgrade
8707:20210102:154612.762 completed 81% of database upgrade
8707:20210102:154612.881 completed 82% of database upgrade
8707:20210102:154613.008 completed 83% of database upgrade
8707:20210102:154613.172 completed 84% of database upgrade
8707:20210102:154613.227 completed 85% of database upgrade
8707:20210102:154613.230 completed 86% of database upgrade
8707:20210102:154613.233 completed 87% of database upgrade
8707:20210102:154613.247 completed 88% of database upgrade
8707:20210102:154613.250 completed 89% of database upgrade
8707:20210102:154613.261 completed 90% of database upgrade
8707:20210102:154613.278 completed 91% of database upgrade
8707:20210102:154613.294 completed 92% of database upgrade
8707:20210102:154613.303 completed 93% of database upgrade
8707:20210102:154613.326 completed 94% of database upgrade
8707:20210102:154613.358 completed 95% of database upgrade
8707:20210102:154613.376 completed 96% of database upgrade
8707:20210102:154613.394 completed 97% of database upgrade
8707:20210102:154613.411 completed 98% of database upgrade
8707:20210102:154613.438 completed 99% of database upgrade
8707:20210102:154613.446 completed 100% of database upgrade
8707:20210102:154613.446 database upgrade fully completed
8707:20210102:154613.454 server #0 started [main process]
8718:20210102:154613.455 server #1 started [configuration syncer #1]
8707:20210102:154613.556 starting event name update forced by database upgrade
8707:20210102:154613.556 completed 1% of event name update
8707:20210102:154613.556 completed 2% of event name update
8707:20210102:154613.556 completed 3% of event name update
8707:20210102:154613.556 completed 4% of event name update
8707:20210102:154613.557 completed 5% of event name update
8707:20210102:154613.557 completed 6% of event name update
8707:20210102:154613.557 completed 7% of event name update
8707:20210102:154613.557 completed 8% of event name update
8707:20210102:154613.557 completed 9% of event name update
8707:20210102:154613.557 completed 10% of event name update
8707:20210102:154613.557 completed 11% of event name update
8707:20210102:154613.557 completed 12% of event name update
8707:20210102:154613.557 completed 13% of event name update
8707:20210102:154613.557 completed 14% of event name update
8707:20210102:154613.557 completed 15% of event name update
8707:20210102:154613.557 completed 16% of event name update
8707:20210102:154613.557 completed 17% of event name update
8707:20210102:154613.558 completed 18% of event name update
8707:20210102:154613.559 completed 19% of event name update
8707:20210102:154613.559 completed 20% of event name update
8707:20210102:154613.560 completed 21% of event name update
8707:20210102:154613.560 completed 22% of event name update
8707:20210102:154613.561 completed 23% of event name update
8707:20210102:154613.562 completed 24% of event name update
8707:20210102:154613.562 completed 25% of event name update
8707:20210102:154613.563 completed 26% of event name update
8707:20210102:154613.563 completed 27% of event name update
8707:20210102:154613.564 completed 28% of event name update
8707:20210102:154613.564 completed 29% of event name update
8707:20210102:154613.564 completed 30% of event name update
8707:20210102:154613.564 completed 31% of event name update
8707:20210102:154613.564 completed 32% of event name update
8707:20210102:154613.564 completed 33% of event name update
8707:20210102:154613.565 completed 34% of event name update
8707:20210102:154613.565 completed 35% of event name update
8707:20210102:154613.565 completed 36% of event name update
8707:20210102:154613.565 completed 37% of event name update
8707:20210102:154613.565 completed 38% of event name update
8707:20210102:154613.565 completed 39% of event name update
8707:20210102:154613.565 completed 40% of event name update
8707:20210102:154613.565 completed 41% of event name update
8707:20210102:154613.565 completed 42% of event name update
8707:20210102:154613.565 completed 43% of event name update
8707:20210102:154613.565 completed 44% of event name update
8707:20210102:154613.565 completed 45% of event name update
8707:20210102:154613.565 completed 46% of event name update
8707:20210102:154613.565 completed 47% of event name update
8707:20210102:154613.565 completed 48% of event name update
8707:20210102:154613.565 completed 49% of event name update
8707:20210102:154613.565 completed 50% of event name update
8707:20210102:154613.565 completed 51% of event name update
8707:20210102:154613.565 completed 52% of event name update
8707:20210102:154613.565 completed 53% of event name update
8707:20210102:154613.565 completed 54% of event name update
8707:20210102:154613.565 completed 55% of event name update
8707:20210102:154613.565 completed 56% of event name update
8707:20210102:154613.565 completed 57% of event name update
8707:20210102:154613.565 completed 58% of event name update
8707:20210102:154613.565 completed 59% of event name update
8707:20210102:154613.566 completed 60% of event name update
8707:20210102:154613.566 completed 61% of event name update
8707:20210102:154613.566 completed 62% of event name update
8707:20210102:154613.566 completed 63% of event name update
8707:20210102:154613.566 completed 64% of event name update
8707:20210102:154613.566 completed 65% of event name update
8707:20210102:154613.566 completed 66% of event name update
8707:20210102:154613.566 completed 67% of event name update
8707:20210102:154613.566 completed 68% of event name update
8707:20210102:154613.566 completed 69% of event name update
8707:20210102:154613.566 completed 70% of event name update
8707:20210102:154613.566 completed 71% of event name update
8707:20210102:154613.566 completed 72% of event name update
8707:20210102:154613.566 completed 73% of event name update
8707:20210102:154613.566 completed 74% of event name update
8707:20210102:154613.566 completed 75% of event name update
8707:20210102:154613.566 completed 76% of event name update
8707:20210102:154613.566 completed 77% of event name update
8707:20210102:154613.566 completed 78% of event name update
8707:20210102:154613.566 completed 79% of event name update
8707:20210102:154613.566 completed 80% of event name update
8707:20210102:154613.566 completed 81% of event name update
8707:20210102:154613.566 completed 82% of event name update
8707:20210102:154613.567 completed 83% of event name update
8707:20210102:154613.567 completed 84% of event name update
8707:20210102:154613.567 completed 85% of event name update
8707:20210102:154613.567 completed 86% of event name update
8707:20210102:154613.567 completed 87% of event name update
8707:20210102:154613.567 completed 88% of event name update
8707:20210102:154613.567 completed 89% of event name update
8707:20210102:154613.567 completed 90% of event name update
8707:20210102:154613.567 completed 91% of event name update
8707:20210102:154613.567 completed 92% of event name update
8707:20210102:154613.567 completed 93% of event name update
8707:20210102:154613.567 completed 94% of event name update
8707:20210102:154613.567 completed 95% of event name update
8707:20210102:154613.567 completed 96% of event name update
8707:20210102:154613.567 completed 97% of event name update
8707:20210102:154613.567 completed 98% of event name update
8707:20210102:154613.567 completed 99% of event name update
8707:20210102:154613.567 completed 100% of event name update
8707:20210102:154613.585 event name update completed
刷新前台页面