Kuidas lubada teenuse jälgimist CWP juhtpaneeli ServicesMonitoris (systemd)

在LinuxHoidke teenus serveris veebisaidi jaoks stabiilselt töötamasSEOVäga tähtis.

CWP juhtpaneelAitab teid teenuse jälgimise tööriistade kaudu.

Kuidas lubada ServicesMonitor (systemd) CWP juhtpaneelil?

Teenuse jälgimise lubamiseks CWP-s:

1. ühendada omagaCWP安装
2. leidaServices Config-> ServicesMonitor( systemd )选项
3. Vali/sisesta:
   Lubamine / keelamine- See lubab/keelab teenuse jälgimise.
   Email teatedSaada – sisestage e-posti aadress, kuhu teateid saate.
   Kontrollige iga- kontrollide vaheline ajavahemik
4. Valige teenus, mida soovite jälgida, näiteks: mariadb.service, monit.service
5. klõpsa提交nuppu.Näete kinnitusteadet:

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

注意 事项:

• 如果süsteemne olekteenus onUnknown,Järelevalve teenuste puhul ei tööta.
• Valitud teenused, mida jälgida, salvestatakse faili /usr/local/etc/services-monitor-systemdaastal.
• Croni tööde jälgimise leiate failist/etc/cron.d/svcMonitor-systemd中ilmuma.

Saab ka läbidachkconfigKäsk teenuste käsitsi lisamiseks/eemaldamiseks:

chkconfig service_name on
chkconfig service_name off

Näiteks kui kõik saadaolevad teenused on lubatud, kuvame cron-teateid, näiteks:

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 juhtpaneel Luba ServicesMonitor (süsteemne) videoõpetus

Järgnevalt kirjeldatakse, kuidas selles artiklis olev CWP juhtpaneel võimaldab teenuse jälgimist ServicesMonitor (systemd)YoutubeVideoõpetus▼