Bagaimana untuk membolehkan pemantauan perkhidmatan dalam CWP Control Panel ServicesMonitor (systemd)

在LinuxPada pelayan, pastikan perkhidmatan berjalan dengan stabil, untuk tapak webSEOSangat penting.

Panel Kawalan CWPAkan membantu anda melalui alat pemantauan perkhidmatan.

Bagaimana untuk mendayakan ServicesMonitor (systemd) dalam panel kawalan CWP?

Untuk mendayakan pemantauan perkhidmatan dalam CWP:

1. sambung ke andaCWPPasang
2. CariKonfigurasi Perkhidmatan->ServicesMonitor( sistem )Pilihan
3. Pilih/Masukkan:
   Membolehkan melumpuhkan- Ini akan membolehkan / melumpuhkan pemantauan perkhidmatan.
   Email pemberitahuanHantar ke - Masukkan alamat e-mel di mana anda akan menerima pemberitahuan.
   Semak setiap- selang masa antara pemeriksaan
4. Pilih perkhidmatan yang anda ingin pantau, contohnya: mariadb.service, monit.service
5. klik提交butang.Anda akan melihat mesej pengesahan:

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

Nota:

• 如果status sistemdperkhidmatan adalahUnknown,Pemantauan tidak akan berfungsi untuk perkhidmatan.
• Perkhidmatan yang dipilih untuk dipantau akan disimpan dalam fail /usr/local/etc/services-monitor-systemddalam.
• Memantau kerja cron boleh didapati dalam fail/etc/cron.d/svcMonitor-systemd中hadir.

Anda juga boleh luluschkconfigPerintah untuk menambah/mengalih keluar perkhidmatan secara manual:

chkconfig service_name on
chkconfig service_name off

Sebagai contoh, apabila semua perkhidmatan yang tersedia didayakan, kami akan memaparkan mesej 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

Tutorial Video Panel Kawalan CWP Dayakan ServicesMonitor (systemd).

Berikut ialah cara panel kawalan CWP dalam artikel ini membolehkan pemantauan perkhidmatan ServicesMonitor (systemd)YoutubeTutorial Video▼