Come abilitare il monitoraggio del servizio in CWP Control Panel ServicesMonitor (systemd)

在LinuxSul server, mantieni il servizio in esecuzione stabile, per il sito webGestione SEOMolto importante.

Pannello di controllo CWPTi aiuterà attraverso strumenti di monitoraggio del servizio.

Come abilitare ServicesMonitor (systemd) nel pannello di controllo CWP?

Per abilitare il monitoraggio del servizio in CWP:

1. connettiti al tuoCWP安装
2. TrovaServizi Config->ServicesMonitor( systemd )选项
3. Seleziona/Inserisci:
   Abilita / Disabilita- Ciò abiliterà/disabilita il monitoraggio del servizio.
   EmainotificheInvia a - Inserisci l'indirizzo email a cui riceverai le notifiche.
   Controlla ogni- intervallo di tempo tra i controlli
4. Seleziona il servizio che desideri monitorare, ad esempio: mariadb.service, monit.service
5. Clicca su提交pulsante.Vedrai un messaggio di conferma:

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

precauzioni:

• 如果stato di sistemail servizio èUnknown,Il monitoraggio non funzionerà per i servizi.
• I servizi selezionati da monitorare verranno salvati in un file /usr/local/etc/services-monitor-systemdIn.
• Il monitoraggio dei lavori cron può essere trovato nel file/etc/cron.d/svcMonitor-systemd中uscire fuori.

Puoi anche passarechkconfigComando per aggiungere/rimuovere manualmente i servizi:

chkconfig service_name on
chkconfig service_name off

Ad esempio, quando tutti i servizi disponibili sono abilitati, visualizzeremo messaggi cron come:

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

Pannello di controllo CWP Abilita Tutorial video ServicesMonitor (systemd).

Di seguito è riportato il modo in cui il pannello di controllo CWP abilita il monitoraggio del servizio ServicesMonitor (systemd) in questo articoloYouTubeTutorial video▼