Comment activer la surveillance des services dans CWP Control Panel ServicesMonitor (systemd)

Dans Linux/UnixSur le serveur, faites en sorte que le service fonctionne de manière stable, pour le site WebSEOTrès important.

Panneau de configuration CWPVous aidera à travers des outils de surveillance de service.

Comment activer ServicesMonitor (systemd) dans le panneau de configuration CWP ?

Pour activer la surveillance des services dans CWP :

1. connectez-vous à votreCWP安装
2. TrouverConfiguration des services-> ServicesMonitor( systemd )Option
3. Sélectionnez/Entrez :
   Activer désactiver- Cela activera/désactivera la surveillance du service.
   Emailes notificationsEnvoyer à - Saisissez l'adresse e-mail à laquelle vous recevrez les notifications.
   Vérifiez chaque- intervalle de temps entre les contrôles
4. Sélectionnez le service que vous souhaitez surveiller, par exemple : mariadb.service, monit.service
5. Cliquer sur提交bouton.Vous verrez un message de confirmation :

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

Note:

• 如果état systèmele service estUnknown,La surveillance ne fonctionnera pas pour les services.
• Les services sélectionnés à surveiller seront enregistrés dans le fichier /usr/local/etc/services-monitor-systemdMoyen.
• La surveillance des tâches cron se trouve dans le fichier/etc/cron.d/svcMonitor-systemd中venez.

Vous pouvez également passerchkconfigCommande pour ajouter/supprimer manuellement des services :

chkconfig service_name on
chkconfig service_name off

Par exemple, lorsque tous les services disponibles sont activés, nous afficherons des messages cron tels que :

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

Tutoriel vidéo sur l'activation de ServicesMonitor (systemd) dans le panneau de configuration CWP

Voici comment le panneau de configuration CWP dans cet article active la surveillance des services ServicesMonitor (systemd) YouTubeTutoriel vidéo▼