Si të aktivizoni monitorimin e shërbimit në CWP Control Panel ServicesMonitor (sistem)

在LinuxNë server, mbajeni shërbimin të funksionojë në mënyrë të qëndrueshme, për faqen e internetitSEOShume e rendesishme.

Paneli i kontrollit CWPDo t'ju ndihmojë përmes mjeteve të monitorimit të shërbimit.

Si të aktivizoni ServicesMonitor (sistemuar) në panelin e kontrollit CWP?

Për të aktivizuar monitorimin e shërbimit në CWP:

1. lidheni me tuajinCwp安装
2. GjejShërbimet Config->ServicesMonitor( systemd )Options
3. Zgjidh/Fut:
   Enable / Disable- Kjo do të mundësojë/çaktivizojë monitorimin e shërbimit.
   Email njoftimeDërgo te - Fusni adresën e emailit ku do të merrni njoftimet.
   Kontrolloni çdo- intervali kohor ndërmjet kontrolleve
4. Zgjidhni shërbimin që dëshironi të monitoroni, për shembull: mariadb.service, monit.service
5. klikoni提交butonin.Do të shihni një mesazh konfirmimi:

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

注意 事项:

• 如果statusi i sistemuarshërbimi ështëUnknown,Monitorimi nuk do të funksionojë për shërbimet.
• Shërbimet e zgjedhura për monitorim do të ruhen në skedar /usr/local/etc/services-monitor-systemdnë.
• Monitorimi i punëve të cron mund të gjendet në skedar/etc/cron.d/svcMonitor-systemd中ngrite.

Ju gjithashtu mund të kalonichkconfigKomanda për të shtuar/hequr manualisht shërbimet:

chkconfig service_name on
chkconfig service_name off

Për shembull, kur të gjitha shërbimet e disponueshme janë aktivizuar, ne do të shfaqim mesazhe cron si:

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

Udhëzues video për aktivizimin e panelit të kontrollit CWP

Më poshtë është se si paneli i kontrollit CWP në këtë artikull mundëson monitorimin e shërbimit ServicesMonitor (sistem)YouTubeVideo tutorial ▼