Modx version 2.7.2 (I’m about to upgrade it)
PHP 7.3
Attempting to install BackupModx 3.0.0.
Installation stops with this in the install console.
Console running…
Error HY000 executing statement: Array ( [0] => HY000 [1] => 2006 [2] => MySQL server has gone away )
Error HY000 executing statement: INSERT INTO modx_session (id, access, data) VALUES (‘8f8925b31fc60ecbca922f1854a719b2’, 1621437792, ‘modx.user.contextTokens|a:1:{s:3:"mgr";i:1;}modx.user.0.resourceGroups|a:1:{s:3:"mgr";a:0:{}}modx.user.0.attributes|a:1:{s:3:"mgr";a:5:{s:16:"modAccessContext";a:1:{s:3:"web";a:1:{i:0;a:3:{s:9:"principal";i:0;s:9:"authority";s:1:"0";s:6:"policy";a:3:{s:4:"load";b:1;s:6:"formit";b:1;s:18:"formit_encryptions";b:0;}}}}s:22:"modAccessResourceGroup";a:0:{}s:17:"modAccessCategory";a:0:{}s:28:"sources.modAccessMediaSource";a:0:{}s:18:"modAccessNamespace";a:0:{}}}modx.mgr.user.token|s:52:"modx5c0ff28a1dc3e1.50830185_160a525e68fbb94.99315366";modx.mgr.session.cookie.lifetime|i:0;modx.mgr.user.config|a:0:{}modx.user.1.userGroupNames|a:1:{i:0;s:13:"Administrator";}’) Array ( [0] => HY000 [1] => 2006 [2] => MySQL server has gone away )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.excludeFiles )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.targetPath )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.cronKey )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.cronFiles )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.cronDatabase )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.cronNote )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.cronEnable )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.cronMaxDatabase )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.cronMaxFiles )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.groups )
Attempting to preserve files at /home/xxxxxxxx/public_html/assets/components/backupmodx into archive /home/xxxxxxxx/public_html/core/packages/backupmodx-3.0.0-pl/modCategory/43f8d105038d35333c554d899fb2f70c.0.preserved.zip
PHP notice: A non well formed numeric value encountered
Attempting to install package with signature: backupmodx-3.0.0-pl
PHP warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”?
Package found…now preparing to install.
PHP warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”?
PHP warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”?
Grabbing package workspace…
Workspace environment initiated, now installing package…
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.debug )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.excludeFolders )
Skipping vehicle object of class modSystemSetting (data object exists and cannot be upgraded); criteria: Array ( [key] => backupmodx.excludeFiles )
Attempting to preserve files at /home/xxxxxxxx/public_html/core/components/backupmodx into archive /home/xxxxxxxx/public_html/core/packages/backupmodx-3.0.0-pl/modCategory/43f8d105038d35333c554d899fb2f70c.1.preserved.zip
PHP notice: A non well formed numeric value encountered
Error HY000 executing statement: Array ( [0] => HY000 [1] => 2006 [2] => MySQL server has gone away )
That suggests the database connection was dropped at the very start of the installation. That could be due to a wait_timeout (if the package takes a long time to unzip) or some sort of security on the server killing the connection for whatever reason.
That php notice by itself is not very useful in debugging, though it is likely related to a problem. Interesting though that you find it on two different packages - typically such issues are package specific. There’s likely a php error hidden either in a php error log on the server, or in the response to the initial connector request when the installation started. Getting to that error would be immensely helpful to identify the problem.
That’s either SiteDash making sure your core is locked down, or visiting the MODX dashboard which also sends a request to the changelog to make sure it’s not readable.
Did you not find a PHP error log? If not you’ll have to dig into the browser console to look at the connector request when starting the installation as I mentioned to see if there’s an error there.
The PHP logging was deactivated. So I turned it in via php.ini. After attempting to install the extras, they only error in the log was a bunch of these:
[19-May-2021 20:35:54 Europe/Amsterdam] PHP Warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”? in /home/xxxxxxx/public_html/core/model/modx/modcachemanager.class.php on line 605