Paano paganahin ang pagsubaybay sa serbisyo sa CWP Control Panel ServicesMonitor (systemd)

在LinuxSa server, panatilihing matatag ang paggana ng serbisyo, para sa websiteSEOSobrang importante.

CWP Control PanelTutulungan ka sa pamamagitan ng mga tool sa pagsubaybay sa serbisyo.

Paano paganahin ang ServicesMonitor (systemd) sa control panel ng CWP?

Upang paganahin ang pagsubaybay sa serbisyo sa CWP:

1. kumonekta sa iyongCWP安装
2. hanapinConfig ng Mga Serbisyo->ServicesMonitor( systemd )选项
3. Piliin/Ipasok:
   Payagan hindi payagan- Ito ay paganahin/i-disable ang pagsubaybay sa serbisyo.
   Email mga abisoIpadala sa - Ilagay ang email address kung saan makakatanggap ka ng mga notification.
   Suriin ang bawat- agwat ng oras sa pagitan ng mga tseke
4. Piliin ang serbisyong gusto mong subaybayan, halimbawa: mariadb.service, monit.service
5. i-click提交pindutan.Makakakita ka ng mensahe ng kumpirmasyon:

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

Tandaan:

• 如果katayuan ng systemdserbisyo ayUnknown,Hindi gagana ang pagsubaybay para sa mga serbisyo.
• Ang mga napiling serbisyo na susubaybayan ay ise-save sa file /usr/local/etc/services-monitor-systemdsa.
• Ang pagsubaybay sa mga trabaho sa cron ay matatagpuan sa file/etc/cron.d/svcMonitor-systemd中itaas.

Makakapasa ka rinchkconfigUtos na manu-manong magdagdag/mag-alis ng mga serbisyo:

chkconfig service_name on
chkconfig service_name off

Halimbawa, kapag pinagana ang lahat ng magagamit na serbisyo, magpapakita kami ng mga mensahe ng cron gaya ng:

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 Control Panel Paganahin ang ServicesMonitor (systemd) Tutorial sa Video

Ang sumusunod ay kung paano pinapagana ng CWP control panel ang pagsubaybay sa serbisyo ServicesMonitor (systemd) sa artikulong itoYouTubeTutorial sa Video▼