ວິທີການເປີດໃຊ້ການກວດສອບການບໍລິການໃນ CWP Control Panel ServicesMonitor (systemd)

在Linuxຢູ່ໃນເຄື່ອງແມ່ຂ່າຍ, ຮັກສາການບໍລິການທີ່ເຮັດວຽກຢ່າງຫມັ້ນຄົງ, ສໍາລັບເວັບໄຊທ໌SEOສໍາ​ຄັນ​ຫຼາຍ.

ແຜງຄວບຄຸມ CWPຈະຊ່ວຍໃຫ້ທ່ານຜ່ານເຄື່ອງມືຕິດຕາມກວດກາການບໍລິການ.

ວິທີການເປີດໃຊ້ ServicesMonitor (systemd) ໃນແຜງຄວບຄຸມ CWP?

ເພື່ອເປີດໃຊ້ການກວດສອບການບໍລິການໃນ CWP:

1. ເຊື່ອມຕໍ່ກັບຂອງທ່ານCWPອຸປະກອນເສີມ
2. ຊອກຫາServices Config->ServicesMonitor( systemd )ຕົວເລືອກ
3. ເລືອກ/ປ້ອນ:
   ເປີດ / ປິດການໃຊ້ງານ- ນີ້​ຈະ​ເຮັດ​ໃຫ້​ສາ​ມາດ / ປິດ​ການ​ຕິດ​ຕາມ​ການ​ບໍ​ລິ​ການ​ຕິດ​ຕາມ​ກວດ​ກາ​.
   Email ການແຈ້ງເຕືອນສົ່ງຫາ - ໃສ່ທີ່ຢູ່ອີເມວທີ່ເຈົ້າຈະໄດ້ຮັບການແຈ້ງເຕືອນ.
   ກວດເບິ່ງທຸກໆ- ໄລ​ຍະ​ເວ​ລາ​ລະ​ຫວ່າງ​ການ​ກວດ​ສອບ​
4. ເລືອກບໍລິການທີ່ທ່ານຕ້ອງການຕິດຕາມ, ຕົວຢ່າງ: mariadb.service, monit.service
5. ຄລິກຍື່ນສະ ເໜີປຸ່ມ.ທ່ານຈະເຫັນຂໍ້ຄວາມຢືນຢັນ:

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

ໝາຍ ເຫດ:

• ໃນ​ກໍ​ລະ​ນີສະຖານະລະບົບການບໍລິການແມ່ນUnknown,ການຕິດຕາມຈະບໍ່ເຮັດວຽກສໍາລັບການບໍລິການ.
• ບໍລິການທີ່ເລືອກເພື່ອຕິດຕາມຈະຖືກບັນທຶກໄວ້ໃນໄຟລ໌ /usr/local/etc/services-monitor-systemdໃນ.
• ການຕິດຕາມວຽກ cron ສາມາດພົບເຫັນຢູ່ໃນໄຟລ໌/etc/cron.d/svcMonitor-systemdປານກາງຫັນຂຶ້ນ.

ນອກນັ້ນທ່ານຍັງສາມາດຜ່ານchkconfigຄໍາສັ່ງທີ່ຈະເພີ່ມ / ເອົາການບໍລິການດ້ວຍຕົນເອງ:

chkconfig service_name on
chkconfig service_name off

ຕົວຢ່າງ, ເມື່ອການບໍລິການທີ່ມີຢູ່ທັງໝົດຖືກເປີດໃຊ້, ພວກເຮົາຈະສະແດງຂໍ້ຄວາມ cron ເຊັ່ນ:

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 ເປີດໃຊ້ ServicesMonitor (systemd) ການສອນວິດີໂອ

ຕໍ່​ໄປ​ນີ້​ແມ່ນ​ວິ​ທີ​ການ​ຄະ​ນະ​ກໍາ​ມະ​ການ​ຄວບ​ຄຸມ CWP ໃນ​ບົດ​ຄວາມ​ນີ້​ເຮັດ​ໃຫ້​ການ​ຕິດ​ຕາມ​ການ​ບໍ​ລິ​ການ ServicesMonitor (systemd​)YouTubeວິດີໂອສອນສອນ ▼