Como habilitar o monitoramento de serviço no CWP Control Panel ServicesMonitor (systemd)

在LinuxNo servidor, mantenha o serviço funcionando de forma estável, para o siteSEOMuito importante.

Painel de controle CWPIrá ajudá-lo através de ferramentas de monitoramento de serviço.

Como habilitar o ServicesMonitor (systemd) no painel de controle do CWP?

Para habilitar o monitoramento de serviço no CWP:

1. conecte-se ao seuCWPInstalação
2. AcharConfiguração de Serviços->Monitor de Serviços( sistema )选项
3. Selecione/Insira:
   Habilitar desabilitar- Isso ativará/desativará o monitoramento de serviço.
   Email notificaçõesEnviar para - Digite o endereço de e-mail onde você receberá notificações.
   Verifique a cada- intervalo de tempo entre as verificações
4. Selecione o serviço que deseja monitorar, por exemplo: mariadb.service, monit.service
5. Clique em提交botão.Você verá uma mensagem de confirmação:

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

Nota:

• 如果status do sistemaserviço éUnknown,O monitoramento não funcionará para serviços.
• Os serviços selecionados para monitorar serão salvos em arquivo /usr/local/etc/services-monitor-systemdMédio.
• Os trabalhos cron de monitoramento podem ser encontrados no arquivo/etc/cron.d/svcMonitor-systemd中virar para cima.

Você também pode passarchkconfigComando para adicionar/remover serviços manualmente:

chkconfig service_name on
chkconfig service_name off

Por exemplo, quando todos os serviços disponíveis estiverem habilitados, exibiremos mensagens 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

Painel de controle CWP Habilitar ServicesMonitor (systemd) Tutorial em vídeo

Veja a seguir como o painel de controle CWP habilita o monitoramento de serviço ServicesMonitor (systemd) neste artigoYouTubeTutorial em vídeo▼