Чӣ тавр фаъол кардани мониторинги хидмат дар CWP Panel Control ServicesMonitor (система)

在LinuxДар сервер, хидматро барои вебсайт устувор нигоҳ доредSEOХеле муҳим.

Панели идоракунии CWPБа шумо тавассути абзорҳои мониторинги хидмат кӯмак хоҳад кард.

Чӣ тавр ServicesMonitor (система) -ро дар панели идоракунии CWP фаъол кардан мумкин аст?

Барои фаъол кардани мониторинги хидмат дар CWP:

1. ба шумо пайваст шаведCWPнасб
2. 查找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 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 даргиронидани Хадамоти Монитор (система) дарси видео

Дар зер чӣ гуна панели идоракунии CWP дар ин мақола мониторинги хидматрасонии ServicesMonitor (система) -ро имкон медиҳадYouTubeДарси видеоӣ▼