Nola gaitu zerbitzuen monitorizazioa CWP Kontrol Paneleko ServicesMonitor-en (systemd)

在LinuxZerbitzarian, mantendu zerbitzua egonkor exekutatzen, webgunerakoSEOOso garrantzitsua.

CWP Kontrol PanelaZerbitzua kontrolatzeko tresnen bidez lagunduko dizu.

Nola gaitu ServicesMonitor (systemd) CWP kontrol panelean?

CWPn zerbitzuaren monitorizazioa gaitzeko:

1. konektatu zureCWP安装
2. aurkituZerbitzuen konfigurazioa->ServicesMonitor( systemd )选项
3. Hautatu/Sartu:
   Gaitu / Desgaitu- Honek zerbitzuaren jarraipena gaitu/desgaituko du.
   Email jakinarazpenakNori bidali - Sartu jakinarazpenak jasoko dituzun helbide elektronikoa.
   Egiaztatu bakoitzean- Kontrolen arteko denbora tartea
4. Hautatu kontrolatu nahi duzun zerbitzua, adibidez: mariadb.service, monit.service
5. egin klik提交botoia.Berrespen-mezu bat ikusiko duzu:

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

Kontuz:

• kasuansistemaren egoerazerbitzua daUnknown,Monitorizazioak ez du funtzionatuko zerbitzuetan.
• Kontrolatzeko hautatutako zerbitzuak fitxategian gordeko dira /usr/local/etc/services-monitor-systemdurtean.
• Cron lanak monitorizatzeko fitxategian aurki daiteke/etc/cron.d/svcMonitor-systemd中agertu.

Pasa zaitezke erechkconfigZerbitzuak eskuz gehitzeko/kentzeko komandoa:

chkconfig service_name on
chkconfig service_name off

Adibidez, erabilgarri dauden zerbitzu guztiak gaituta daudenean, cron mezuak bistaratuko ditugu, hala nola:

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 Kontrol Panela Gaitu ServicesMonitor (systemd) Bideo Tutoriala

Hona hemen artikulu honetako CWP kontrol panelak zerbitzuen monitorizazioa nola gaitzen duen ServicesMonitor (systemd)YouTubeBideo-tutoriala▼