• 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!
  • 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 system update seem to stuck, even after more then one reboot

SteffenB

New Pleskian
Server operating system version
Ubuntu 22.04.2 LTS
Plesk version and microupdate number
18.0.50
accidently the update process of system updates was started twice. After one finished, the other stucks, even after 2 reboots of the whole server. See the picture. Any suggestions for me how to handle this?
 

Attachments

  • Bildschirm­foto 2023-03-22 um 08.08.24.png
    Bildschirm­foto 2023-03-22 um 08.08.24.png
    719.7 KB · Views: 5
It's possible that it's just a stuck task and not actual system updates happening. That happens when you, say, reboot the server while it's doing things. Follow this article for the "Canceling a stuck task in Plesk for Linux" answer to be walked through for fixing it, over at https://support.plesk.com/hc/en-us/articles/115002120793--How-to-cancel-a-stuck-task-in-Plesk

(also you had this under the Windows forum but since you're using Linux, it should had been under Obsidian for Linux, I moved it for you though).
 
Back
Top