• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Question Failed to update Plesk

Marc_L

New Pleskian
When I perform an update of Plesk, the message “Failed to update Plesk” appears on top of the page.

In the “autoinstaller3.log” I see the following:
[2019-01-07 09:34:47.142839] Patches were installed successfully.
[2019-01-07 09:34:47.144499] The changes were applied successfully.

However at the end of the file I see a few rules with the message:
ProductInf3FileGuard destroyed. Build didn't change

My questions are:
  • Do I have to worry about that
  • What do these messages mean
  • How can I avoid the error message “Failed to update Plesk”

Plesk version: Version 17.5.3 Update #64
Operating system: Debian 8.11

Kind regards,

Marc L
 
maybe there are more details in the logfiles

Try to run on CLI
# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

and then

# plesk repair installation

if this is not helping take into consider to contact Plesk support directly
 
maybe there are more details in the logfiles

Try to run on CLI
# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

and then

# plesk repair installation

if this is not helping take into consider to contact Plesk support directly

Thank you for your answer Brujo. However I try to understand what happens.

According to the messages in de logfile “Patches were installed successfully” and “The changes were applied successfully.” I would say the update was successful, but I am not sure. I would like to know why I get the message “Failed to update Plesk” and what does the message “ProductInf3FileGuard destroyed. Build didn't change” means.

I cannot find any other useful messages in the logfile. The las 8 lines of the logfile are:

[2019-01-07 09:34:47.217838] FileFetcher: get file (~empty)/PHP72_17/php72-deb8.0-x86_64.plesk17.inf3
[2019-01-07 09:34:47.217929] Downloading file PHP72_17/php72-deb8.0-x86_64.plesk17.inf3: 0%
[2019-01-07 09:34:47.225677] Downloading file PHP72_17/php72-deb8.0-x86_64.plesk17.inf3: 100% was finished.
[2019-01-07 09:34:47.226157] ProductInf3FileGuard destroyed. Build didn't change
[2019-01-07 09:34:47.226200] FileFetcher: get file (~empty)/SITEBUILDER_17.0.16/sitebuilder-17.0.16-deball-all.inf3
[2019-01-07 09:34:47.226267] Downloading file SITEBUILDER_17.0.16/sitebuilder-17.0.16-deball-all.inf3: 0%
[2019-01-07 09:34:47.231016] Downloading file SITEBUILDER_17.0.16/sitebuilder-17.0.16-deball-all.inf3: 100% was finished.
[2019-01-07 09:34:47.231457] ProductInf3FileGuard destroyed. Build didn't change

Kind regards,
Marc L
 
I have the same issue on Ubuntu 18.04.2 LTS
/var/log/plesk/install/autoinstaller3.log


