Quomodo processus Monitae in Vestae CP decuriae CentOS 7 systematis configurare?

ad priusChen WeiliangBlog communicavitCentOS 6 Tutorial instituere et configurare Monit ▼

How does CentOS 6 use Monit ad monitor? Linux institutionem et uninstallation Monit tutorial

Quot facit CentOS 6 usus monitor vigilantia? Monitor Linux institutionem et uninstallation monitor vigilantia programmatio est aperta fons monitoring instrumentum pro Linux operandi ratio, auxilium web browser ad processus systematis monitoris uti potest, cum progressio vel ministerium deficit et descendit, monit facere potest...

Sed in CentOS 7 configurationeMonit magnaProgressio, cum aliquibus differentiis a CentOS 6, non prorsus eadem est.

Quomodo Monit vigilantia programma in VestaCP decuria CentOS 7 systematis instituere?

Hoc doceo focuses in: Quomodo institutionem Monit vigilantia programmatis in VestaCP panel currit in CentOS 7 servo? CentOS 7 ratio VestaCP tabella, quomodo Monit configurationem statuo? Quid est Monit? Monit parvum instrumentum ad systemata Unix administrandi et vigilantia...

si vestriLinuxHospes utitur systematis CentOS VII. Monit in Vestae CP insertis tabulis, hanc discessionem sequi potes ut programmata Monit vigilantia configurare possit.

Monit vigilantia processus muneris

Sequentia est ministerium configurationis contenti processus monitoris (delere aliqua officia vigilantia minus adhibita);

Monit magna configuratione

Monit configuration file nomina diversa sunt pro CentOS 6 & 7;

• Nomen Configurationis Monit fasciculi CentOS 6 est "monit.conf"
• Nomen Configurationis Monit fasciculi CentOS 7 est "monitrc"

cum SFTP * 软件Postquam intrans Linux tuum servo, lima configurationem Monit ▼

/etc/monitrc

Configurationem sequentem adde contentum huic fasciculi "monitrc" ▼

##
## 陈沩亮博客示例monit配置文件说明：
## 1. 域名以 www.etufo.org 为例。
## 2. 后面带xxx的均是举例用的名字，需要根据自己的需要修改。
##
################################################## #############################
## Monit control file
################################################## #############################
#
# 检查周期，默认为2分钟，对于网站来说有点长，可以根据需要自行调节，这改成30秒。
set daemon 30

