AnnLinuxAir an fhrithealaiche, cùm an t-seirbheis a 'ruith gu seasmhach, airson an làrach-lìnSEOGlè chudromach.
Pannal Smachd CWPCuidichidh e thu tro innealan sgrùdaidh seirbheis.
Mar a bheir thu comas do ServicesMonitor (systemd) ann am pannal smachd CWP?
Gus sgrùdadh seirbheis a chomasachadh ann an CWP:
- ceangail ri do chuidCWP安装
- 查找Config seirbheisean-> ServicesMonitor( siostam )Roghainnean
- Tagh/Cuir a-steach:
Cumasaich / Cuir an comas casg air- Bheir seo comas / cuir à comas sgrùdadh seirbheis.
Email brathanCuir gu - Cuir a-steach an seòladh puist-d far am faigh thu fiosan.
Feuch gach- ùine eadar sgrùdaidhean - Tagh an t-seirbheis a tha thu airson sùil a chumail, mar eisimpleir: mariadb.service, monit.service
- cliog提交putan.Chì thu teachdaireachd dearbhaidh:
Service Monitoring is not enabled Enabling monitoring in cron MAILTO=cwp1@ chenweilaing.com */15 * * * * root /usr/local/bin/svcMonitor-systemd Monitoring Enabled: Yes
Nota:
- Gun fhiosstaid siostamtha seirbheis
Unknown
,Chan obraich sgrùdadh airson seirbheisean. - Thèid seirbheisean taghte airson sùil a chumail air an sàbhaladh ann am faidhle
/usr/local/etc/services-monitor-systemd
a-steach. - Gheibhear sùil air obraichean cron anns an fhaidhle
/etc/cron.d/svcMonitor-systemd
MeadhanachTionndaidh suas.
Faodaidh tu cuideachd a dhol seachadchkconfigÒrdugh gus seirbheisean a chur ris / a thoirt air falbh le làimh:
chkconfig service_name on
chkconfig service_name off
Mar eisimpleir, nuair a bhios a h-uile seirbheis a tha ri fhaighinn air a chomasachadh, seallaidh sinn teachdaireachdan cron mar:
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
Pannal Smachd CWP Dèan comas air ServicesMonitor (systemd) Oideachadh Bhidio
Tha na leanas mar a tha pannal smachd CWP a’ comasachadh sgrùdadh seirbheis ServicesMonitor (systemd) san artaigil seoYouTubeOideachadh Bhidio ▼
An dòchas blog Chen Weiliang ( https://www.chenweiliang.com/ ) co-roinnte "Mar a nì thu comas air ServicesMonitor (systemd) ann am Pannal Smachd CWP", a tha cuideachail dhut.
Fàilte gus ceangal an artaigil seo a cho-roinn:https://www.chenweiliang.com/cwl-1414.html
Fàilte don t-sianal Telegram de bhlog Chen Weiliang gus na h-ùrachaidhean as ùire fhaighinn!
📚 Tha luach mòr anns an stiùireadh seo, 🌟 Is e cothrom ainneamh a tha seo, na caill e! ⏰⌛💨
Roinn agus toil ma thogras tu!
Is e do roinneadh agus do rudan mar ar brosnachadh leantainneach!