Uyenza njani iliso yenkonzo kwiPaneli yoLawulo yeCWP yeeNkonzoMonitor (systemd)

InLinuxKwiseva, gcina inkonzo isebenza ngokuzinzileyo, kwiwebhusayithiseoIbaluleke kakhulu.

Iphaneli yokulawula yeCWPKuya kukunceda ngokusebenzisa izixhobo esweni inkonzo.

Uyenza njani iServiceMonitor (systemd) kwiphaneli yolawulo yeCWP?

Ukwenza uhlolo lwenkonzo lusebenze kwi-CWP:

1. qhagamshela kweyakhoI-CWPufakelo
2. fumanaUqwalaselo lweeNkonzo->IiNkonzoMonitor(I inkqubo ) U选项
3. Khetha/Ngena:
   Yenziwe yasebenza ayasebenza- Oku kuya kwenza/kucime ukujongwa kwenkonzo.
   Email izazisoThumela ku-Faka idilesi ye-imeyile apho uya kufumana khona izaziso.
   Jonga yonke into-Isithuba sexesha phakathi kweetshekhi
4. Khetha inkonzo ofuna ukuyijonga, umzekelo: mariadb.service, monit.service
5. cofa提交iqhosha.Uya kubona umyalezo 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:

• mhlawumbiubume benkquboinkonzo yiUnknown,Ukubeka iliso akuyi kusebenza kwiinkonzo.
• Iinkonzo ezikhethiweyo zokubeka iliso ziya kugcinwa kwifayile /usr/local/etc/services-monitor-systemdphakathi.
• Ukubeka iliso kwe-cron imisebenzi inokufumaneka kwifayile/etc/cron.d/svcMonitor-systemdPhakathi。

Unako kwakhona ukupasachkconfigUmyalelo wokongeza/ukususa iinkonzo ngesandla:

chkconfig service_name on
chkconfig service_name off

Umzekelo, xa zonke iinkonzo ezikhoyo zivuliwe, siya kubonisa imiyalezo yecron 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 yoLawulo ye-CWP yenza i-ServiceMonitor (i-systemd) i-Video Tutorial isebenze

Oku kulandelayo yindlela iphaneli yolawulo ye-CWP eyenza ngayo ukujongwa kwenkonzo i-ServiceMonitor (systemd) kweli nqakuYouTubeIsifundo seVidiyo▼