Como habilitar a supervisión do servizo no panel de control CWP ServicesMonitor (systemd)

enLinuxNo servidor, mantén o servizo funcionando de forma estable para o sitio webSEOMoi importante.

Panel de control CWPAxudarache a través das ferramentas de seguimento do servizo.

Como habilitar ServicesMonitor (systemd) no panel de control CWP?

Para activar a supervisión do servizo en CWP:

1. conéctate ao teuCWP安装
2. BuscarServizos Config->ServicesMonitor( systemd )选项
3. Seleccionar/Introducir:
   Habilitar Deshabilitar- Isto activará/desactivará o seguimento do servizo.
   Email notificaciónsEnviar a - Introduza o enderezo de correo electrónico onde recibirá as notificacións.
   Comproba cada- intervalo de tempo entre comprobacións
4. Seleccione o servizo que quere supervisar, por exemplo: mariadb.service, monit.service
5. Prema en提交botón.Verás unha mensaxe de confirmación:

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

coidado:

• 如果estado do sistemaservizo éUnknown,A vixilancia non funcionará para os servizos.
• Os servizos seleccionados para supervisar gardaranse no ficheiro /usr/local/etc/services-monitor-systemddentro.
• No ficheiro pódese atopar o seguimento dos traballos cron/etc/cron.d/svcMonitor-systemd中aparecer.

Tamén podes pasarchkconfigComando para engadir/eliminar servizos manualmente:

chkconfig service_name on
chkconfig service_name off

Por exemplo, cando todos os servizos dispoñibles estean activados, mostraremos mensaxes cron como:

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 Activar ServicesMonitor (systemd) Videotutorial

O seguinte é como o panel de control CWP deste artigo permite a supervisión do servizo ServicesMonitor (systemd)YouTubeVideotutorial▼