Hvernig á að virkja þjónustuvöktun í CWP Control Panel ServicesMonitor (systemd)

ÍLinuxÁ þjóninum skaltu halda þjónustunni stöðugri í gangi fyrir vefsíðunaSEOMjög mikilvægt.

CWP stjórnborðMun hjálpa þér í gegnum þjónustuvöktunartæki.

Hvernig á að virkja ServicesMonitor (systemd) í CWP stjórnborði?

Til að virkja þjónustuvöktun í CWP:

1. tengjast þínumCWPuppsetningu
2. horfðu uppÞjónusta Config->ServicesMonitor( systemd )Valkostur
3. Veldu/sláðu inn:
   Virkja afvirkja- Þetta mun virkja/slökkva á þjónustuvöktun.
   Email tilkynningarSenda til - Sláðu inn netfangið þar sem þú munt fá tilkynningar.
   Athugaðu hvert- tímabil á milli athugana
4. Veldu þjónustuna sem þú vilt fylgjast með, til dæmis: mariadb.service, monit.service
5. smellur提交takki.Þú munt sjá staðfestingarskilaboð:

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

Athugasemd:

• í málikerfisstaðaþjónusta erUnknown,Vöktun mun ekki virka fyrir þjónustu.
• Valdar þjónustur til að fylgjast með verða vistaðar í skrá /usr/local/etc/services-monitor-systemdí.
• Vöktun cron störf er að finna í skránni/etc/cron.d/svcMonitor-systemd中mæta.

Þú getur líka farið framhjáchkconfigSkipun til að bæta við/fjarlægja þjónustu handvirkt:

chkconfig service_name on
chkconfig service_name off

Til dæmis, þegar öll tiltæk þjónusta er virkjuð, munum við birta cron skilaboð eins og:

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 Virkja ServicesMonitor (systemd) myndbandsleiðbeiningar

Eftirfarandi er hvernig CWP stjórnborðið í þessari grein gerir þjónustuvöktun kleift ServicesMonitor (systemd)YoutubeKennslumyndband▼