Cómo habilitar el monitoreo de servicios en CWP Control Panel ServicesMonitor (systemd)

在LinuxEn el servidor, mantenga el servicio funcionando de manera estable, para el sitio webSEOMuy importante.

Panel de control de CWPLe ayudará a través de herramientas de seguimiento del servicio.

¿Cómo habilitar ServicesMonitor (systemd) en el panel de control de CWP?

Para habilitar la supervisión del servicio en CWP:

1. conéctate a tuCWP安装
2. EncontrarConfiguración de servicios->Monitor de servicios( sistemad )选项
3. Seleccione/Ingrese:
   Habilitar deshabilitar- Esto habilitará/deshabilitará el monitoreo del servicio.
   Email notificacionesEnviar a: ingrese la dirección de correo electrónico donde recibirá las notificaciones.
   Revisa cada- intervalo de tiempo entre controles
4. Seleccione el servicio que desea monitorear, por ejemplo: mariadb.service, monit.service
5. Haga clic en提交botón.Verá un mensaje 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

Nota:

• 如果estado del sistemael servicio esUnknown,La supervisión no funcionará para los servicios.
• Los servicios seleccionados para monitorear se guardarán en un archivo /usr/local/etc/services-monitor-systemden.
• Los trabajos cron de supervisión se pueden encontrar en el archivo/etc/cron.d/svcMonitor-systemd中aparecer.

también puedes pasarchkconfigComando para agregar/eliminar servicios manualmente:

chkconfig service_name on
chkconfig service_name off

Por ejemplo, cuando todos los servicios disponibles estén habilitados, mostraremos mensajes 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

Panel de control de CWP Habilitar ServicesMonitor (systemd) Tutorial en video

A continuación se muestra cómo el panel de control de CWP en este artículo habilita el monitoreo de servicios ServicesMonitor (systemd)YouTubeVideotutorial▼