Servicemonitoring inschakelen in CWP Control Panel ServicesMonitor (systemd)

在LinuxHoud de service op de server stabiel, voor de websiteSEOErg belangrijk.

CWP-configuratieschermHelpt u door middel van servicemonitoringtools.

Hoe ServicesMonitor (systemd) inschakelen in het CWP-configuratiescherm?

Om servicebewaking in CWP in te schakelen:

1. verbinding maken met uwCWP安装
2. VindenServices Config->ServicesMonitor( systemd )选项
3. Selecteer/Voer in:
   Inschakelen / uitschakelen- Hiermee wordt servicebewaking in-/uitgeschakeld.
   EmaiIk meldingenVerzenden naar - Voer het e-mailadres in waarop u meldingen ontvangt.
   Controleer elke- tijdsinterval tussen controles
4. Selecteer de service die u wilt controleren, bijvoorbeeld: mariadb.service, monit.service
5. Klik op提交knop.U ziet een bevestigingsbericht:

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

voorzorgsmaatregelen:

• 如果systeemstatusservice isUnknown,Monitoring werkt niet voor services.
• Geselecteerde services om te controleren worden opgeslagen in een bestand /usr/local/etc/services-monitor-systemdin.
• Monitoring cron jobs zijn te vinden in het bestand/etc/cron.d/svcMonitor-systemd中harder zetten.

U kunt ook passerenchkconfigOpdracht om handmatig services toe te voegen/te verwijderen:

chkconfig service_name on
chkconfig service_name off

Wanneer bijvoorbeeld alle beschikbare services zijn ingeschakeld, zullen we cron-berichten weergeven, zoals:

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

CWP-configuratiescherm ServicesMonitor (systemd) Videozelfstudie inschakelen

Het volgende is hoe het CWP-configuratiescherm in dit artikel servicebewaking mogelijk maakt ServicesMonitor (systemd)YouTubeVideo-zelfstudie▼