Cum să activați monitorizarea serviciului în CWP Control Panel ServicesMonitor (systemd)

înLinuxPe server, mențineți serviciul să funcționeze stabil, pentru site-ul webSEOFoarte important.

Panoul de control CWPVă va ajuta cu instrumentele de monitorizare a serviciilor.

Cum se activează ServicesMonitor (systemd) în panoul de control CWP?

Pentru a activa monitorizarea serviciului în CWP:

1. conectați-vă la dvsCWP安装
2. găsiServicii Configurare->ServicesMonitor( systemd )选项
3. Selectați/Introduceți:
   Permite dezactivarea--Acest lucru va activa/dezactiva monitorizarea serviciului.
   Email notificăriTrimite către – Introduceți adresa de e-mail la care veți primi notificări.
   Verificați fiecare——Intervalul de timp dintre două verificări
4. Selectați serviciul pe care doriți să-l monitorizați, de exemplu: mariadb.service, monit.service
5. clic提交buton. Veți vedea un mesaj de confirmare:

Service Monitoring is not enabled
Enabling monitoring in cron
MAILTO=cwp1@ chenweilaing.com
*/15 * * * * root /usr/local/bin/svcMonitor-systemd
Monitoring Enabled: Yes

Măsuri de precauție:

• 如果starea systemdserviciul esteUnknown,Monitorizarea nu va funcționa pentru servicii.
• Serviciile selectate pentru a fi monitorizate vor fi salvate în fișier /usr/local/etc/services-monitor-systemdîn.
• Monitorizarea joburilor cron se poate face în fișier/etc/cron.d/svcMonitor-systemd中dă mai tare.

Poți și să trecichkconfigComenzi pentru adăugarea/eliminarea manuală a serviciilor:

chkconfig service_name on
chkconfig service_name off

De exemplu, când toate serviciile disponibile sunt activate, vom afișa mesaje cron precum:

From: (Cron Daemon) <[email protected]>
Subject: Cron <root@cwp1> /usr/local/bin/svcMonitor-systemd

Restarted service amavisd.service on cwp1 at Sat Mar 31 01:00:01 EDT 2018 Job for amavisd.service failed because the control process exited with error code. See “systemctl status amavisd.service” and “journalctl -xe” for details.

Restarted service arp-ethers.service on cwp1 at Sat Mar 31 01:00:03 EDT 2018 Restarted service [email protected] on cwp1 at Sat Mar 31 01:00:04 EDT 2018 Failed to stop [email protected]: Unit name [email protected] is missing the instance name.

See system logs and ‘systemctl status [email protected]‘ for details.

Failed to get load state of [email protected]: Unit name [email protected] is missing the instance name.

Failed to start [email protected]: Unit name [email protected] is missing the instance name.

See system logs and ‘systemctl status [email protected]‘ for details.

Restarted service console-shell.service on cwp1 at Sat Mar 31 01:00:05 EDT 2018 Restarted service garb.service on cwp1 at Sat Mar 31 01:00:06 EDT 2018 Restarted service [email protected] on cwp1 at Sat Mar 31 01:00:07 EDT 2018 Failed to stop [email protected]: Unit name [email protected] is missing the instance name.

See system logs and ‘systemctl status [email protected]‘ for details.

Failed to get load state of [email protected]: Unit name [email protected] is missing the instance name.

Failed to start [email protected]: Unit name [email protected] is missing the instance name.

See system logs and ‘systemctl status [email protected]‘ for details.

Restarted service ntalk.service on cwp1 at Sat Mar 31 01:00:09 EDT 2018 Job for ntalk.service failed because a configured resource limit was exceeded. See “systemctl status ntalk.service” and “journalctl -xe” for details.

Restarted service rdisc.service on cwp1 at Sat Mar 31 01:00:10 EDT 2018 Job for rdisc.service failed because the control process exited with error code. See “systemctl status rdisc.service” and “journalctl -xe” for details.

Restarted service [email protected] on cwp1 at Sat Mar 31 01:00:17 EDT 2018 Failed to stop [email protected]: Unit name [email protected] is missing the instance name.

See system logs and ‘systemctl status [email protected]‘ for details.

Failed to get load state of [email protected]: Unit name [email protected] is missing the instance name.

Failed to start [email protected]: Unit name [email protected] is missing the instance name.

See system logs and ‘systemctl status [email protected]‘ for details.

Restarted service svnserve.service on cwp1 at Sat Mar 31 01:00:18 EDT 2018 Job for svnserve.service failed because the control process exited with error code. See “systemctl status svnserve.service” and “journalctl -xe” for details.

Restarted service tcsd.service on cwp1 at Sat Mar 31 01:00:19 EDT 2018 Job for tcsd.service failed because the control process exited with error code. See “systemctl status tcsd.service” and “journalctl -xe” for details.

Restarted service vzfifo.service on cwp1 at Sat Mar 31 01:00:20 EDT 2020

Panoul de control CWP activează tutorialul video ServicesMonitor (systemd).

Următoarele sunt cum să activați monitorizarea serviciilor ServicesMonitor (systemd) în panoul de control CWP din acest articolYouTubeTutorial video▼