Hoe kinne jo tsjinstmonitoring ynskeakelje yn CWP Control Panel ServicesMonitor (systemd)

在linuxOp de server, hâld de tsjinst stabyl rinnend, foar de websideSEOHiel wichtich.

CWP Control PanelSil jo helpe troch ark foar monitoaring fan tsjinsten.

Hoe kinne jo ServicesMonitor (systemd) ynskeakelje yn CWP-kontrôlepaniel?

Om tsjinstmonitoring yn CWP yn te skeakeljen:

1. ferbine mei joCWPynstallaasje
2. 查找Services Config-> ServicesMonitor( systemd )选项
3. Selektearje/Enter:
   Ynskeakelje útskeakelje- Dit sil tsjinstmonitoring ynskeakelje/útskeakelje.
   Email notifikaasjesStjoer nei - Fier it e-postadres yn wêr't jo notifikaasjes sille ûntfange.
   Kontrolearje elk- tiid ynterfal tusken kontrôles
4. Selektearje de tsjinst dy't jo kontrolearje wolle, bygelyks: mariadb.service, monit.service
5. klik提交knop.Jo sille in befêstigingsberjocht sjen:

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

caution:

• 如果systemd statustsjinst isUnknown,Tafersjoch sil net wurkje foar tsjinsten.
• Selekteare tsjinsten om te kontrolearjen sille wurde bewarre yn bestân /usr/local/etc/services-monitor-systemdyn.
• Monitoring cron jobs kinne fûn wurde yn it bestân/etc/cron.d/svcMonitor-systemdMediumlûder sette.

Jo kinne ek trochjaanchkconfigKommando om tsjinsten manuell ta te foegjen / te ferwiderjen:

chkconfig service_name on
chkconfig service_name off

Bygelyks, as alle beskikbere tsjinsten binne ynskeakele, sille wy cron-berjochten werjaan lykas:

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

It folgjende is hoe't it CWP-kontrôlepaniel tsjinstmonitoring ServicesMonitor (systemd) yn dit artikel mooglik makketYouTubeFideo-tutorial▼