د CWP Control Panel ServicesMonitor (systemd) کې د خدماتو څارنه څنګه فعال کړئ

پهلینوکسپه سرور کې، د ویب پاڼې لپاره خدمت په ثابت ډول روان وساتئSEOډیر مهم.

د CWP کنټرول پینلد خدماتو څارنې وسیلو له لارې به تاسو سره مرسته وکړي.

په CWP کنټرول پینل کې د ServicesMonitor (systemd) فعالولو څرنګوالی؟

په CWP کې د خدماتو نظارت فعالولو لپاره:

1. ستاسو سره وصل کړئCWPلګول
2. موندلد خدماتو تنظیم -> د خدماتو مانیټر( سیسټم D )选项
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په
• د څارنې کرون دندې په فایل کې موندل کیدی شي/etc/cron.d/svcMonitor-systemdمنځنینشه کیدل، ښکاره کیدل.

تاسو هم پاس کولی شئchkconfigپه لاسي ډول د خدماتو اضافه / لرې کولو امر:

chkconfig service_name on
chkconfig service_name off

د مثال په توګه، کله چې ټول موجود خدمتونه فعال شي، موږ به د کرون پیغامونه ښکاره کړو لکه:

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 کنټرول پینل د خدماتو مانیټر (سیسټمd) ویډیو ټیوټوریل فعال کړئ

لاندې دا دی چې څنګه پدې مقاله کې د CWP کنټرول پینل د خدماتو څارنې خدماتو مانیټر (سیسټمd) فعالويYouTubeویډیو ټیوټوریل▼