[2019-02-25 08:44:40.386968] All patches were applied.
[2019-02-25 08:44:40.387013]
[2019-02-25 08:44:40.396155] Patch plesk-17.8.11~patch42 installation summary: 290 items applied, 0 items skipped, 0 items failed.
[2019-02-25 08:44:41.001920] Bootstrapper has finished action (exec time: 0 sec.): parent_name='PLESK_17_8_11', sequence='post-patch', stage='execute', sequence_order='10', operation='install', exec_cmd='/opt/psa/admin/sbin/update_history 42'', m_arch='', output: ~empty
[2019-02-25 08:44:42.169781]
Patches were installed successfully.
[2019-02-25 08:44:42.170324]
The changes were applied successfully.
[2019-02-25 08:44:42.170362] ComponentsExamine::doPostExamine: no components for examination
[2019-02-25 08:44:42.170380] Plesk Installer: installation time 7 sec.
[2019-02-25 08:44:42.170773] FileFetcher: get file (~empty)/PSA_17.8.11/plesk-17.8.11-ubt18.04-x86_64.inf3
[2019-02-25 08:44:42.170868] Downloading file PSA_17.8.11/plesk-17.8.11-ubt18.04-x86_64.inf3: 0%
[2019-02-25 08:44:42.199940] Downloading file PSA_17.8.11/plesk-17.8.11-ubt18.04-x86_64.inf3: 100% was finished.
[2019-02-25 08:44:42.200231] ProductInf3FileGuard destroyed. Build didn't change
[2019-02-25 08:44:42.200252] FileFetcher: get file (~empty)/PHP70_17/php70-ubt18.04-x86_64.plesk17.inf3
[2019-02-25 08:44:42.200279] Downloading file PHP70_17/php70-ubt18.04-x86_64.plesk17.inf3: 0%
[2019-02-25 08:44:42.211231] Downloading file PHP70_17/php70-ubt18.04-x86_64.plesk17.inf3: 100% was finished.
[2019-02-25 08:44:42.211356] ProductInf3FileGuard destroyed. Build didn't change
[2019-02-25 08:44:42.211375] FileFetcher: get file (~empty)/PHP71_17/php71-ubt18.04-x86_64.plesk17.inf3
[2019-02-25 08:44:42.211407] Downloading file PHP71_17/php71-ubt18.04-x86_64.plesk17.inf3: 0%
[2019-02-25 08:44:42.222391] Downloading file PHP71_17/php71-ubt18.04-x86_64.plesk17.inf3: 100% was finished.
[2019-02-25 08:44:42.222562] ProductInf3FileGuard destroyed. Build didn't change
[2019-02-25 08:44:42.222591] FileFetcher: get file (~empty)/PHP72_17/php72-ubt18.04-x86_64.plesk17.inf3
[2019-02-25 08:44:42.222638] Downloading file PHP72_17/php72-ubt18.04-x86_64.plesk17.inf3: 0%
[2019-02-25 08:44:42.233726] Downloading file PHP72_17/php72-ubt18.04-x86_64.plesk17.inf3: 100% was finished.
[2019-02-25 08:44:42.233939] ProductInf3FileGuard destroyed. Build didn't change
[2019-02-25 08:44:42.233973] FileFetcher: get file (~empty)/PHP73_17/php73-ubt18.04-x86_64.inf3
[2019-02-25 08:44:42.234030] Downloading file PHP73_17/php73-ubt18.04-x86_64.inf3: 0%
[2019-02-25 08:44:42.245273] Downloading file PHP73_17/php73-ubt18.04-x86_64.inf3: 100% was finished.
[2019-02-25 08:44:42.245508] ProductInf3FileGuard destroyed. Build didn't change
[2019-02-25 08:44:42.245549] FileFetcher: get file (~empty)/SITEBUILDER_17.8.12/sitebuilder-17.8.12-deball-all.inf3
[2019-02-25 08:44:42.245608] Downloading file SITEBUILDER_17.8.12/sitebuilder-17.8.12-deball-all.inf3: 0%
[2019-02-25 08:44:42.256974] Downloading file SITEBUILDER_17.8.12/sitebuilder-17.8.12-deball-all.inf3: 100% was finished.
[2019-02-25 08:44:42.257195] ProductInf3FileGuard destroyed. Build didn't change
 
This might a Plesk issue.... We're on Update #41 but ran Update #42 via CLI as it has appeared on the Plesk change log.
This section of the log is the most relevent to our post:
Code:
~
Retrieving information about the installed license key...
[2019-02-25 06:34:06.751385] KeyUpdateChecker::doCheck: no components for check key update
[2019-02-25 06:34:06.751428] ComponentsExamine::doPreExamineAndCheckForCriticalIssues: no components for examination
[2019-02-25 06:34:06.751680]
Getting bootstrapper packages to installation list:
[2019-02-25 06:34:06.751723] Following bootstrapper packages will be installed: (empty)
[2019-02-25 06:34:06.751742]  ----------------
[2019-02-25 06:34:06.751757] Getting packages to installation list:
[2019-02-25 06:34:06.751778] Following packages will be installed: (empty)
[2019-02-25 06:34:06.751795]  ----------------
[2019-02-25 06:34:06.751866] Patch for plesk 17.8.11 will not be installed since it is already applied.
[2019-02-25 06:34:06.751896] You already have the latest version of product(s) and all the selected components
installed. Installation will not continue
~
So either; nothing that we already use (or don't use, like the old PHP versions that are part of #Update 42) is affected by this update (but we would have thought PPM-8134 and PPPM-9456 were still applicable...) and so there's genuinely no task to be completed or, there is a possible Plesk issue with Update #42 ;)
 
Update... We ran the CLI process again, as there were also, some Ubuntu updates that were avalailable today.
This this time the Plesk Upgrade #41 > #42 has run as normal, with no errors or cancelled installations.
 
I experienced the same. Last months the Plesk update/upgrades didn't run. Installation stopped everytimes in the beginning.
 
Back
Top