• 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.

Issue Error when updating to 18.0.50 and during plesk repair installation

opus68

New Pleskian
Server operating system version
CentOS Linux 7.9.2009
Plesk version and microupdate number
Plesk Obsidian 18.0.50
I ran into a problem report when updating two servers from 18.0.49 to 18.0.50. When trying to "repair plesk installation" the same problem re-appears and repair fails. However, "plesk repair all -n" flags no errors or warnings.

Please see below the relevant excerpt from the installation log.

Thanks!

Code:
INFO: Applicable tasks:
2019-02-18-14-09-55
2019-04-25-14-46-58
2020-03-19-17-13-39
INFO: Executing upgrade task: 2019-02-18-14-09-55 (forced)
SUCCESS: Upgrade step 2019-02-18-14-09-55_InstallEssentialExtensions.php was successfully done.
ERROR: Upgrade step 2019-04-25-14-46-58_ReportUsage.php failed with code 1 and output:
INFO: Executing upgrade task: 2019-04-25-14-46-58 (forced)
PHP Warning: Trying to access array offset on value of type null; File: /usr/local/psa/admin/plib/ServerInfo/System.php, Line: 349

PHP Warning: Trying to access array offset on value of type null
Line: 349
File: /usr/local/psa/admin/plib/ServerInfo/System.php
Stack Trace:
#0  Smb_Exception_Syntax::handleError(2, Trying to access array offset on value of type null, /usr/local/psa/admin/plib/ServerInfo/System.php, 349) called at [/usr/local/psa/admin/plib/ServerInfo/System.php:349]
#1  Plesk\ServerInfo\System->getVzTemplate() called at [/usr/local/psa/admin/plib/ServerInfo/Structure.php:54]
#2  Plesk\ServerInfo\Structure->Plesk\ServerInfo\{closure}(vz-template) called at [/usr/local/psa/admin/plib/ServerInfo/Structure.php:26]
#3  Plesk\ServerInfo\Structure->eachField(Closure Object ()) called at [/usr/local/psa/admin/plib/ServerInfo/Structure.php:58]
#4  Plesk\ServerInfo\Structure->get() called at [/usr/local/psa/admin/plib/ServerInfo/Structure.php:81]
 
Hi all,

some added information: it seems to me that the "ReportUsage" daily maintenance task is being called during upgrade/repair and returns a warning which may be the culprit. Running the daily maintenance task manually gives

Code:
plesk daily -f ReportUsage
PHP Warning: Trying to access array offset on value of type null; File: /usr/local/psa/admin/plib/ServerInfo/System.php, Line: 349

PHP Warning:  Trying to access array offset on value of type null in /usr/local/psa/admin/plib/ServerInfo/System.php on line 349
PHP Warning: Trying to access array offset on value of type null; File: /usr/local/psa/admin/plib/ServerInfo/System.php, Line: 360

PHP Warning:  Trying to access array offset on value of type null in /usr/local/psa/admin/plib/ServerInfo/System.php on line 360

I don't think this was the case before upgrade to 18.0.50.

Does anybody observe the same behaviour? I am not aware of any changes to the server configuration that may be causing that.

Thanks!
 
Hi @opus68, thank you for reporting this here. According to developers, this is a known issue that has aready been fixed. The fix will become available in version 18.0.51. The current warning is a warning only. It does not have a severe impact on anything and can be ignored for now. Your system should run as expected on the current 18.0.50 version.
 
Back
Top