Sut i alluogi monitro gwasanaeth yn CWP Control Panel ServicesMonitor (systemd)

在LinuxAr y gweinydd, cadwch y gwasanaeth yn rhedeg yn sefydlog, ar gyfer y wefanSEOPwysig iawn.

Panel Rheoli CWPBydd yn eich helpu trwy offer monitro gwasanaeth.

Sut i alluogi ServicesMonitor (systemd) ym mhanel rheoli CWP?

Er mwyn galluogi monitro gwasanaeth yn CWP:

1. cysylltu â'chCWPgosod
2. dod o hydFfurfweddu Gwasanaethau->Monitor Gwasanaethau( systemd )Dewislen
3. Dewiswch/Rhowch:
   Galluogi Analluogi- Bydd hyn yn galluogi/analluogi monitro gwasanaeth.
   Email hysbysiadauAnfon at - Rhowch y cyfeiriad e-bost lle byddwch yn derbyn hysbysiadau.
   Gwiriwch bob- y cyfnod amser rhwng gwiriadau
4. Dewiswch y gwasanaeth rydych chi am ei fonitro, er enghraifft: mariadb.service, monit.service
5. cliciwchCyflwynobotwm.Byddwch yn gweld neges cadarnhau:

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

Nodyn:

• 如果statws systemdgwasanaeth ynUnknown,Ni fydd monitro yn gweithio i wasanaethau.
• Bydd gwasanaethau dethol i'w monitro yn cael eu cadw yn y ffeil /usr/local/etc/services-monitor-systemdyn.
• Gellir dod o hyd i swyddi monitro cron yn y ffeil/etc/cron.d/svcMonitor-systemdCanoligtroi i fyny.

Gallwch chi hefyd basiochkconfigGorchymyn i ychwanegu/dileu gwasanaethau â llaw:

chkconfig service_name on
chkconfig service_name off

Er enghraifft, pan fydd yr holl wasanaethau sydd ar gael wedi'u galluogi, byddwn yn dangos negeseuon cron fel:

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

Panel Rheoli CWP Galluogi ServicesMonitor (systemd) Tiwtorial Fideo

Dyma sut mae panel rheoli CWP yn galluogi monitro gwasanaeth ServicesMonitor (systemd) yn yr erthygl honYouTubeTiwtorial Fideo ▼