Every update for 11.5 is a complete reinstall?

[King555]

Since I installed Plesk 11.5 (on a Debian 6 server) every update, which should only be a microupdate, is a complete reinstall of Plesk. Plesk wants to upgrade every single package and requires 1.2 GB disk space for doing so.

Why? Is this a normal behaviour in 11.5?

 

[Nikolay.]

Estimation of required space at 1.2 GB is an error. In fact, much less space is needed.

 

[King555]

But is it true that Plesk wants to upgrade every package? Because it lists every package.

Upgrading from Plesk 11.5 #1 to 11.5 #2 was the same installation procedure as updating from 11.0 to 11.5 - with all the problems like non-working Watchdog etc. And I'm afraid that the update to 11.5 #3 does the same.

 

[King555]

Now I upgraded to #3, which is a micro update in my opinion, but it was the same as a complete reinstall (again).

 

[Nikolay.]

I think if you have any problems with Plesk 11.5 updates you should report them as detailed as possible.

 

[King555]

There are not many details missing.

I have Debian 6 x64, I originally installed Plesk 11.0, then upgraded (every time via console) to the next versions (no big version jumps) and now I have the latest version installed. Before 11.5 every small update was just a matter of seconds, but now it takes minutes, because everything is reinstalled.

 

[GravuTrad]

Use the upgrader/updater (updater in this case for the moment) from admin panel. It will normally update your upgrader to the last version and correct this.

 

[King555]

I updated the Plesk updater via the panel, but this did not solve my problem.

 

[Sergey L]

Well, can you show output of updater or something? Which packages you can see updated and downloaded?

 

[King555]

OK, here are some outputs after running "/usr/local/psa/admin/bin/autoinstaller":
(please note that I have the German version)

----------------------------
After pressing Enter several times:
----------------------------

Die folgenden Produktversionen sind verfügbar:

1. [*] Parallels Plesk Panel
  2. (*) Parallels Plesk Panel 11.5.30 (currently installed)

----------------------------
After pressing Enter after the package list:
----------------------------

Es werden Informationen zum installierten Lizenzkey abgerufen...
Komponentenprüfungen werden gestartet...
Datei wird heruntergeladen PSA_11.5.30/examiners/panel_preupgrade_checker.php: 11%..22%..36%..43%..50%..63%..71%..81%..93%..100% fertig.
Datei wird heruntergeladen PSA_11.5.30/examiners/php_launcher.sh: 100% fertig.

Bei der Komponentenvalidierung wurde mindestens 1 wichtiges Problem gefunden:
Parallels Panel pre-upgrade check...
  No packages found matching psa-atmail.
  No packages found matching plesk-roundcube.
  WARNING: Unable to connect to some Plesk ports. Please see /root/parallels/PSA_11.5.30/examiners/plesk10_preupgrade_checker.log for details. Find the full list of the required open ports at http://kb.parallels.com/en/391

Das Fortfahren mit der Installation oder ein Upgrading, ohne die gefundenen Probleme zu lösen,
 kann Ihre Daten beschädigen.

Möchten Sie fortfahren?
Geben Sie entweder Yes (Ja) oder No (Nein) ein:
 [N]:

----------------------------
After typing "Yes":
----------------------------

Folgender Festplattenspeicher wird in den Verzeichnissen benötigt:
/opt: 1200.00 MB.
Benötigt gesamt: 1200.00 MB, vorhanden 790728.00 MB.

Es sind 0 Pakete, die für das ordnungsgemäße Funktionieren dieses Produkts erforderlich sind, wurden
in Ihrem System nicht gefunden.

Es sind 22 Pakete vorhanden, die aktualisiert werden müssen,
um das Produkt zu installieren.

----------------------------
Listing the components:
----------------------------

 1. [U] libpam-plesk-11.5.30-debian6.0.build115130711.12.amd64
  2. [U] plesk-completion-11.5.30-debian6.0.build115130711.12.all
  3. [U] plesk-core-11.5.30-debian6.0.build115130711.12.amd64
  4. [U] plesk-dns-bind-driver-11.5.30-debian6.0.build115130710.19.all
  5. [U] plesk-l10n-11.5.30-debian6.0.build115130712.12.all
  6. [U] plesk-mail-qc-driver-11.5.30-debian6.0.build115130711.12.amd64
  7. [U] plesk-management-node-11.5.30-debian6.0.build115130711.12.amd64
  8. [U] plesk-service-node-utilities-11.5.30-debian6.0.build115130711.12.amd64
  9. [U] plesk-skins-11.5.30-548.13071112.all
 10. [U] plesk-web-hosting-11.5.30-debian6.0.build115130711.12.amd64
 11. [U] psa-courier-authlib-0.65.0-debian6.0.build115130711.12.amd64
 12. [U] psa-courier-imap-4.12.0-debian6.0.build115130710.19.amd64
 13. [U] psa-firewall-11.5.30-debian6.0.build115130711.12.amd64
 14. [U] psa-horde-5.0.4-debian6.0.build115130710.19.all
 15. [U] psa-imp-6.0.4-debian6.0.build115130710.19.all
 16. [U] psa-locale-base-en-us-11.5.30-debian6.0.build115130710.16.all
 17. [U] psa-mail-driver-common-11.5.30-debian6.0.build115130711.12.amd64
 18. [U] psa-pylibplesk-11.5.30-debian6.0.build115130711.12.amd64
 19. [U] psa-qmail-2:1.03-debian6.0.build115130710.19.amd64
 20. [U] psa-spamassassin-11.5.30-debian6.0.build115130711.12.amd64
 21. [U] psa-watchdog-11.5.30-debian6.0.build115130711.12.amd64
 22. [U] psa11.5-php-fakepackage-11.5.30-debian6.0.build115130711.12.amd64

