Kumaha ngaktifkeun monitoring jasa dina CWP Control Panel ServicesMonitor (systemd)

在LinuxDina server, tetep jasa ngajalankeun stably, pikeun websiteSEOPenting pisan.

Panel Kontrol CWPBakal ngabantosan anjeun ngalangkungan alat ngawaskeun jasa.

Kumaha cara ngaktipkeun ServicesMonitor (systemd) dina panel kontrol CWP?

Pikeun ngaktifkeun monitoring jasa dina CWP:

1. nyambung ka anjeunCWP安装
2. manggihServices Config->ServicesMonitor( systemd )选项
3. Pilih/Lebetkeun:
   Ngaktifkeun nganonaktifkeun- Ieu bakal ngaktifkeun / nganonaktipkeun monitoring jasa.
   Email béwaraKirim ka - Asupkeun alamat surélék dimana anjeun bakal nampa bewara.
   Pariksa unggal- interval waktu antara cék
4. Pilih jasa anu anjeun hoyong monitor, contona: mariadb.service, monit.service
5. klik提交kancing.Anjeun bakal ningali pesen konfirmasi:

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

Catetan:

• 如果status sistemdjasa nyaétaUnknown,Pangimeutan moal tiasa dianggo pikeun jasa.
• Ladenan anu dipilih pikeun diawaskeun bakal disimpen dina file /usr/local/etc/services-monitor-systemddi.
• Ngawaskeun padamelan cron tiasa dipendakan dina file/etc/cron.d/svcMonitor-systemdsedengjadina.

Anjeun oge bisa luluschkconfigParéntah pikeun nambihan / mupus jasa sacara manual:

chkconfig service_name on
chkconfig service_name off

Salaku conto, nalika sadaya jasa anu sayogi diaktipkeun, kami bakal ningalikeun pesen cron sapertos:

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

Di handap ieu kumaha panel kontrol CWP dina tulisan ieu ngamungkinkeun jasa monitoring ServicesMonitor (systemd)YouTubePidéo Tutorial▼