Article ID: 3028, created on Nov 2, 2007, last review on Apr 24, 2016

  • Applies to:
  • Plesk 8.3 for Linux/Unix
  • Plesk 8.2 for Linux/Unix
  • Plesk 8.1 for Linux/Unix


SWsoft Plesk Autoinstaller/Autoupdater tool installs/updates not only Plesk itself but also checks for available updates of components that are not part of Plesk but which Plesk highly depends on, such as apache web server, mysql server and so on. The difference between Plesk for Linux and Plesk for FreeBSD is that

- Linux application updates from operating system vendor come as compiled RPMs, FreeBSD application updates in general are done with application port recompilation. So that Plesk for FreeBSD update usually takes more time, because recompilation takes more time then RPM update,

- Application ports in FreeBSD ports collection are frequently updated and modified, sometimes manual actions are required during port update (they are described in /usr/ports/UPDATING file) and if some third port compilation fails then it will cause that Plesk update interrupts in the middle. In this case you need to find out compilation failure reason, correct it and re-run Plesk update. Of course, RPM update failures on Linux system also happen, but probability of compilation failure is higher then RPM update failure.

So that Plesk update on FreeBSD system in general may take more time and has more chances to interrupt. And the following rules help to make installation and update process safer:

- update to the latest Plesk version is preferred then to earlier version because the latest Plesk version is more convenient to fresher FreeBSD ports,

- download and use the latest console autoinstaller utility from Plesk download pages at,

- if autoinstaller notifies that port collection on your server differs from ports snapshot used during Plesk QA tests, agree to update your collection to Plesk tested one,

- run update when your clients activity is low and keep in mind that update may take more time then you think if interruption happen,

In general it may also be a good idea to have a test copy of server with the same operating system and applications installed for upgrade tests before upgrade of production servers.

5dd10e4b1e2dd7a2aa8a50c580dd41a2 583c136e45a1f548d12213fea9b7833d 9f8b3267dc294b8e42f097f7cddbc524 b8ef5052d936e902043e41759118114e 29d1e90fd304f01e6420fbe60f66f838 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF