Sida loo sahlo la socodka adeega gudaha CWP Control Panel ServicesMonitor (systemd)

GudahaLinuxSeerfarka, ka dhig adeeggu inuu si xasiloon u shaqeeyo, mareegahaSEOAad muhiim u ah.

CWP Control PanelWaxay kaa caawin doonaan agabka la socodka adeegga.

Sida loo sahlo ServicesMonitor (systemd) ee guddiga kantaroolka ee CWP?

Si loo suurtageliyo la socodka adeegga CWP:

1. ku xidhnow kaagaCWP安装
2. HelAdeegyada Config->ServicesMonitor( systemd )选项
3. Dooro/ Geli:
   Awoodi / Diido- Tani waxay awood u siinaysaa/dami doontaa la socodka adeegga.
   Email ogeysiisyadaU dir - Geli ciwaanka iimaylka halkaas oo aad ka heli doonto ogeysiisyo.
   Hubi mid kasta- waqti u dhexeeya jeegaga
4. Dooro adeegga aad rabto inaad la socoto, tusaale ahaan: mariadb.service, monit.service
5. gujiGudbibadhanka.Waxaad arki doontaa fariinta xaqiijinta:

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

Xusuusin:

• Lacallaxaalad habaysanadeeggu waaUnknown,Kormeerku uma shaqayn doono adeegyada.
• Adeegyada la doortay si loola socdo waxaa lagu keydin doonaa faylka /usr/local/etc/services-monitor-systemdgudaha.
• Shaqooyinka cron la socodka waxaa laga heli karaa faylka/etc/cron.d/svcMonitor-systemdDhexdhexaadsoo jeedi.

Sidoo kale waad gudbi kartaaxikmadAmarka si gacanta loogu daro/kasaar adeegyada:

chkconfig service_name on
chkconfig service_name off

Tusaale ahaan, marka dhammaan adeegyada jira la furo, waxaanu soo bandhigi doonaa farriimaha cron sida:

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

Kontoroolka CWP wuxuu u sahlaa ServicesMonitor (systemd) casharka fiidyaha

Midda soo socota waa sida guddiga kantaroolka CWP uu awood ugu siiyo la socodka adeegga ServicesMonitor (systemd) ee maqaalkanYouTubeCasharrada Fiidiyowga▼