Zabbix 3.x 升級到 Zabbix 4.x

前言

Zabbix目前已經(jīng)發(fā)布4.0 LTS長期支持版慰安，雖然很多插件還停留在3.4版本比如Grafana表窘，但是還是要提前做好準備。生產(chǎn)環(huán)境建議暫時保持在3.4版本肌访，因為在4.0版本中很多語法發(fā)生改變螟蒸，建議仔細評估落剪。最重要的事情提醒三遍，不要忘記備份尿庐，不要忘記備份，不要忘記備份呢堰。

Zabbix 3.x 升級到 Zabbix 4.x

更新歷史

2018年11月01日 - 初稿

閱讀原文 - https://wsgzao.github.io/post/zabbix-upgrade/

擴展閱讀

Zabbix - https://www.zabbix.com/

官方文檔

https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400
https://www.zabbix.com/documentation/3.4/zh/manual/installation/upgrade
https://www.zabbix.com/download

Zabbix升級步驟

備份數(shù)據(jù)庫

# 數(shù)據(jù)庫全備時間比較長且文件交大抄瑟，建議壓縮或者使用xtrabackup
mysqldump -uzabbix -pzabbix --opt --skip-lock-tables --database zabbix > zabbix.sql
mysqldump -uzabbix -pzabbix --opt --skip-lock-tables --database zabbix | gzip > zabbix_`date +'%Y%m%d%H%M%S'`.sql.gz

CentOS

# 停止服務
service zabbix-server stop
service zabbix-agent stop
service httpd stop

# 備份 zabbix 文件
mkdir /opt/zabbix-backup/
cp /etc/zabbix/zabbix_server.conf /opt/zabbix-backup/
cp /etc/httpd/conf.d/zabbix.conf  /opt/zabbix-backup/
cp -R /usr/share/zabbix/ /opt/zabbix-backup/
cp -R /usr/share/doc/zabbix-* /opt/zabbix-backup/

# 升級zabbix源
rpm -Uvh https://repo.zabbix.com/zabbix/4.0/rhel/7/x86_64/zabbix-release-4.0-1.el7.noarch.rpm
# 升級zabbix
# yum upgrade zabbix-server-mysql zabbix-web-mysql zabbix-agent zabbix-proxy-mysql
yum clean all
yum upgrade zabbix-server-mysql zabbix-web-mysql zabbix-agent 

# 啟動zabbix
service zabbix-server start
service zabbix-agent start
service httpd start

# 檢查升級日志
tail -f /var/log/zabbix/zabbix_server.log

