• 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.

Issue Cannot Install Updates within Updates & Upgrades > Add/Remove Components or via Command Line

Craig1986

Basic Pleskian
I run a VPS, which has Plesk (Version 17.8.11) installed, where I have just gone to install a few components via the below steps within the Plesk Interface:
  • Tools & Settings > Updates and Upgrades > Add/Remove Components
For some reason, I am having difficulties whereby when I go to select 'Continue', the page simply refreshes with some extra information at the top of the page rather than progressing to the installation page. I have tried selecting 'Continue' several times but I get the same response. Furthermore, I have tried installing the various components separately (PHP version, Firewall etc) but I get the same issue.

As an alternative, I tried using the Command Line:
  • # plesk installer --select-release-current --install-component psa-firewall
but ended up with the output:
  • BUSY: Update operation was locked by another update process.
    exit status 1
Just wondering what could be causing the issue, and how I can resolve such an issue, as I have not had this issue before. From the Command Line Output, it appears that there is an install already in process. As such, I was thinking that maybe Plesk is running some update in the Background or my current efforts of installation have stopped mid way etc. Is there a way to check on this? The issue has been producing the same outcome for over an hour now. Surely such a Plesk update would not take this long?
 
Please take your text with the word Plesk, separated by comma:
Plesk, BUSY: Update operation was locked by another update process
and start a quick google search.
So, you will be immediately redirected to PLESK SUPPORT ARTICLES, which lead to the best solution.
 
Please take your text with the word Plesk, separated by comma:
Plesk, BUSY: Update operation was locked by another update process
and start a quick google search.
So, you will be immediately redirected to PLESK SUPPORT ARTICLES, which lead to the best solution.
My apologies ... Should had mentioned I had already referred to Unable to open the "Updates and Upgrades" page or start Plesk Installer in CLI: Update operation was locked by another update process where I had killed all processes. Just to make sure, I ran the necessary Command Lines again to ensure the processes did not reappear.

Unfortunately, the issue is still persisting. I was wondering if there could be some kind of Background Task that could be causing an issue or maybe someone has come across some conflict with a particular Component.
 
No prob., no need to apologize. YOU'RE WELCOME... freui.gif
I also follow(ed) the great tutorials by PLESK SUPPORT + BLOGS + FORUM
Everything written and shown in an easy understanding way.
I had exactly the same problem like you last year and it was resolved by the help of Plesk support.
 
Back
Top