include /etc/monit.d/*

# 日志文件
set logfile /var/log/monit.log

#
# 邮件通知服务器
#
#set mailserver mail.example.com
set mailserver localhost with timeout 30 seconds

#
# 通知邮件的格式设置，下面是默认格式供参考
#
## Monit by default uses the following alert mail format:
##
## --8<--
## From: monit@$HOST # sender
## Subject: monit alert -- $EVENT $SERVICE # subject
##
## $EVENT Service $SERVICE #
## #
## Date: $DATE #
## Action: $ACTION #
## Host: $HOST # body
## Description: $DESCRIPTION #
## #
## Your faithful employee, #
## monit #
## --8<--
##
## You can override the alert message format or its parts such as subject
## or sender using the MAIL-FORMAT statement. Macros such as $DATE, etc.
## are expanded on runtime. For example to override the sender:
#
# 简单的，这只改了一下发送人，有需要可以自己修改其它内容。
set mail-format { from: admin@xxxx }

# 设置邮件通知接收者。建议发到gmail，方便邮件过滤。
set alert xxx@xxxx

set httpd port 2812 and #设置http监控页面的端口
use address www.etufo.org # http监控页面的IP或域名
##allow localhost # 允许本地访问
##allow 203.82.90.239 # 允许指定IP访问
allow user:password # 访问用户名密码

################################################## #############################
## Services
################################################## #############################
#
# 系统整体运行状况监控，默认的就可以，可以自己去微调
#
# 系统名称，可以是IP或域名
#check system www.etufo.org
# if loadavg (1min) > 4 then alert
# if loadavg (5min) > 2 then alert
# if memory usage > 75% then alert
# if cpu usage (user) > 70% then alert
# if cpu usage (system) > 30% then alert
# if cpu usage (wait) > 20% then alert


# 可选的ssl端口的监控，如果有的话
# if failed port 443 type tcpssl protocol http
# with timeout 15 seconds
# then restart

# 监控mariadb
check process mysql with pidfile /var/run/mariadb/mariadb.pid
start program = "/usr/bin/systemctl start mariadb"
stop program = "/usr/bin/systemctl stop mariadb"
if failed host 127.0.0.1 port 3306 for 2 cycles then restart
if 2 restarts within 4 cycles then timeout

# 监控httpd
check process httpd with pidfile /var/run/httpd/httpd.pid
    start program = "/usr/bin/systemctl start httpd"
    stop program = "/usr/bin/systemctl stop httpd"
#    if children > 120 for 2 cycles then restart
#    if failed host localhost port 8080 protocol http for 2 cycles then restart
#    if 4 restarts within 10 cycles then timeout
  
# 监控nginx
check process nginx with pidfile /var/run/nginx.pid
    start program = "/usr/bin/systemctl start nginx"
    stop program = "/usr/bin/systemctl stop nginx"
#    if failed host localhost port 443 protocol http for 2 cycles then restart
#    if 4 restarts within 10 cycles then timeout

# 监控sshd
check process sshd with pidfile /var/run/sshd.pid
start program = "/usr/bin/systemctl start sshd"
stop program = "/usr/bin/systemctl stop sshd"
if failed host localhost port 22 protocol ssh for 2 cycles then restart
if 4 restarts within 10 cycles then timeout

# 监控vesta-nginx
check process vesta-nginx with pidfile /var/run/vesta-nginx.pid
start program = "/usr/bin/systemctl start vesta"
stop program = "/usr/bin/systemctl stop vesta"
if failed host localhost port 8083 protocol https for 2 cycles then restart
if 4 restarts within 10 cycles then timeout

# 监控vesta-php
check process vesta-php with pidfile /var/run/vesta-php.pid
start program = "/usr/bin/systemctl start vesta"
stop program = "/usr/bin/systemctl stop vesta"
if failed host localhost port 8083 protocol https for 2 cycles then restart
if 4 restarts within 10 cycles then timeout

# 监控vsftpd
check process vsftpd with match vsftpd
start program = "/usr/bin/systemctl start vsftpd"
stop program = "/usr/bin/systemctl stop vsftpd"
if failed host localhost port 21 protocol ftp for 2 cycles then restart
if 4 restarts within 10 cycles then timeout

#监控crond
check process crond with pidfile /var/run/crond.pid
start program = "/usr/bin/systemctl start crond"
stop program = "/usr/bin/systemctl stop crond"
if 5 restarts within 5 cycles then timeout

#监控dovecot
check process dovecot with pidfile /var/run/dovecot/master.pid
start program = "/usr/bin/systemctl start dovecot"
stop program = "/usr/bin/systemctl stop dovecot"
if failed host localhost port 143 protocol imap for 2 cycles then restart
if 4 restarts within 10 cycles then timeout

#监控exim
check process exim with pidfile /var/run/exim.pid
start program "/usr/bin/systemctl start exim"
stop program "/usr/bin/systemctl stop exim"
if failed host localhost port 25 protocol smtp for 2 cycles then restart
if 4 restarts within 10 cycles then timeout

Si contentus configurationem MONIT mutaveris, opus est ut sileo Monit officium ut effectum ▼

systemctl restart monit

Renovatio die 2018 Maii 5:

cd /etc/monit.d/
git clone https://github.com/infinitnet/vesta-centos7-monit.git ./ && rm -f README.md
myip=1.2.3.4
sed -i 's/host localhost/host '$myip'/g' /etc/monit.d/*.conf
systemctl restart monit

• Locum tuum IP commune1.2.3.4.

git bash imperium invenire non potuit quia error accideret ▼

CentOS 7 error git vercundus imperium non inveni linux

Post VestaCP imperium panel insertis, cum Monit vigilantia programmatis figurans: git clone https://github.com/infinitnet/vesta-centos7-monit.git ./ && rm -f README.md Error nuntius apparet: -bash: git : com...

Patet etiam quod post hoc praeceptum intrantes ▼ .

sed -i 's/host localhost/host '$myip'/g' /etc/monit.d/*.conf

Hoc errore nuntius videtur ▼

sed: can't read /etc/monit.d/*.conf: No such file or directory

Monit log visum errore

SSH visum monit.log stipes lima imperium ▼

tailf /var/log/monit.log

• SSH ut monit.log fasciculum speculari, solum ultimae 10 lineae lignorum ostendi possunt.

SFTP login commendatur /var/log/monit.log ut plene videre statum prioris monit.log file log.

Error electronica mittens

Si Monit mail mitti non potest, nuntius sequens error ▼e apparebit

error : Cannot open a connection to the mailserver localhost:25 -- Operation now in progress
error : Mail: Delivery failed -- no mail server is available

Fix email mittens errores

Chen WeiliangCommendatur utGmail ESMTP ▼

set mailserver smtp.gmail.com port 587
username "[email protected]"
password "password"
using tlsv1
with timeout 30 seconds

Solutio est reponere statuto electronico servitori in Monit configuration file, quaeso hanc doceo pro singulis ▼ . reprimendam

Monit log epistulae promptae: 534 5.7.14 https://support.google.com/mail/answer/78754 - gsmtp

Monit vigilantia programma, quid facerem si servom localem constituo cum timeout 30 secundis, sed epistulam mittere non desino?Chen Weiliang suggessit ut Gmail ESMTP ▼semtp.gmail.com portum 587 usoris Gmail invenias pone

statistic error filesystem

Si errores sequentes inveneris in monit.log fasciculi stipes ▼

filesystem statistic error: cannot read /proc/diskstats -- No such file or directory

• Probabiliter quod Linux defaltis ad minimam institutionem VestaCPpanel, non est /proc/diskstats Orbis status magna lima.

statistic errores propono filesystem

I step:SSH in /etc/monit.d catalogue ▼

cd /etc/monit.d

I step:Delere Monit officium magna file "root-space.conf" ▼

rm -rf root-space.conf

I step:SSH sileo Monit vigilantia ▼

systemctl restart monit.service

Monit Command (Special for CentOS 7)

View Monit startup status ▼

systemctl status monit.service

Monit satus ad ministerium ▼

systemctl start monit.service

Monit officium claudere ▼ *

systemctl stop monit.service

Sileo Monit ministerium ▼

systemctl restart monit

Incipit Monit officium in tabernus ▼

systemctl enable monit.service

Illuminationes interdum Monit ministerium ▼

systemctl disable monit.service