5044:20181101:212148.975 Starting Zabbix Server. Zabbix 4.0.1 (revision 86073).
  5044:20181101:212149.173 ****** Enabled features ******
  5044:20181101:212149.173 SNMP monitoring:           YES
  5044:20181101:212149.173 IPMI monitoring:           YES
  5044:20181101:212149.173 Web monitoring:            YES
  5044:20181101:212149.173 VMware monitoring:         YES
  5044:20181101:212149.173 SMTP authentication:       YES
  5044:20181101:212149.173 Jabber notifications:      YES
  5044:20181101:212149.173 Ez Texting notifications:  YES
  5044:20181101:212149.173 ODBC:                      YES
  5044:20181101:212149.173 SSH2 support:              YES
  5044:20181101:212149.173 IPv6 support:              YES
  5044:20181101:212149.173 TLS support:               YES
  5044:20181101:212149.173 ******************************
  5044:20181101:212149.173 using configuration file: /etc/zabbix/zabbix_server.conf
  5044:20181101:212149.276 current database version (mandatory/optional): 03040000/03040007
  5044:20181101:212149.360 required mandatory version: 04000000
  5044:20181101:212149.361 starting automatic database upgrade
  5044:20181101:212149.774 completed 0% of database upgrade
  5044:20181101:212149.775 completed 1% of database upgrade
  5044:20181101:212149.865 completed 2% of database upgrade
  5044:20181101:212149.867 completed 3% of database upgrade
  5044:20181101:212149.871 completed 4% of database upgrade
  5044:20181101:212149.874 completed 5% of database upgrade
  5044:20181101:212149.922 completed 6% of database upgrade
  5044:20181101:212150.015 completed 7% of database upgrade
  5044:20181101:212150.169 completed 8% of database upgrade
  5044:20181101:212150.314 completed 9% of database upgrade
  5044:20181101:212150.469 completed 10% of database upgrade
  5044:20181101:212150.523 completed 11% of database upgrade
  5044:20181101:212150.563 completed 12% of database upgrade
  5044:20181101:212150.565 completed 13% of database upgrade
  5044:20181101:212150.574 completed 14% of database upgrade
  5044:20181101:212150.621 completed 15% of database upgrade
  5044:20181101:212150.715 completed 16% of database upgrade
  5044:20181101:212150.809 completed 17% of database upgrade
  5044:20181101:212150.818 completed 18% of database upgrade
  5044:20181101:212150.867 completed 19% of database upgrade
  5044:20181101:212150.871 completed 20% of database upgrade
  5044:20181101:212150.959 completed 21% of database upgrade
  5044:20181101:212151.124 completed 22% of database upgrade
  5044:20181101:212151.209 completed 23% of database upgrade
  5044:20181101:212151.272 completed 24% of database upgrade
  5044:20181101:212151.275 completed 25% of database upgrade
  5044:20181101:212151.314 completed 26% of database upgrade
  5044:20181101:212152.118 completed 27% of database upgrade
  5044:20181101:212152.613 completed 28% of database upgrade
  5044:20181101:212153.271 completed 29% of database upgrade
  5044:20181101:212153.570 completed 30% of database upgrade
  5044:20181101:212154.869 completed 31% of database upgrade
  5044:20181101:212156.368 completed 32% of database upgrade
  5044:20181101:212156.665 completed 33% of database upgrade
  5044:20181101:212157.465 completed 34% of database upgrade
  5044:20181101:212157.820 completed 35% of database upgrade
  5044:20181101:212158.509 completed 36% of database upgrade
  5044:20181101:212200.662 completed 37% of database upgrade
  5044:20181101:212200.710 completed 38% of database upgrade
  5044:20181101:212200.715 completed 39% of database upgrade
  5044:20181101:212200.761 completed 40% of database upgrade
  5044:20181101:212200.807 completed 41% of database upgrade
  5044:20181101:212200.810 completed 42% of database upgrade
  5044:20181101:212200.811 completed 43% of database upgrade
  5044:20181101:212200.813 completed 44% of database upgrade
  5044:20181101:212200.815 completed 45% of database upgrade
  5044:20181101:212200.818 completed 46% of database upgrade
  5044:20181101:212200.913 completed 47% of database upgrade
  5044:20181101:212200.960 completed 48% of database upgrade
  5044:20181101:212201.013 completed 49% of database upgrade
  5044:20181101:212201.116 completed 50% of database upgrade
  5044:20181101:212201.119 completed 51% of database upgrade
  5044:20181101:212201.157 completed 52% of database upgrade
  5044:20181101:212201.160 completed 53% of database upgrade
  5044:20181101:212201.164 completed 54% of database upgrade
  5044:20181101:212201.166 completed 55% of database upgrade
  5044:20181101:212201.169 completed 56% of database upgrade
  5044:20181101:212201.206 completed 57% of database upgrade
  5044:20181101:212201.208 completed 58% of database upgrade
  5044:20181101:212201.305 completed 59% of database upgrade
  5044:20181101:212201.308 completed 60% of database upgrade
  5044:20181101:212201.311 completed 61% of database upgrade
  5044:20181101:212201.356 completed 62% of database upgrade
  5044:20181101:212201.363 completed 63% of database upgrade
  5044:20181101:212201.413 completed 64% of database upgrade
  5044:20181101:212201.414 completed 65% of database upgrade
  5044:20181101:212201.465 completed 66% of database upgrade
  5044:20181101:212201.517 completed 67% of database upgrade
  5044:20181101:212201.562 completed 68% of database upgrade
  5044:20181101:212201.656 completed 69% of database upgrade
  5044:20181101:212201.666 completed 70% of database upgrade
  5044:20181101:212201.719 completed 71% of database upgrade
  5044:20181101:212201.758 completed 72% of database upgrade
  5044:20181101:212201.760 completed 73% of database upgrade
  5044:20181101:212201.764 completed 74% of database upgrade
  5044:20181101:212201.766 completed 75% of database upgrade
  5044:20181101:212201.817 completed 76% of database upgrade
  5044:20181101:212201.862 completed 77% of database upgrade
  5044:20181101:212202.054 completed 78% of database upgrade
  5044:20181101:212202.112 completed 79% of database upgrade
  5044:20181101:212202.158 completed 80% of database upgrade
  5044:20181101:212202.210 completed 81% of database upgrade
  5044:20181101:212202.261 completed 82% of database upgrade
  5044:20181101:212202.315 completed 83% of database upgrade
  5044:20181101:212202.566 completed 84% of database upgrade
  5044:20181101:212202.609 completed 85% of database upgrade
  5044:20181101:212202.619 completed 86% of database upgrade
  5044:20181101:212202.656 completed 87% of database upgrade
  5044:20181101:212202.659 completed 88% of database upgrade
  5044:20181101:212202.661 completed 89% of database upgrade
  5044:20181101:212202.669 completed 90% of database upgrade
  5044:20181101:212202.761 completed 91% of database upgrade
  5044:20181101:212203.214 completed 92% of database upgrade
  5044:20181101:212203.360 completed 93% of database upgrade
  5044:20181101:212203.365 completed 94% of database upgrade
  5044:20181101:212203.403 completed 95% of database upgrade
  5044:20181101:212203.417 completed 96% of database upgrade
  5044:20181101:212203.467 completed 97% of database upgrade
  5044:20181101:212203.508 completed 98% of database upgrade
  5044:20181101:212203.564 completed 99% of database upgrade
  5044:20181101:212203.566 completed 100% of database upgrade
  5044:20181101:212203.566 database upgrade fully completed
  5044:20181101:212203.660 starting event name update forced by database upgrade
  5044:20181101:212203.706 completed 1% of event name update
  5044:20181101:212203.706 completed 2% of event name update
  5044:20181101:212203.706 completed 3% of event name update
  5044:20181101:212203.706 completed 4% of event name update
  5044:20181101:212203.706 completed 5% of event name update
  5044:20181101:212203.706 completed 6% of event name update
  5044:20181101:212203.706 completed 7% of event name update
  5044:20181101:212203.706 completed 8% of event name update
  5044:20181101:212203.706 completed 9% of event name update
  5044:20181101:212203.706 completed 10% of event name update
  5044:20181101:212203.706 completed 11% of event name update
  5044:20181101:212203.706 completed 12% of event name update
  5044:20181101:212203.707 completed 13% of event name update
  5044:20181101:212203.707 completed 14% of event name update
  5044:20181101:212203.707 completed 15% of event name update
  5044:20181101:212203.707 completed 16% of event name update
  5044:20181101:212203.707 completed 17% of event name update
  5044:20181101:212203.707 completed 18% of event name update
  5044:20181101:212203.707 completed 19% of event name update
  5044:20181101:212203.707 completed 20% of event name update
  5044:20181101:212203.707 completed 21% of event name update
  5044:20181101:212203.707 completed 22% of event name update
  5044:20181101:212203.707 completed 23% of event name update
  5044:20181101:212203.707 completed 24% of event name update
  5044:20181101:212203.707 completed 25% of event name update
  5044:20181101:212203.708 completed 26% of event name update
  5044:20181101:212203.708 completed 27% of event name update
  5044:20181101:212203.708 completed 28% of event name update
  5044:20181101:212203.708 completed 29% of event name update
  5044:20181101:212203.708 completed 30% of event name update
  5044:20181101:212203.708 completed 31% of event name update
  5044:20181101:212203.708 completed 32% of event name update
  5044:20181101:212203.710 completed 33% of event name update
  5044:20181101:212203.712 completed 34% of event name update
  5044:20181101:212203.714 completed 35% of event name update
  5044:20181101:212203.717 completed 36% of event name update
  5044:20181101:212203.717 completed 37% of event name update
  5044:20181101:212203.717 completed 38% of event name update
  5044:20181101:212203.717 completed 39% of event name update
  5044:20181101:212203.718 completed 40% of event name update
  5044:20181101:212203.718 completed 41% of event name update
  5044:20181101:212203.718 completed 42% of event name update
  5044:20181101:212203.718 completed 43% of event name update
  5044:20181101:212203.718 completed 44% of event name update
  5044:20181101:212203.718 completed 45% of event name update
  5044:20181101:212203.718 completed 46% of event name update
  5044:20181101:212203.718 completed 47% of event name update
  5044:20181101:212203.718 completed 48% of event name update
  5044:20181101:212203.719 completed 49% of event name update
  5044:20181101:212203.719 completed 50% of event name update
  5044:20181101:212203.758 completed 51% of event name update
  5044:20181101:212203.804 completed 52% of event name update
  5044:20181101:212203.804 completed 53% of event name update
  5044:20181101:212203.804 completed 54% of event name update
  5044:20181101:212203.804 completed 55% of event name update
  5044:20181101:212203.805 completed 56% of event name update
  5044:20181101:212203.805 completed 57% of event name update
  5044:20181101:212203.805 completed 58% of event name update
  5044:20181101:212203.805 completed 59% of event name update
  5044:20181101:212203.805 completed 60% of event name update
  5044:20181101:212203.805 completed 61% of event name update
  5044:20181101:212203.805 completed 62% of event name update
  5044:20181101:212203.805 completed 63% of event name update
  5044:20181101:212203.805 completed 64% of event name update
  5044:20181101:212203.805 completed 65% of event name update
  5044:20181101:212203.805 completed 66% of event name update
  5044:20181101:212203.806 completed 67% of event name update
  5044:20181101:212203.806 completed 68% of event name update
  5044:20181101:212203.806 completed 69% of event name update
  5044:20181101:212203.807 completed 70% of event name update
  5044:20181101:212203.807 completed 71% of event name update
  5044:20181101:212203.807 completed 72% of event name update
  5044:20181101:212203.807 completed 73% of event name update
  5044:20181101:212203.807 completed 74% of event name update
  5044:20181101:212203.807 completed 75% of event name update
  5044:20181101:212203.807 completed 76% of event name update
  5044:20181101:212203.807 completed 77% of event name update
  5044:20181101:212203.808 completed 78% of event name update
  5044:20181101:212203.808 completed 79% of event name update
  5044:20181101:212203.808 completed 80% of event name update
  5044:20181101:212203.808 completed 81% of event name update
  5044:20181101:212203.808 completed 82% of event name update
  5044:20181101:212203.808 completed 83% of event name update
  5044:20181101:212203.808 completed 84% of event name update
  5044:20181101:212203.808 completed 85% of event name update
  5044:20181101:212203.809 completed 86% of event name update
  5044:20181101:212203.809 completed 87% of event name update
  5044:20181101:212203.810 completed 88% of event name update
  5044:20181101:212203.810 completed 89% of event name update
  5044:20181101:212203.810 completed 90% of event name update
  5044:20181101:212203.810 completed 91% of event name update
  5044:20181101:212203.810 completed 92% of event name update
  5044:20181101:212203.810 completed 93% of event name update
  5044:20181101:212203.810 completed 94% of event name update
  5044:20181101:212203.811 completed 95% of event name update
  5044:20181101:212203.811 completed 96% of event name update
  5044:20181101:212203.811 completed 97% of event name update
  5044:20181101:212203.811 completed 98% of event name update
  5044:20181101:212203.811 completed 99% of event name update
  5044:20181101:212203.811 completed 100% of event name update
  5044:20181101:212205.304 event name update completed

