• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Updater with locked base packages

LegolasTheElf

Basic Pleskian
Hi all,
we have a CentOS 5 Plesk installation installed very few months ago, and we have seen a lot of problems when we update from 8.2 to 8.3 .
first the updater doesn't want to make the upgrade saying that the license was not valid (!!!!), thing that a tech of the staff that have installed us Plesk have fixed doing something to the uploader (don't know what, but it resolved the problem, so we have loved him), and after that we have discovered that webmail doesn't work anymore (when we tried to access webmail.domain.tld we see an error page that say that the domain wasn't configured into the server) that we have fixed with the command /usr/local/psa/admin/sbin/websrvmng -a -v that seems to recreate all the domains config files.

Now, and after have browsed all the net in search of plesk info to solve the previously problems, we have noticed that into the upgrader page we have always checked the two packages "Base packages of Plesk" and "Plesk Updater".
We don't have the orange icon in front of the two rows, and the packages are signaled as "you have an up-to-date version" so we don't want to touch them, especially because we have read about a lot of problems that can born trying to update a just-updated package, but we also want to activate the "Bandwidth Limiter For Apache support (mod_bw)" package to use him, and we have seen a lot of posts here that sayinf that is mandatory to use plesk updater for this things...

someone know how we can unlock the two check for those packages? some kind of CLI command to give or similar?

Thanks a lot
 
issue with autoinstaller was caused by old version of it, you just need to use the latest one.

http://kb.swsoft.com/en/3543

for your latest issue with psa-update packages, try to remove files from /var/spool/up2date/ to another location and run autoinstaller/updater again.
 
Back
Top