Sådan aktiveres serviceovervågning i CWP Kontrolpanel ServicesMonitor (systemd)

在LinuxPå serveren skal du holde tjenesten kørende stabilt for webstedetSEOMeget vigtigt.

CWP kontrolpanelVil hjælpe dig gennem serviceovervågningsværktøjer.

Hvordan aktiveres ServicesMonitor (systemd) i CWP kontrolpanel?

Sådan aktiverer du serviceovervågning i CWP:

1. oprette forbindelse til dinCWP安装
2. FindServices Config->ServicesMonitor( systemd )选项
3. Vælg/indtast:
   Aktivere deaktivere- Dette vil aktivere/deaktivere serviceovervågning.
   Email meddelelserSend til - Indtast den e-mailadresse, hvor du vil modtage meddelelser.
   Tjek hver- tidsinterval mellem kontroller
4. Vælg den tjeneste, du vil overvåge, for eksempel: mariadb.service, monit.service
5. Klik på提交knap.Du vil se en bekræftelsesmeddelelse:

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

注意 事项:

• 如果systemd statusservice erUnknown,Overvågning vil ikke fungere for tjenester.
• Udvalgte tjenester, der skal overvåges, vil blive gemt i filen /usr/local/etc/services-monitor-systemdi.
• Overvågning af cron-job kan findes i filen/etc/cron.d/svcMonitor-systemd中Skru op.

Du kan også beståchkconfigKommando til manuelt at tilføje/fjerne tjenester:

chkconfig service_name on
chkconfig service_name off

For eksempel, når alle tilgængelige tjenester er aktiveret, vil vi vise cron-meddelelser såsom:

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 Kontrolpanel Aktiver ServicesMonitor (systemd) Videovejledning

Det følgende er, hvordan CWP-kontrolpanelet i denne artikel aktiverer serviceovervågning ServicesMonitor (systemd)YouTubeVideotutorial▼