• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Forwarded to devs Upgrade to 18.0.37 fails in step TrimPlanNames

Hangover2

Regular Pleskian
Username: Hangover2

TITLE

Upgrade to 18.0.37 fails in step TrimPlanNames

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.36 to 37, Debian 10.10, x86-64

PROBLEM DESCRIPTION

Upgrade to 18.0.37 fails in step TrimPlanNames

STEPS TO REPRODUCE

Start upgrade from Plesk Obsidian 18.0.36 to 18.0.37
Plesk Edition: Web Pro Edition

ACTUAL RESULT

ERROR: Upgrade step 2021-07-01-11-34-45_TrimPlanNames.php failed with code 255 and output:
[2021-07-20 13:13:41.408] 9484:60f6afe560510 ERR [panel] Unknown action: template_reseller_update.
PHP Fatal error: Uncaught JMS\Serializer\Exception\RuntimeException: Could not decode JSON, syntax error - malformed JSON. in /opt/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php:240
Stack trace:
#0 /opt/psa/admin/plib/vendor/jms/serializer/src/Serializer.php(245): JMS\Serializer\JsonDeserializationVisitor->prepare('')
#1 /opt/psa/admin/plib/vendor/jms/serializer/src/Serializer.php(180): JMS\Serializer\Serializer->visit(Object(JMS\Serializer\GraphNavigator\DeserializationGraphNavigator), Object(JMS\Serializer\JsonDeserializationVisitor), Object(JMS\Serializer\DeserializationContext), '', 'json', 'Plesk\\Task\\Mana...')
#2 /opt/psa/admin/plib/Task/Manager.php(72): JMS\Serializer\Serializer->deserialize('', 'Plesk\\Task\\Mana...', 'json')
#3 /opt/psa/admin/plib/WebServerManager/Adapter/AsyncReconfiguration.php(49): Plesk\Task\Manager->createTask(Object(Plesk\Task\Manager\Request))
#4 /opt/psa/admin/plib/WebServerManager/Adapter/AsyncReconfiguration.php(21): WebServerManager_Adapter_Apache->taskManagerExe in /opt/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php on line 240
Fatal error: Uncaught JMS\Serializer\Exception\RuntimeException: Could not decode JSON, syntax error - malformed JSON. in /opt/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php:240
Stack trace:
#0 /opt/psa/admin/plib/vendor/jms/serializer/src/Serializer.php(245): JMS\Serializer\JsonDeserializationVisitor->prepare('')
#1 /opt/psa/admin/plib/vendor/jms/serializer/src/Serializer.php(180): JMS\Serializer\Serializer->visit(Object(JMS\Serializer\GraphNavigator\DeserializationGraphNavigator), Object(JMS\Serializer\JsonDeserializationVisitor), Object(JMS\Serializer\DeserializationContext), '', 'json', 'Plesk\\Task\\Mana...')
#2 /opt/psa/admin/plib/Task/Manager.php(72): JMS\Serializer\Serializer->deserialize('', 'Plesk\\Task\\Mana...', 'json')
#3 /opt/psa/admin/plib/WebServerManager/Adapter/AsyncReconfiguration.php(49): Plesk\Task\Manager->createTask(Object(Plesk\Task\Manager\Request))
#4 /opt/psa/admin/plib/WebServerManager/Adapter/AsyncReconfiguration.php(21): WebServerManager_Adapter_Apache->taskManagerExe in /opt/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php on line 240
Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.
Warning: execute post install/upgrade actions
***** installing problem report *****
Warning: execute post install/upgrade actions
***** installing problem report *****
Warning: execute post install/upgrade actions
STOP plesk-core-18.0 upgrading AT Tue Jul 20 13:14:05 CEST 2021: PROBLEMS FOUND

EXPECTED RESULT

no error

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you.
The bug is confirmed. Internal issue PPPM-13114 has been created.
 
Question: Will the upgrade need to be re-run or while the fix for PPPM-13114 fix it for already upgraded installs?
 
Can confirm. Same bug on CentOS Linux 7.9.2009 (Core) while upgrading from 18.0.36 to 18.0.37.

