Cumu attivà u monitoraghju di serviziu in CWP Control Panel ServicesMonitor (systemd)

inLinuxNantu à u servitore, mantene u serviziu in esecuzione stabile, per u situ webSEOAssai impurtante.

Pannellu di cuntrollu CWPVi aiuterà à traversu strumenti di surviglianza di serviziu.

Cumu attivà ServicesMonitor (systemd) in u pannellu di cuntrollu CWP?

Per attivà u monitoraghju di serviziu in CWP:

1. cunnette à u vostruCWPinstallazione
2. truvàServices Config->ServicesMonitor( systemd )选项
3. Selezziunà / Entra:
   Abilita / Disattiva- Questu permetterà / disattivà u monitoraghju di u serviziu.
   Email notificheMandate à - Inserite l'indirizzu email induve riceverete notificazioni.
   Verificate ogni- intervallu di tempu trà i cuntrolli
4. Selezziunà u serviziu chì vulete monitorà, per esempiu: mariadb.service, monit.service
5. cliccate提交buttone.Vi vede un missaghju di cunferma:

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

Nota:

• in casustatus di sistemaserviziu hèUnknown,U monitoraghju ùn funziona micca per i servizii.
• I servizii selezziunati per monitorà seranu salvati in u schedariu /usr/local/etc/services-monitor-systemdin.
• Monitoring cron jobs pò esse trovu in u schedariu/etc/cron.d/svcMonitor-systemdMediumalzà.

Pudete ancu passàchkconfigCumanda per aghjunghje / caccià i servizii manualmente:

chkconfig service_name on
chkconfig service_name off

Per esempiu, quandu tutti i servizii dispunibuli sò attivati, avemu da vede i missaghji cron cum'è:

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 Enable ServicesMonitor (systemd) Video Tutorial

Eccu cumu u pannellu di cuntrollu CWP in questu articulu permette u monitoraghju di u serviziu ServicesMonitor (systemd)YouTubeTutorial Video▼