Cara ngaktifake pemantauan layanan ing CWP Control Panel ServicesMonitor (systemd)

在LinuxIng server, tetep layanan mlaku kanthi stabil, kanggo situs webSEOPenting banget.

Panel Kontrol CWPBakal mbantu sampeyan liwat alat ngawasi layanan.

Kepiye cara ngaktifake ServicesMonitor (systemd) ing panel kontrol CWP?

Kanggo ngaktifake pemantauan layanan ing CWP:

1. nyambung menyang PanjenenganCWP安装
2. 查找Konfigurasi Layanan->ServicesMonitor( sistem )選项
3. Pilih/Ketik:
   Murup mati- Iki bakal ngaktifake / mateni ngawasi layanan.
   Email kabarKirim menyang - Ketik alamat email ing ngendi sampeyan bakal nampa kabar.
   Priksa saben- interval wektu antarane mriksa
4. Pilih layanan sing pengin dipantau, contone: mariadb.service, monit.service
5. klik提交tombol.Sampeyan bakal weruh 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

Cathetan:

• 如果status sistemlayanan punikaUnknown,Ngawasi ora bakal bisa kanggo layanan.
• Layanan sing dipilih kanggo ngawasi bakal disimpen ing file /usr/local/etc/services-monitor-systemding
• Ngawasi cron jobs bisa ditemokake ing file/etc/cron.d/svcMonitor-systemdSedhengmunggah.

Sampeyan uga bisa luluschkconfigPrintah kanggo nambah / mbusak layanan kanthi manual:

chkconfig service_name on
chkconfig service_name off

Contone, nalika kabeh layanan sing kasedhiya diaktifake, kita bakal nampilake pesen cron kayata:

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

Ing ngisor iki carane panel kontrol CWP ing artikel iki mbisakake layanan monitoring ServicesMonitor (systemd)YouTubeTutorial Video▼