Kiel ebligi servomonitoradon en CWP Kontrolpanelo ServicesMonitor (systemd)

EnlinuxSur la servilo, tenu la servon funkcii stabile, por la retejoSEOTre grava.

CWP KontrolpaneloHelpos vin per servaj monitoraj iloj.

Kiel ebligi ServicesMonitor (systemd) en CWP-kontrolpanelo?

Por ebligi servomonitoradon en CWP:

1. konekti al viaCWPinstalado
2. rigardu suprenServoj Agordo->ServicesMonitor( sistemo )Elekto
3. Elektu/Enigu:
   Ebligi / Malebligi- Ĉi tio ebligos/malŝaltos servomonitoradon.
   Email sciigojSendi al - Enigu la retadreson, kie vi ricevos sciigojn.
   Kontrolu ĉiun- tempointervalo inter kontroloj
4. Elektu la servon, kiun vi volas kontroli, ekzemple: mariadb.service, monit.service
5. Alklaku提交butonon.Vi vidos konfirman mesaĝon:

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

Noto:

• en la okazo sesistema statusoservo estasUnknown,Monitorado ne funkcios por servoj.
• Elektitaj servoj por monitori estos konservitaj en dosiero /usr/local/etc/services-monitor-systemden.
• Monitorado de cron-laboroj troviĝas en la dosiero/etc/cron.d/svcMonitor-systemdMezaaperu.

Vi ankaŭ povas pasichkconfigKomando por mane aldoni/forigi servojn:

chkconfig service_name on
chkconfig service_name off

Ekzemple, kiam ĉiuj disponeblaj servoj estas ebligitaj, ni montros cron-mesaĝojn kiel:

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 Kontrolpanelo Ebligu ServicesMonitor (systemd) Video Lernilo

Jen kiel la CWP-kontrolpanelo ebligas servomonitoradon ServicesMonitor (systemd) en ĉi tiu artikoloYouTubeVideo Lernilo▼