Kif tippermetti l-monitoraġġ tas-servizz f'CWP Control Panel ServicesMonitor (systemd)

在LinuxFuq is-server, żomm is-servizz jaħdem b'mod stabbli, għall-websajtSEOImportanti ħafna.

Panel tal-Kontroll tas-CWPSe jgħinek permezz ta 'għodod ta' monitoraġġ tas-servizz.

Kif tippermetti ServicesMonitor (systemd) fil-pannell tal-kontroll CWP?

Biex tippermetti l-monitoraġġ tas-servizz fis-CWP:

1. qabbad ma tiegħekCWP安装
2. SibServizzi Konfigurazzjoni->ServicesMonitor( systemd )选项
3. Agħżel/Daħħal:
   Enable / Itfi- Dan se jippermetti/jiskonnettja l-monitoraġġ tas-servizz.
   Email notifikiIbgħat lil - Daħħal l-indirizz elettroniku fejn tirċievi n-notifiki.
   Iċċekkja kull- intervall ta' ħin bejn il-kontrolli
4. Agħżel is-servizz li trid tissorvelja, pereżempju: mariadb.service, monit.service
5. ikklikkja提交buttuna.Se tara messaġġ ta' konferma:

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

Nota:

• 如果status systemdservizz huwaUnknown,Il-monitoraġġ mhux se jaħdem għas-servizzi.
• Is-servizzi magħżula għall-monitoraġġ se jiġu ffrankati fil-fajl /usr/local/etc/services-monitor-systemdfi.
• Il-monitoraġġ tal-impjiegi cron jistgħu jinstabu fil-fajl/etc/cron.d/svcMonitor-systemd中dawwar up.

Tista 'wkoll tgħaddichkconfigKmand biex iżżid/tneħħi s-servizzi manwalment:

chkconfig service_name on
chkconfig service_name off

Pereżempju, meta s-servizzi kollha disponibbli jkunu attivati, aħna se nuru messaġġi cron bħal:

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

Panel tal-Kontroll CWP Ippermetti ServizziMonitor (systemd) Video Tutorial

Dan li ġej huwa kif il-pannell tal-kontroll CWP jippermetti l-monitoraġġ tas-servizz ServicesMonitor (systemd) f'dan l-artikoluYouTubeVideo Tutorial▼