Kako omogočiti spremljanje storitev v CWP Control Panel ServicesMonitor (systemd)

在LinuxNa strežniku zagotovite stabilno delovanje storitve za spletno mestoSEOZelo pomembno.

Nadzorna plošča CWPPomagal vam bo z orodji za spremljanje storitev.

Kako omogočiti ServicesMonitor (systemd) na nadzorni plošči CWP?

Če želite omogočiti spremljanje storitev v CWP:

1. povežite se s svojimCWP安装
2. NajtiStoritve Config->ServicesMonitor( sistemd )Možnost
3. Izberite/vnesite:
   Omogoči onemogoči- To bo omogočilo/onemogočilo spremljanje storitev.
   Email obvestilaPošlji - Vnesite e-poštni naslov, na katerega boste prejemali obvestila.
   Preverite vsako- časovni interval med preverjanji
4. Izberite storitev, ki jo želite spremljati, na primer: mariadb.service, monit.service
5. kliknite提交gumb.Videli boste potrditveno sporočilo:

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

注意 事项:

• 如果stanje systemdstoritev jeUnknown,Spremljanje storitev ne bo delovalo.
• Izbrane storitve za spremljanje bodo shranjene v datoteko /usr/local/etc/services-monitor-systemdv.
• Spremljanje opravil cron lahko najdete v datoteki/etc/cron.d/svcMonitor-systemd中prikazati se.

Lahko tudi mimochkconfigUkaz za ročno dodajanje/odstranjevanje storitev:

chkconfig service_name on
chkconfig service_name off

Na primer, ko so omogočene vse razpoložljive storitve, bomo prikazali sporočila cron, kot so:

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

Video vadnica nadzorne plošče CWP Omogoči ServicesMonitor (systemd).

Spodaj je opisano, kako nadzorna plošča CWP v tem članku omogoča spremljanje storitev ServicesMonitor (systemd)YouTubeVideo vadnica▼