Yadda ake kunna saka idanu na sabis a cikin CWP Control Panel ServicesMonitor (systemd)

ALinuxA kan uwar garken, kiyaye sabis ɗin yana gudana a tsaye, don gidan yanar gizonSEOMuhimmanci sosai.

Cibiyar Kula da CWPZai taimake ku ta kayan aikin sa ido na sabis.

Yadda ake kunna ServicesMonitor (systemd) a cikin kwamitin kula da CWP?

Don kunna saka idanu na sabis a cikin CWP:

1. haɗi zuwa nakuCWPƘare
2. samuConfig Services->ServicesMonitor( tsarin tsarin )Yi amfani da kyau
3. Zaɓi/Shiga:
   Yarda / Kashe- Wannan zai taimaka/kashe kulawar sabis.
   Email sanarwarAika zuwa - Shigar da adireshin imel inda za ku karɓi sanarwa.
   Duba kowane- tazarar lokaci tsakanin cak
4. Zaɓi sabis ɗin da kuke son saka idanu, misali: mariadb.service, monit.service
5. danna提交maballin.Za ku ga saƙon tabbatarwa:

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

Lura:

• 如果tsarin halisabis neUnknown,Sa ido ba zai yi aiki don ayyuka ba.
• Za a adana ayyukan da aka zaɓa don saka idanu a cikin fayil /usr/local/etc/services-monitor-systemdMatsakaici.
• Ana iya samun ayyukan cron na saka idanu a cikin fayil ɗin/etc/cron.d/svcMonitor-systemdMatsakaicijuya sama.

Hakanan zaka iya wucewasyedaUmarni don ƙara/cire ayyuka da hannu:

chkconfig service_name on
chkconfig service_name off

Misali, lokacin da aka kunna duk ayyukan da ake da su, za mu nuna saƙonnin cron kamar:

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 Control Panel Kunna AyyukaMonitor (systemd) Koyarwar Bidiyo

Mai zuwa shine yadda kwamitin kula da CWP ke ba da damar sa ido kan sabis ServicesMonitor (systemd) a cikin wannan labarinYouTubeKoyarwar Bidiyo ▼