Com habilitar la supervisió del servei al tauler de control CWP ServicesMonitor (systemd)

在LinuxAl servidor, manteniu el servei funcionant de manera estable per al lloc webSEOMolt important.

Tauler de control CWPT'ajudarà amb les eines de seguiment del servei.

Com habilitar ServicesMonitor (systemd) al tauler de control CWP?

Per habilitar la supervisió del servei a CWP:

1. connecta amb el teuCWP安装
2. trobarConfiguració de serveis->ServicesMonitor( systemd )选项
3. Seleccioneu/Introduïu:
   Activar desactivar- Això habilitarà/desactivarà la supervisió del servei.
   Email notificacionsEnviar a: introduïu l'adreça de correu electrònic on rebreu les notificacions.
   Comproveu cada- Interval de temps entre comprovacions
4. Seleccioneu el servei que voleu supervisar, per exemple: mariadb.service, monit.service
5. Fer clic a提交botó.Veureu un missatge de confirmació:

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

Nota:

• Siestat del sistemael servei ésUnknown,El seguiment no funcionarà per als serveis.
• Els serveis seleccionats per supervisar es desaran al fitxer /usr/local/etc/services-monitor-systemddins.
• El seguiment de treballs cron es pot trobar al fitxer/etc/cron.d/svcMonitor-systemd中apareix.

També pots passarchkconfigOrdre per afegir/eliminar serveis manualment:

chkconfig service_name on
chkconfig service_name off

Per exemple, quan tots els serveis disponibles estiguin habilitats, mostrarem missatges cron com ara:

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

Tauler de control CWP Activar ServicesMonitor (systemd) Tutorial de vídeo

A continuació es mostra com el tauler de control CWP d'aquest article permet la supervisió del servei ServicesMonitor (systemd)YouTubeVídeo tutorial▼