• 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 The System Updates tool is already installing updates in automatic mode. Please try later.

GlennT

Basic Pleskian
I am getting "The System Updates tool is already installing updates in automatic mode. Please try later." when trying to update system components on Onyx 17.0.x.
  • I don't have system components set to automatically update.
  • I do have Plesk + third party components set to automatically update.
I tried disabling auto updates for Plesk + components but that did not work.

This is happening on two servers and is a recent problem.

Sounds like something isn't working correctly in Plesk.

G
 
Hi GlennT,
( and Hi malfunction, )

in case of a message like:

The System Updates tool is already installing updates in automatic mode. Please try later
pls. make sure to check with

Code:
ps -aux | grep installer
and/or
Code:
ps aux | grep yum
Code:
ps aux | grep apt
( depending to your current operating system! )

... that there is no other instance currently running on your server, as there is only ONE instance allowed. Unfinished or orphanded processes might interfere here, which should be corrected, before you continue.
 
Thanks UFHH01, that was helpful, I found some stray yum processes running. Killing those wasn't all of it, still left a bit of a mess of incomplete updates, but I was able to sort that out and we're back to normal now.
 
Back
Top