• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Alternative for Watchdog on Ubuntu 22.04

H.W.B

Regular Pleskian
Server operating system version
Ubuntu 22.04.2 LTS
Plesk version and microupdate number
Version 18.0.52 Update #3
Hello

Ubuntu 22.04 does not support the Watchdog package from Plesk.
Is there an alternive available that monitors services and can restart them??

Thank you
Henk
 
Watchdog uses the Monit package, which can be installed separately:

Googling for "ubuntu 22.04 mmonit" reveals many guides to install and configure Monit.
 
This might be useful for you:

 
Hello Maarten,

Set the Panel.ini with all my services.
Only changed the restart=always to Restart=on-failure because if always, every service is restarting every 7 seconds.....
So now to see if this works.
Thank you
 
Hello Maarten,

I tested with fail2ban to stop the service, but he didn't restart it....
is this ok??
In the panel.ini i entered:
[fail2ban]
Service.RestartSec = 7
Service.Restart = on-failure


Henk
 
You should enter this in panel.ini instead of [fail2ban]:
Code:
[systemd]
Service.RestartSec = 7
Service.Restart = always

I just tested it, and it works as expected:
Code:
# /usr/local/psa/admin/sbin/register_service --enable fail2ban

# systemctl cat fail2ban | grep -i restart
Restart=on-failure
RestartPreventExitStatus=0 255

# ps -ef | grep fail2ban
root     1010167       1  0 Jun06 ?        00:39:07 /usr/bin/python2 /usr/bin/fail2ban-server -xf start

# kill -9 1010167

# tail -f /var/log/messages
Jun 10 12:24:10 host systemd[1]: fail2ban.service: Main process exited, code=killed, status=9/KILL
Jun 10 12:24:10 host systemd[1]: fail2ban.service: Failed with result 'signal'.
Jun 10 12:24:10 host systemd[1]: fail2ban.service: Service RestartSec=100ms expired, scheduling restart.
Jun 10 12:24:10 host systemd[1]: fail2ban.service: Scheduled restart job, restart counter is at 1.
Jun 10 12:24:10 host systemd[1]: Stopped Fail2Ban Service.
Jun 10 12:24:10 host systemd[1]: Starting Fail2Ban Service...
Jun 10 12:24:10 host systemd[1]: Started Fail2Ban Service.
 
Hello Maarten,

I chaged it to systemd and now it works!!
Thank you
I have entered all my services in the panel.ini.
Are there anymore that uses systemd instead of there own servicename???
If you want i can list them, but there are a lot..

Henk
 
Back
Top