Giunsa paghimo ang pag-monitor sa serbisyo sa CWP Control Panel ServicesMonitor (systemd)

在LinuxSa server, ipadayon nga lig-on ang serbisyo, para sa websiteSEOImportante kaayo.

CWP Control PanelMakatabang kanimo pinaagi sa mga himan sa pagmonitor sa serbisyo.

Giunsa paghimo ang ServicesMonitor (systemd) sa control panel sa CWP?

Aron mahimo ang pagmonitor sa serbisyo sa CWP:

1. sumpay sa imongAng CWPPag-instalar
2. 查找Mga Serbisyo Config->ServicesMonitor( systemd )选项
3. Pagpili/Pagsulod:
   Pag-Enable / Disable- Kini makahimo / dili pag-monitor sa serbisyo.
   Email mga pahibaloIpadala sa - Pagsulod sa email address diin makadawat ka og mga pahibalo.
   Susiha ang matag- agwat sa oras tali sa mga tseke
4. Pilia ang serbisyo nga gusto nimong bantayan, pananglitan: mariadb.service, monit.service
5. pag-klik提交butones.Makita nimo ang mensahe sa pagkumpirma:

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

Hinumdomi:

• 如果kahimtang sa sistemaserbisyo kayUnknown,Ang pagmonitor dili molihok alang sa mga serbisyo.
• Ang pinili nga mga serbisyo nga bantayan ma-save sa file /usr/local/etc/services-monitor-systemdsa.
• Ang pag-monitor sa mga trabaho sa cron makita sa file/etc/cron.d/svcMonitor-systemdMediumpasaka.

Makapasar sab kachkconfigSugo nga mano-mano ang pagdugang/pagtangtang sa mga serbisyo:

chkconfig service_name on
chkconfig service_name off

Pananglitan, kung ang tanan nga magamit nga serbisyo mahimo’g, ipakita namon ang mga mensahe sa cron sama sa:

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 Enable ServicesMonitor (systemd) Video Tutorial

Ang mosunod mao ang paagi nga ang CWP control panel makahimo sa pagmonitor sa serbisyo ServicesMonitor (systemd) niining artikulohaYouTubeTutorial sa Video▼