I don't want to install this update right now, because I would have to reboot my server, because Watchdog doesn't work anymore after every big upgrade (and currently every update is a big upgrade).

 

[Nikolay.]

Watchdog doesn't work anymore after every big upgrade

as I said before:

if you have any problems with Plesk 11.5 updates you should report them as detailed as possible.

 

[King555]

Especially the Watchdog problem exists since Plesk 8. I don't believe this will be ever fixed.

But this is not the main problem of this thread.

Can someone tell me, what happens when you now call the updater, let's say updating from 11.5.30 #2 to 11.5.30 #3? Does the updater only install some minor updates or every component including restarting every service (Apache, MySQL, mail servers etc.)?

 

[Nikolay.]

But this is not the main problem of this thread.

Apparently you still don't understand it. The way updates work internally is a purely technical aspect of the product. It can be changed by developers depending on product needs. One update may include only PHP files, other may include binaries and running scripts. This is not something you can influence or should worry about.

The customer-affecting upgrade bugs, on the other hand, is a question of customer satisfaction. Therefore they will be fixed according to their priority. Unless you (or someone else) report in detail which issues you are having, they will (probably) never be fixed. Make a good deed for all Plesk users and heed my advice.

 

[King555]

Maybe I really don't understand.

One update may include only PHP files, other may include binaries and running scripts

Yes, of course, but when the changelog speaks of some minor bug fixes, why does the updater updates absolutely everything? And why is this behaviour only since Plesk 11.5 and not in 8, 9, 10, 11? The thing is not the non-working Watchdog after the update, the thing is that before 11.5 I could do Plesk updates during daytime. But now, since everything is restarted (web server etc.), I can do it only during night, when no one visits my sites.

Unless you (or someone else) report in detail which issues you are having, they will (probably) never be fixed. Make a good deed for all Plesk users and heed my advice.

I still do not know which additional details I could give. I think I posted all information regarding this.

 

[Nikolay.]

But now, since everything is restarted (web server etc.), I can do it only during night, when no one visits my sites.

Valid point. Though not "everything" is restarted every update.

Here's the answer you seek, but will not like: updater updates whatever needs updating. For example, sitting on update #3 will pile up things that need to be updated, consequently making a perception of huge update. Another example: if an issue to be fixed is severe enough, it would affect more stuff and make update "bigger".

As the product lives major issues will be resolved and updates will get (statistically) smaller. Therefore you may keep doing updates at night until Plesk 11.5 moves to the next release tier, if you wish.

I think I posted all information regarding this.

Your choice.

 

[Sergey L]

Can someone tell me, what happens when you now call the updater, let's say updating from 11.5.30 #2 to 11.5.30 #3? Does the updater only install some minor updates or every component including restarting every service (Apache, MySQL, mail servers etc.)?

There are several kinds of possible update:
1) individual files
2) certain correction routines
3) some packages of Plesk
4) 3rd party packages (Apache, MySQL, etc)

Now how it shall work when you get new microupdate (11.5.30 #2,11.5.30 #3, etc):
1) every MU includes fixes for some individual files. They don't cause your 3rd parties updated or restarted
2) some MU may include correction routines which clean and fix previous misconfigurations. It may cause some of your 3rd parties restarted
3) some updates may include re-built packages of Plesk. That's what you have seen in

1. libpam-plesk-11.5.30-debian6.0.build115130711.12.amd64
2. plesk-completion-11.5.30-debian6.0.build115130711.12.all
3. plesk-core-11.5.30-debian6.0.build115130711.12.amd64
...

They may cause your 3rd parties restarted, but not always.
4) Starting 11.5 microupdates DO NOT cause update of Apache, MySQL, etc because of potential site compatibility issues. These components shall be updated separately at convenient time

So to answer your question, updater would bring what we count as minor update in form of #1, #2 or #3. It may include updated parts of Plesk sometimes. And it may cause restart of Apache, MySQL, etc sometimes. It does never include update to Apache, MySQL, etc.

 

[paulieG]

Hi Sergey,

Support ticket 1694303

This is the same issue that we have raised with your support team and been told utter nonsense. Please can you investigate the ticket which has sufficient information to replicate the problem (for anyone else who wants to see if it happens try editing /usr/local/psa/admin/htdocs/theme/css/custom.css on some occasions this file will be overwritten with the original when the Plesk installer reinstalls all packages).

/tmp/autoinstaller3.log also shows that on occasion the updater is (re)installing packages during what should be the MU update process.

This is on CloudLinux 6.4 with updated and clean installs of Plesk 11.5

Paul.