Ahoana ny fomba ahafahana manara-maso ny serivisy amin'ny CWP Control Panel ServicesMonitor (systemd)

InLinuxEo amin'ny mpizara, tazomy hatrany ny serivisy, ho an'ny tranokalaSEOTena zava-dehibe.

CWP Control PanelHanampy anao amin'ny alàlan'ny fitaovana fanaraha-maso serivisy.

Ahoana no ahafahan'ny ServicesMonitor (systemd) ao amin'ny tontonana fanaraha-maso CWP?

Mba ahafahana manara-maso ny serivisy amin'ny CWP:

1. mifandray amin'ny anaoCWPfametrahana
2. hitadyServices Config->ServicesMonitor( systemd )选项
3. Select/Enter:
   Enable / Disable- Izany dia ahafahana / manakana ny fanaraha-maso ny serivisy.
   Email fampahafantaranaAlefaso any - Ampidiro ny adiresy mailaka izay handraisanao fampahafantarana.
   Jereo tsirairay- elanelana eo anelanelan'ny fisavana
4. Safidio ny serivisy tianao hojerena, ohatra: mariadb.service, monit.service
5. tsindrioSubmitbokotra.Hahita hafatra fanamafisana ianao:

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

fepetra:

• 如果sata systemdserivisy diaUnknown,Tsy hiasa ho an'ny serivisy ny fanaraha-maso.
• Ny serivisy voafantina hojerena dia hotehirizina ao anaty rakitra /usr/local/etc/services-monitor-systemdin.
• Ny fanaraha-maso ny asa cron dia hita ao amin'ny rakitra/etc/cron.d/svcMonitor-systemdMediummipoitra.

Afaka mandalo ihany koa ianaochkconfigDidy manampy/manala tolotra tanana:

chkconfig service_name on
chkconfig service_name off

Ohatra, rehefa alefa ny serivisy rehetra misy, dia hampiseho hafatra cron toy ny:

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

Ity manaraka ity dia ny fomba ahafahan'ny CWP control panel ahafahan'ny serivisy fanaraha-maso ServicesMonitor (systemd) ato amin'ity lahatsoratra ityYouTubeVideo Tutorial▼