Ubuntu

# 停止服務
service zabbix-server stop
service zabbix-agent stop
service apache2 stop

# 備份 zabbix 文件
mkdir /opt/zabbix-backup/
cp /etc/zabbix/zabbix_server.conf /opt/zabbix-backup/
cp /etc/apache2/conf-enabled/zabbix.conf /opt/zabbix-backup/
cp -R /usr/share/zabbix/ /opt/zabbix-backup/ 
cp -R /usr/share/doc/zabbix-* /opt/zabbix-backup/

# 升級zabbix源
rm -Rf /etc/apt/sources.list.d/zabbix.list
wget https://repo.zabbix.com/zabbix/4.0/ubuntu/pool/main/z/zabbix-release/zabbix-release_4.0-2+bionic_all.deb
dpkg -i zabbix-release_4.0-2+xenial_all.deb
apt-get update

# 添加時出現(xiàn)問題：dpkg: error: dpkg status database is locked by another process
rm /var/lib/dpkg/lock
dpkg --configure -a

# 升級zabbix
# apt-get install --only-upgrade zabbix-server-mysql zabbix-frontend-php zabbix-agent zabbix-proxy-mysql
apt-get install --only-upgrade zabbix-server-mysql zabbix-frontend-php zabbix-agent

# 啟動zabbix
service zabbix-server start
service zabbix-agent start
service apache2 start

