Slik aktiverer du tjenesteovervåking i CWP Control Panel ServicesMonitor (systemd)

在LinuxPå serveren, hold tjenesten i gang stabilt, for nettstedetSEOVeldig viktig.

CWP kontrollpanelVil hjelpe deg gjennom tjenesteovervåkingsverktøy.

Hvordan aktiverer jeg ServicesMonitor (systemd) i CWP-kontrollpanelet?

Slik aktiverer du tjenesteovervåking i CWP:

1. koble til dinCWP安装
2. FinneTjenester Konfigurasjon-> Tjenester Monitor( systemd )选项
3. Velg/skriv inn:
   På av- Dette vil aktivere/deaktivere tjenesteovervåking.
   Email varslerSend til - Skriv inn e-postadressen der du vil motta varsler.
   Sjekk hver- tidsintervall mellom kontrollene
4. Velg tjenesten du vil overvåke, for eksempel: mariadb.service, monit.service
5. Klikk på提交knapp.Du vil se en bekreftelsesmelding:

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

Forsiktig:

• i tilfellesystemd statustjenesten erUnknown,Overvåking vil ikke fungere for tjenester.
• Utvalgte tjenester som skal overvåkes vil bli lagret i filen /usr/local/etc/services-monitor-systemdi.
• Overvåking av cron-jobber finner du i filen/etc/cron.d/svcMonitor-systemd中skru opp.

Du kan også beståchkconfigKommando for å legge til/fjerne tjenester manuelt:

chkconfig service_name on
chkconfig service_name off

For eksempel, når alle tilgjengelige tjenester er aktivert, vil vi vise cron-meldinger 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 Kontrollpanel Aktiver ServicesMonitor (systemd) videoopplæring

Følgende er hvordan CWP-kontrollpanelet aktiverer tjenesteovervåking ServicesMonitor (systemd) i denne artikkelenYouTubeVideoopplæring▼