Cara mengaktifkan pemantauan layanan di CWP Control Panel ServicesMonitor (systemd)

在LinuxDi server, jaga agar layanan tetap berjalan dengan stabil, untuk situs webSEOSangat penting.

Panel Kontrol CWPAkan membantu Anda melalui alat pemantauan layanan.

Bagaimana cara mengaktifkan ServicesMonitor (systemd) di panel kontrol CWP?

Untuk mengaktifkan pemantauan layanan di CWP:

1. terhubung ke AndaCWP安装
2. TemukanKonfigurasi Layanan->Monitor Layanan( systemd )选项
3. Pilih/Masukkan:
   Aktifkan / Nonaktifkan- Ini akan mengaktifkan/menonaktifkan pemantauan layanan.
   Email pemberitahuanKirim ke - Masukkan alamat email tempat Anda akan menerima pemberitahuan.
   Periksa setiap- interval waktu antara pemeriksaan
4. Pilih layanan yang ingin Anda pantau, misalnya: mariadb.service, monit.service
5. Klik提交tombol.Anda akan melihat pesan konfirmasi:

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

Catatan:

• dalam halstatus sistemlayanan adalahUnknown,Pemantauan tidak akan berfungsi untuk layanan.
• Layanan yang dipilih untuk dipantau akan disimpan dalam file /usr/local/etc/services-monitor-systemdSedang.
• Memantau pekerjaan cron dapat ditemukan di file/etc/cron.d/svcMonitor-systemd中找到.

Anda juga bisa luluschkconfig.dllPerintah untuk menambah/menghapus layanan secara manual:

chkconfig service_name on
chkconfig service_name off

Misalnya, ketika semua layanan yang tersedia diaktifkan, kami akan menampilkan pesan cron seperti:

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

Panel Kontrol CWP Aktifkan Tutorial Video ServicesMonitor (systemd)

Berikut adalah cara panel kontrol CWP dalam artikel ini mengaktifkan pemantauan layanan ServicesMonitor (systemd)YoutubeVideo Tutorial▼