CWP ڪنٽرول پينل سروسز مانيٽر (سسٽم ڊي) ۾ سروس مانيٽرنگ کي ڪيئن فعال ڪجي

ع ۾لينڪسسرور تي، ويب سائيٽ لاءِ، خدمت کي مستحڪم طور تي جاري رکوSEOتمام ضروري.

CWP ڪنٽرول پينلخدمت جي نگراني جي اوزار ذريعي توهان جي مدد ڪندو.

CWP ڪنٽرول پينل ۾ ServicesMonitor (systemd) کي ڪيئن فعال ڪجي؟

CWP ۾ خدمت جي نگراني کي فعال ڪرڻ لاء:

1. توهان سان ڳنڍيوCWP安装
2. 查找خدمتن جي جوڙجڪ->Services مانيٽر( سسٽم )选项
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 ڪنٽرول پينل Enable ServicesMonitor (systemd) وڊيو ٽيوٽوريل

هيٺ ڏنل آهي ڪيئن هن آرٽيڪل ۾ CWP ڪنٽرول پينل سروس مانيٽرنگ سروس مانيٽر (سسٽم ڊي) کي فعال ڪري ٿو.يوٽيوبوڊيو سبق ▼