KWLinuxKuseva, gcina isevisi isebenza ngokuzinzile, kuwebhusayithiSEOBaluleke kakhulu.
Iphaneli yokulawula ye-CWPIzokusiza ngamathuluzi okuqapha isevisi.
Uyenza kanjani i-ServiceMonitor (systemd) isebenze kuphaneli yokulawula ye-CWP?
Ukuze unike amandla ukuqapha kwesevisi ku-CWP:
- xhuma kweyakhoCWPukufakwa
- TholaI-Service Config->ServicesMonitor( i-systemd )选项
- Khetha/Faka:
Nika amandla / Khubaza- Lokhu kuzokwenza/kukhubaze ukuqapha kwesevisi.
Email izazisoThumela ku- Faka ikheli le-imeyili lapho uzothola khona izaziso.
Hlola zonke- isikhathi sokuphumula phakathi kwamasheke - Khetha isevisi ofuna ukuyigada, isibonelo: mariadb.service, monit.service
- chofoza提交inkinobho.Uzobona umlayezo wokuqinisekisa:
Service Monitoring is not enabled Enabling monitoring in cron MAILTO=cwp1@ chenweilaing.com */15 * * * * root /usr/local/bin/svcMonitor-systemd Monitoring Enabled: Yes
Qaphela:
- 如果isimo se-systemdisevisi
Unknown
,Ukuqapha ngeke kusebenzele izinsizakalo. - Amasevisi akhethiwe ozogadwa azolondolozwa kufayela
/usr/local/etc/services-monitor-systemd
phakathi. - Ukuqapha imisebenzi ye-cron ingatholakala kufayela
/etc/cron.d/svcMonitor-systemd
Phakathikhuphula.
Ungaphasa futhialikhokhiYala ukuze wengeze/ususe mathupha amasevisi:
chkconfig service_name on
chkconfig service_name off
Isibonelo, uma zonke izinsiza ezitholakalayo zinikwe amandla, sizobonisa imilayezo ye-cron efana nale:
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
Iphaneli Yokulawula ye-CWP Nika amandla i-ServiceMonitor (systemd) Isifundo Sevidiyo
Okulandelayo indlela iphaneli yokulawula ye-CWP inika amandla ukuqapha kwesevisi i-ServiceMonitor (systemd) kulesi sihlokoYouTubeOkokufundisa kwevidiyo▼
I-Hope Chen Weiliang Blog ( https://www.chenweiliang.com/ ) kwabelwane ngokuthi "Uyivumela kanjani i-ServiceMonitor (systemd) kuphaneli yokulawula ye-CWP", okuwusizo kuwe.
Siyakwamukela ukwabelana ngesixhumanisi salesi sihloko:https://www.chenweiliang.com/cwl-1414.html
Uyemukelwa esiteshini seTelegram sebhulogi ka-Chen Weiliang ukuze uthole izibuyekezo zakamuva!
📚 Lo mhlahlandlela uqukethe inani elikhulu, 🌟Leli ithuba eliyivelakancane, ungaphuthelwa! ⏰⌛💨
Yabelana futhi uthanda uma uthanda!
Ukwabelana kwakho nokuthanda kwakho kuyisisusa sethu esiqhubekayo!