Code:
Trying to establish test connection... connected
done
===> Cumulative APS controller upgrade (final stage) has been started.
Upgrade or repair for 'apsc' (stage 'post') is not required
===> Cumulative upgrade of APS controller (final stage) has been completed.
===> Cumulative Plesk upgrade (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade of Plesk (final stage) has been completed.
Trying to add header to file /usr/local/psa/etc/webalizer.conf... file /usr/local/psa/etc/webalizer.conf already contains required header
SUCCESS: Upgrade step 2019-02-18-14-09-55_InstallEssentialExtensions.php was successfully done.
SUCCESS: Upgrade step 2019-04-25-14-46-58_ReportUsage.php was successfully done.
SUCCESS: Upgrade step 2020-03-19-17-13-39_UpgradeExtensions.php was successfully done.
ERROR: Upgrade step 2021-07-01-11-34-45_TrimPlanNames.php failed with code 255 and output:
PHP Fatal error: Uncaught JMS\Serializer\Exception\RuntimeException: Could not decode JSON, syntax error - malformed JSON. in /usr/local/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php:240
Stack trace:
#0 /usr/local/psa/admin/plib/vendor/jms/serializer/src/Serializer.php(245): JMS\Serializer\JsonDeserializationVisitor->prepare('')
#1 /usr/local/psa/admin/plib/vendor/jms/serializer/src/Serializer.php(180): JMS\Serializer\Serializer->visit(Object(JMS\Serializer\GraphNavigator\DeserializationGraphNavigator), Object(JMS\Serializer\JsonDeserializationVisitor), Object(JMS\Serializer\DeserializationContext), '', 'json', 'Plesk\\Task\\Mana...')
#2 /usr/local/psa/admin/plib/Task/Manager.php(72): JMS\Serializer\Serializer->deserialize('', 'Plesk\\Task\\Mana...', 'json')
#3 /usr/local/psa/admin/plib/WebServerManager/Adapter/AsyncReconfiguration.php(49): Plesk\Task\Manager->createTask(Object(Plesk\Task\Manager\Request))
#4 /usr/local/psa/admin/plib/WebServerManager/Adapter/AsyncReconfiguration.php(21): WebServerMa in /usr/local/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php on line 240

Fatal error: Uncaught JMS\Serializer\Exception\RuntimeException: Could not decode JSON, syntax error - malformed JSON. in /usr/local/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php:240
Stack trace:
#0 /usr/local/psa/admin/plib/vendor/jms/serializer/src/Serializer.php(245): JMS\Serializer\JsonDeserializationVisitor->prepare('')
#1 /usr/local/psa/admin/plib/vendor/jms/serializer/src/Serializer.php(180): JMS\Serializer\Serializer->visit(Object(JMS\Serializer\GraphNavigator\DeserializationGraphNavigator), Object(JMS\Serializer\JsonDeserializationVisitor), Object(JMS\Serializer\DeserializationContext), '', 'json', 'Plesk\\Task\\Mana...')
#2 /usr/local/psa/admin/plib/Task/Manager.php(72): JMS\Serializer\Serializer->deserialize('', 'Plesk\\Task\\Mana...', 'json')
#3 /usr/local/psa/admin/plib/WebServerManager/Adapter/AsyncReconfiguration.php(49): Plesk\Task\Manager->createTask(Object(Plesk\Task\Manager\Request))
#4 /usr/local/psa/admin/plib/WebServerManager/Adapter/AsyncReconfiguration.php(21): WebServerMa in /usr/local/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php on line 240
Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.


Warning: execute post install/upgrade actions

***** installing problem report *****
Warning: execute post install/upgrade actions
***** installing problem report *****
Warning: execute post install/upgrade actions
STOP plesk-core-18.0 upgrading AT Wed Jul 28 16:59:34 EEST 2021: PROBLEMS FOUND
===> Configuring ProFTPD server
 
Indeed -

My concern is that while it will be fixed for future updates will the "Run upgrade with option --repair to rerun failed steps." need to be manually run on installations that have already been upgraded?
 
Back
Top