docker

  1. 拉取最新鏡像
  2. 停止并刪除當前運行容器
  3. 用最新鏡像重新創(chuàng)建容器
  4. All Done
# 查找當前系統(tǒng)中使用的鏡像
docker images
# 拉取最新鏡像
docker pull zabbix/zabbix-web-nginx-mysql
docker pull zabbix/zabbix-server-mysql
# 查找容器ID
docker ps
# 導出之前的容器配置信息
docker inspect 14fd67405076
# 停止容器
docker stop 14fd67405076
docker kill 14fd67405076
# 刪除容器
docker rm 14fd67405076
# 用最新鏡像重新創(chuàng)建容器
docker run --name zabbix-server-mysql -t \
--link mysql-server:mysql \
-e DB_SERVER_HOST="mysql-server" \
-e MYSQL_DATABASE="zabbix" \
-e MYSQL_USER="zabbix" \
-e MYSQL_PASSWORD="zabbix" \
-e MYSQL_ROOT_PASSWORD="zabbix" \
-v /etc/localtime:/etc/localtime:ro \
-v /data/docker/zabbix/alertscripts:/usr/lib/zabbix/alertscripts \
-v /data/docker/zabbix/externalscripts:/usr/lib/zabbix/externalscripts \
-p 10051:10051 \
-d \
zabbix/zabbix-server-mysql

