Kako omogućiti praćenje usluga u CWP Control Panel ServicesMonitor (systemd)

在LinuxNa serveru održavajte stabilno funkcioniranje usluge za web stranicuSEOVeoma važno.

CWP Control PanelPomoći će vam kroz alate za praćenje usluga.

Kako omogućiti ServicesMonitor (systemd) u CWP kontrolnoj tabli?

Da biste omogućili praćenje usluge u CWP:

1. povežite se sa svojimCWP安装
2. nađiServices Config->ServicesMonitor( systemd )选项
3. Odaberite/unesite:
   Omogući onemogući- Ovo će omogućiti/onemogućiti praćenje usluge.
   Email obavještenjaPošalji na - Unesite adresu e-pošte na koju ćete primati obavještenja.
   Provjerite svaki- vremenski interval između provjera
4. Odaberite uslugu koju želite pratiti, na primjer: mariadb.service, monit.service
5. kliknite提交dugme.Vidjet ćete poruku potvrde:

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

Napomena:

• 如果systemd statususluga jeUnknown,Monitoring neće raditi za usluge.
• Odabrani servisi za praćenje biće sačuvani u fajlu /usr/local/etc/services-monitor-systemdu.
• Nadgledanje cron poslova se može naći u datoteci/etc/cron.d/svcMonitor-systemdsrednjiokreni se.

Možete i proćichkconfigNaredba za ručno dodavanje/uklanjanje usluga:

chkconfig service_name on
chkconfig service_name off

Na primjer, kada su svi dostupni servisi omogućeni, prikazat ćemo cron poruke kao što su:

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 Omogućite ServicesMonitor (systemd) Video Tutorial

Evo kako CWP kontrolna tabla u ovom članku omogućava praćenje servisa ServicesMonitor (systemd)YouTubeVideo Tutorial▼