CWP Control Panel ServicesMonitor (tizim) da xizmat monitoringini qanday yoqish mumkin

在LinuxServerda veb-sayt uchun xizmatni barqaror ishlashini ta'minlangSEOJuda muhim.

CWP boshqaruv paneliXizmat monitoringi vositalari orqali sizga yordam beradi.

CWP boshqaruv panelida ServicesMonitor (tizim)ni qanday yoqish mumkin?

CWP da xizmat monitoringini yoqish uchun:

1. ga ulaningCWP® è £ £…
2. 查找Services Config->ServicesMonitor( tizimd )Tanlash
3. Tanlash/Kirish:
   Yoqish / o'chirish- Bu xizmat monitoringini yoqadi/o'chiradi.
   Email bildirishnomalarYuborish - bildirishnomalar oladigan elektron pochta manzilini kiriting.
   Har bir tekshiring- tekshirishlar orasidagi vaqt oralig'i
4. Kuzatmoqchi bo'lgan xizmatni tanlang, masalan: mariadb.service, monit.service
5. bosing提交tugmasi.Siz tasdiqlash xabarini ko'rasiz:

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

Izoh:

• bu holatdatizim holatixizmat hisoblanadiUnknown,Xizmatlar uchun monitoring ishlamaydi.
• Monitoring uchun tanlangan xizmatlar faylda saqlanadi /usr/local/etc/services-monitor-systemdyilda.
• Cron ishlarini kuzatish faylda mavjud/etc/cron.d/svcMonitor-systemdO'rtachako'rinib qolish; .. ga aylanib qolish.

Siz ham o'tishingiz mumkinchkconfigXizmatlarni qo'lda qo'shish/o'chirish buyrug'i:

chkconfig service_name on
chkconfig service_name off

Masalan, barcha mavjud xizmatlar yoqilganda, biz cron xabarlarini ko'rsatamiz, masalan:

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 Boshqaruv paneli Xizmatlar Monitorini yoqish (tizim) Video darsligi

Quyida ushbu maqoladagi CWP boshqaruv paneli qanday qilib ServicesMonitor (tizim) xizmatini kuzatish imkonini beradi.YouTubeVideo darslik▼