docker run --name zabbix-web-nginx-mysql -t \
--link mysql-server:mysql \
--link zabbix-server-mysql:zabbix-server \
-e DB_SERVER_HOST="mysql-server" \
-e MYSQL_DATABASE="zabbix" \
-e MYSQL_USER="zabbix" \
-e MYSQL_PASSWORD="zabbix" \
-e MYSQL_ROOT_PASSWORD="zabbix" \
-e PHP_TZ="Asia/Singapore" \
-p 80:80 \
-d \
zabbix/zabbix-web-nginx-mysql
?著作權歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
  • 人面猴
    序言：七十年代末，一起剝皮案震驚了整個濱河市枉疼，隨后出現(xiàn)的幾起案子皮假，更是在濱河造成了極大的恐慌，老刑警劉巖骂维，帶你破解...
    沈念sama閱讀 219,039評論 6贊 508
  • 死咒
    序言：濱河連續(xù)發(fā)生了三起死亡事件惹资，死亡現(xiàn)場離奇詭異，居然都是意外死亡航闺，警方通過查閱死者的電腦和手機褪测，發(fā)現(xiàn)死者居然都...
    沈念sama閱讀 93,426評論 3贊 395
  • 救了他兩次的神仙讓他今天三更去死
    文/潘曉璐 我一進店門，熙熙樓的掌柜王于貴愁眉苦臉地迎上來潦刃，“玉大人侮措，你說我怎么就攤上這事」愿埽” “怎么了分扎？”我有些...
    開封第一講書人閱讀 165,417評論 0贊 356
  • 道士緝兇錄：失蹤的賣姜人
    文/不壞的土叔 我叫張陵，是天一觀的道長胧洒。 經(jīng)常有香客問我畏吓，道長，這世上最難降的妖魔是什么卫漫？ 我笑而不...
    開封第一講書人閱讀 58,868評論 1贊 295
  • ?港島之戀（遺憾婚禮）
    正文 為了忘掉前任菲饼，我火速辦了婚禮，結果婚禮上列赎，老公的妹妹穿的比我還像新娘巴粪。我一直安慰自己，他們只是感情好，可當我...
    茶點故事閱讀 67,892評論 6贊 392
  • 惡毒庶女頂嫁案：這布局不是一般人想出來的
    文/花漫 我一把揭開白布肛根。 她就那樣靜靜地躺著辫塌，像睡著了一般。 火紅的嫁衣襯著肌膚如雪派哲。 梳的紋絲不亂的頭發(fā)上臼氨，一...
    開封第一講書人閱讀 51,692評論 1贊 305
  • 城市分裂傳說
    那天，我揣著相機與錄音芭届，去河邊找鬼储矩。 笑死，一個胖子當著我的面吹牛褂乍，可吹牛的內(nèi)容都是我干的持隧。 我是一名探鬼主播，決...
    沈念sama閱讀 40,416評論 3贊 419
  • 雙鴛鴦連環(huán)套：你想象不到人心有多黑
    文/蒼蘭香墨 我猛地睜開眼逃片，長吁一口氣：“原來是場噩夢啊……” “哼屡拨！你這毒婦竟也來了？” 一聲冷哼從身側(cè)響起褥实，我...
    開封第一講書人閱讀 39,326評論 0贊 276
  • 萬榮殺人案實錄
    序言：老撾萬榮一對情侶失蹤呀狼，失蹤者是張志新（化名）和其女友劉穎，沒想到半個月后损离，有當?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體哥艇，經(jīng)...
    沈念sama閱讀 45,782評論 1贊 316
  • ?護林員之死
    正文 獨居荒郊野嶺守林人離奇死亡，尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內(nèi)容為張勛視角 年9月15日...
    茶點故事閱讀 37,957評論 3贊 337
  • ?白月光啟示錄
    正文 我和宋清朗相戀三年僻澎，在試婚紗的時候發(fā)現(xiàn)自己被綠了貌踏。 大學時的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片。...
    茶點故事閱讀 40,102評論 1贊 350
  • 活死人
    序言：一個原本活蹦亂跳的男人離奇死亡窟勃，死狀恐怖哩俭，靈堂內(nèi)的尸體忽然破棺而出，到底是詐尸還是另有隱情拳恋，我是刑警寧澤凡资，帶...
    沈念sama閱讀 35,790評論 5贊 346
  • ?日本核電站爆炸內(nèi)幕
    正文 年R本政府宣布，位于F島的核電站谬运，受9級特大地震影響隙赁，放射性物質(zhì)發(fā)生泄漏。R本人自食惡果不足惜梆暖，卻給世界環(huán)境...
    茶點故事閱讀 41,442評論 3贊 331
  • 男人毒藥：我在死后第九天來索命
    文/蒙蒙 一伞访、第九天 我趴在偏房一處隱蔽的房頂上張望。 院中可真熱鬧轰驳，春花似錦厚掷、人聲如沸弟灼。這莊子的主人今日做“春日...
    開封第一講書人閱讀 31,996評論 0贊 22
  • 一樁弒父案冒黑，背后竟有這般陰謀
    文/蒼蘭香墨 我抬頭看了看天上的太陽田绑。三九已至，卻和暖如春抡爹，著一層夾襖步出監(jiān)牢的瞬間掩驱，已是汗流浹背。 一陣腳步聲響...
    開封第一講書人閱讀 33,113評論 1贊 272
  • 情欲美人皮
    我被黑心中介騙來泰國打工冬竟， 沒想到剛下飛機就差點兒被人妖公主榨干…… 1. 我叫王不留欧穴，地道東北人。 一個月前我還...
    沈念sama閱讀 48,332評論 3贊 373
  • 代替公主和親
    正文 我出身青樓泵殴，卻偏偏與公主長得像涮帘，于是被迫代替她去往敵國和親。 傳聞我的和親對象是個殘疾皇子笑诅，可洞房花燭夜當晚...
    茶點故事閱讀 45,044評論 2贊 355

推薦閱讀更多精彩內(nèi)容

  • 先附上zabbix官方安裝說明： https://www.zabbix.com/documentation/3.4...
    fantasymango閱讀 845評論 0贊 1
  • Zabbix 安裝 本文是參考 《Zabbix 教程從入門到精通v1.0》 所作的實驗调缨。 大綱： 一、LNMP 環(huán)...
    C86guli閱讀 1,555評論 0贊 8
  • 前言 Zabbix是目前最為主流的開源監(jiān)控方案之一苟鸯，部署本身并不困難，難的是深入理解棚点。根據(jù)在生產(chǎn)環(huán)境的實踐從新版Z...
    王奧OX閱讀 814評論 0贊 1
  • Zabbix簡介 Zabbix官方網(wǎng)站Zabbix中文文檔 本文系統(tǒng)環(huán)境是CentOS7x86_64, Zabbi...
    Zhang21閱讀 8,006評論 0贊 37
  • # Python 資源大全中文版 我想很多程序員應該記得 GitHub 上有一個 Awesome - XXX 系列...
    aimaile閱讀 26,489評論 6贊 427