Issue cause to 18.0.30 Obsidian fails with DB failure

[pipeman1981]

Hi all,

I tried to upgrade my 17.8.11 to Obsidian, different versions. Latest try was to migrate to 18.0.30 , it fails with

ERROR: Upgrade step 2018-09-04-04-45-30_DetectMysqlForkTypes.php failed with code 1 and output:
[2020-10-06 22:55:32.552] ERR [panel] DB query failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'fork' in 'field list', query was: select `id`, `host`, `port`, `type`, `last_error`, `server_version`, `fork` from DatabaseServers:
0: /opt/psa/admin/plib/Upgrade/upgrade.php:41
ERROR: Plesk\Upgrade\Exception: DB query failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'fork' in 'field list', query was: select `id`, `host`, `port`, `type`, `last_error`, `server_version`, `fork` from DatabaseServers (upgrade.php:41)

Please find attached the full log file.

I already checked the database without sucess:

root@server:/var/www/vhosts# plesk repair db
Warning: Current locale is unusable. Using 'C' instead.

Checking the Plesk database using the native database server tools .. [OK]

Checking the structure of the Plesk database ........................ [OK]

Checking the consistency of the Plesk database ...................... [OK]

Error messages: 0; Warnings: 0; Errors resolved: 0

Does anybody have any idea that could help me to get the upgrade working?

Thanks in advance.

Carsten

 

[IgorG]

Does anybody have any idea that could help me to get the upgrade working?

Try to use this KB article - Plesk is not working after the upgrade: Specified column "status" is not in the row

 

[pipeman1981]

Hej Igor, hej all,
thanks for your quick help, I just tried plesk repair installation and got:

root@server:/# plesk repair installation

Reconfiguring the Plesk installation

Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

 Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
===> Cumulative upgrade and repair of APS controller database has been completed.
===> Cumulative APS controller upgrade and repair (final stage) has been started.
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp17.8.11-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.

**** Product repair started.

===> Checking for previous installation ... found.
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

 Trying to start service mysql... /usr/sbin/mysqld (pid 9128) is running...
done
 Trying to establish test connection... connected
done
 Trying to find psa database... version is 017008011
 Trying to backup MySQL database... done
 MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.17.8.11-17.8.11.20201016-220107.dump.gz
 Finishing up upgrade procedures and rerunning previously failed upgrade actions...
 Checking for the group 'lock-manager'...
 Trying to add supplementary group 'lock-manager' for user 'psaadm'...  already there
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
 Trying to backup MySQL database... done
 MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.17.8.11-17.8.11.20201016-220118.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
Upgrade or repair for 'apsc' (stage 'post') is not required
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
 Trying to reset database user password for 'pma_9EPTamSIxoet@'... done
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
Upgrade or repair for 'core' (stage 'prep') is not required
===> Preparing Plesk database upgrade (revertable stage).

 Trying to set psa database version to 017008011... done
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
===> Plesk database scheme upgrade has been completed.
done
===> Cumulative Plesk upgrade and repair (final stage) has been started.
Upgrade or repair for 'core' (stage 'post') is not required
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
 Trying to upgrade and repair SpamAssassin service configuration... Upgrade or repair for 'spamassassin' (stage 'files') is not required
done
 Trying to upgrade and repair Roundcube webmail configuration... Upgrade or repair for 'roundcube' (stage 'files') is not required
done
 Trying to upgrade Roundcube Web Based mail client configs and DB from '1.3.8' to '1.3.11'... Executing database schema update.

WARNING!
Some problems are found during upgrade Roundcube Web Based mail client configs and DB from '1.3.8' to '1.3.11'. Run /usr/share/psa-roundcube/bin/update.sh manually to complete upgrade.(see log file: /var/log/plesk/install/plesk_17.8.11_repair.log)

Continue...

Synchronizing state of bind9.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable bind9
 Reconfiguring mail subsystem...
 Reconfiguring Apache web server...
 Reconfiguring ProFTPD FTP server...
===> Configuring ProFTPD server
 Reconfiguring AWStats web statistics...
 Reconfiguring WatchDog...
 Restoring SELinux contexts...
Synchronizing state of sw-cp-server.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable sw-cp-server
Synchronizing state of sw-engine.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable sw-engine
Synchronizing state of dovecot.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable dovecot
Synchronizing state of drwebd.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable drwebd
Synchronizing state of spamassassin.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable spamassassin
Synchronizing state of pc-remote.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable pc-remote
Synchronizing state of nginx.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable nginx
Synchronizing state of psa.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable psa
Synchronizing state of networking.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable networking
 Reconfiguring SSL ciphers and protocols...
 Regenerating web servers' configuration files...
 Cleaning active Panel sessions...
 Fixing permissions on Panel packages files
WARNING:failed to get permissions for package diverts others to: /usr/lib/apache2/modules/mod_proxy.so.orig from package /var/cache/apt/archives/libapache2-mod-proxy-psa_2.4.18-ubuntu16.04.17100418_amd64.deb
WARNING:failed to get permissions for package diverts others to: /usr/lib/apache2/modules/mod_proxy_fcgi.so.orig from package /var/cache/apt/archives/libapache2-mod-proxy-psa_2.4.18-ubuntu16.04.17100418_amd64.deb

Bootstrapper repair finished.
Errors occurred while performing the following actions: fix RoundCube configuration.
Check '/var/log/plesk/install/plesk_17.8.11_repair.log' and '/var/log/plesk/install/plesk_17.8.11_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Plesk support.

exit status 1

Before, I tried plesk repair all -v, some issues have been found and fixed.

Can I ignore the findings of the repair installation job and start the upgrade to 18.0.30 again or Do I have to fix these issues manually? If the latter, how can I do that?

Thanks again,

Carsten

 

[Bitpalast]

I see that a Roundcube upgrade of the database has failed. Please carefully check this article if this could apply to your case:

RoundCube webmail is not accessible on Plesk: DATABASE ERROR: CONNECTION FAILED

Applicable to: Plesk Obsidian for Linux Plesk Onyx for Linux Symptoms RoundCube webmail page is not accessible. The following error message is displayed: PLESK_INFO: DATABASE ERROR: CONNECTIO...

support.plesk.com

Make sure you create a full database backup before modifying the database.

 

[pipeman1981]

Hej all,
thanks a lot, I updated roundcube successfuly now, problem was a wrong php-mysql-package.
But nevertheless, the upgrade to plesk 18.0.30 fails with this error in the post installation steps regarding the DatabaseServers table, where the column fork does not exist, indeed.
I do find some more problems regarding missing columns:

ERROR: Upgrade step 2019-03-28-10-02-21_AddCodeToNotifications.php failed with code 1 and output:
[2020-10-20 23:09:29.580] ERR [panel] Specified column "code" is not in the row:
0: /opt/psa/admin/plib/Upgrade/upgrade.php:41
ERROR: Plesk\Upgrade\Exception: Specified column "code" is not in the row (upgrade.php:41)

SUCCESS: Upgrade step 2019-03-28-17-04-01_RemoveDefaultNotifications.php was successfully done.
SUCCESS: Upgrade step 2019-04-15-05-49-51_UpdateIsapiPreCondition.php was successfully done.
SUCCESS: Upgrade step 2019-04-25-08-56-26_ConfigureArrProxy.php was successfully done.
SUCCESS: Upgrade step 2019-04-25-14-46-58_ReportUsage.php was successfully done.
SUCCESS: Upgrade step 2019-06-06-01-40-27_AddAcmeChallengeSite.php was successfully done.
SUCCESS: Upgrade step 2019-06-07-11-26-26_NullDefaultNotificationSubjects.php was successfully done.
SUCCESS: Upgrade step 2019-06-07-17-22-29_SecureIISWebmailsWithoutCertificate.php was successfully done.
SUCCESS: Upgrade step 2019-08-26-12-07-56_InstallExtensionRepairKit.php was successfully done.
ERROR: Upgrade step 2019-08-26-12-48-49_InstallExtensionSslIt.php failed with code 1 and output:
[2020-10-20 23:09:47.604] ERR [extension/sslit] Die Ausfhrung von post-install.php ist fehlgeschlagen. Fehlermeldung: Can not find domain by id 13
[2020-10-20 23:09:47.856] ERR [panel] Die Ausfhrung von post-install.php ist fehlgeschlagen. Fehlermeldung: Can not find domain by id 13:
0: /opt/psa/admin/plib/Upgrade/upgrade.php:41
ERROR: Plesk\Upgrade\Exception: Die Ausfhrung von post-install.php ist fehlgeschlagen. Fehlermeldung: Can not find domain by id 13 (upgrade.php:41)

SUCCESS: Upgrade step 2019-08-26-13-00-13_InstallExtensionComposer.php was successfully done.
SUCCESS: Upgrade step 2019-08-26-13-15-41_InstallExtensionAdvancedMonitoring.php was successfully done.
SUCCESS: Upgrade step 2019-10-09-11-05-57_SendProductAgreement.php was successfully done.
SUCCESS: Upgrade step 2019-11-11-13-20-40_AddWebPMimeType.php was successfully done.
SUCCESS: Upgrade step 2019-11-14-07-15-09_SetDefaultPasswordStrength.php was successfully done.
SUCCESS: Upgrade step 2019-11-19-09-48-55_ResetThemeToOnyx.php was successfully done.
SUCCESS: Upgrade step 2019-12-01-22-23-14_MoveUserSettings.php was successfully done.
SUCCESS: Upgrade step 2019-12-17-06-50-14_SetGlobalDefaultDoc.php was successfully done.
SUCCESS: Upgrade step 2020-01-21-06-04-13_ApplyPleskDirectoriesSecurity.php was successfully done.
SUCCESS: Upgrade step 2020-01-21-06-09-31_ConfigurePleskWebsite.php was successfully done.
SUCCESS: Upgrade step 2020-01-21-06-35-35_DetermineDatabaseServer.php was successfully done.
SUCCESS: Upgrade step 2020-01-23-13-51-50_SwitchLoginDateToPersistentStorage.php was successfully done.
ERROR: Upgrade step 2020-01-31-15-17-42_DefaultWebsiteContent.php failed with code 1 and output:
[2020-10-20 23:10:23.564] ERR [panel] DB query failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'mname' in 'field list', query was: select `id`, `name`, `displayName`, `email`, `status`, `syncRecords`, `syncSoa`, `type`, `ttl`, `ttl_unit`, `refresh`, `refresh_unit`, `retry`, `retry_unit`, `expire`, `expire_unit`, `minimum`, `minimum_unit`, `serial`, `serial_format`, `external_id`, `rnameType`, `mname` from `dns_zone` where `id`=33:
0: /opt/psa/admin/plib/Upgrade/upgrade.php:41
ERROR: Plesk\Upgrade\Exception: DB query failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'mname' in 'field list', query was: select `id`, `name`, `displayName`, `email`, `status`, `syncRecords`, `syncSoa`, `type`, `ttl`, `ttl_unit`, `refresh`, `refresh_unit`, `retry`, `retry_unit`, `expire`, `expire_unit`, `minimum`, `minimum_unit`, `serial`, `serial_format`, `external_id`, `rnameType`, `mname` from `dns_zone` where `id`=33 (upgrade.php:41)

SUCCESS: Upgrade step 2020-02-06-06-29-08_CreateTempUploadDir.php was successfully done.
SUCCESS: Upgrade step 2020-02-11-01-27-43_InstallPleskWebSocketService.php was successfully done.
ERROR: Upgrade step 2020-03-04-13-19-10_AddAutodiscoveryDnsRecords.php failed with code 1 and output:
[2020-10-20 23:10:24.533] ERR [panel] DB query failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'mname' in 'field list', query was: select `id`, `name`, `displayName`, `email`, `status`, `syncRecords`, `syncSoa`, `type`, `ttl`, `ttl_unit`, `refresh`, `refresh_unit`, `retry`, `retry_unit`, `expire`, `expire_unit`, `minimum`, `minimum_unit`, `serial`, `serial_format`, `external_id`, `rnameType`, `mname` from `dns_zone` where `id`=33:
0: /opt/psa/admin/plib/Upgrade/upgrade.php:41
ERROR: Plesk\Upgrade\Exception: DB query failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'mname' in 'field list', query was: select `id`, `name`, `displayName`, `email`, `status`, `syncRecords`, `syncSoa`, `type`, `ttl`, `ttl_unit`, `refresh`, `refresh_unit`, `retry`, `retry_unit`, `expire`, `expire_unit`, `minimum`, `minimum_unit`, `serial`, `serial_format`, `external_id`, `rnameType`, `mname` from `dns_zone` where `id`=33 (upgrade.php:41)

SUCCESS: Upgrade step 2020-03-18-10-49-47_GenerateHostname.php was successfully done.
SUCCESS: Upgrade step 2020-03-19-17-13-39_UpgradeExtensions.php was successfully done.
SUCCESS: Upgrade step 2020-04-17-10-39-36_InitSmbUser.php was successfully done.
SUCCESS: Upgrade step 2020-04-21-02-08-33_RemovePleskImagesVirtualDirectory.php was successfully done.
SUCCESS: Upgrade step 2020-05-13-08-59-59_ApplyEventLogSecurity.php was successfully done.
ERROR: Upgrade step 2020-05-29-04-34-43_RegenerateSubdomainGuids.php failed with code 1 and output:
[2020-10-20 23:10:25.942] ERR [panel] DB query failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'mname' in 'field list', query was: select `id`, `name`, `displayName`, `email`, `status`, `syncRecords`, `syncSoa`, `type`, `ttl`, `ttl_unit`, `refresh`, `refresh_unit`, `retry`, `retry_unit`, `expire`, `expire_unit`, `minimum`, `minimum_unit`, `serial`, `serial_format`, `external_id`, `rnameType`, `mname` from `dns_zone` where `id`=33:
0: /opt/psa/admin/plib/Upgrade/upgrade.php:41
ERROR: Plesk\Upgrade\Exception: DB query failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'mname' in 'field list', query was: select `id`, `name`, `displayName`, `email`, `status`, `syncRecords`, `syncSoa`, `type`, `ttl`, `ttl_unit`, `refresh`, `refresh_unit`, `retry`, `retry_unit`, `expire`, `expire_unit`, `minimum`, `minimum_unit`, `serial`, `serial_format`, `external_id`, `rnameType`, `mname` from `dns_zone` where `id`=33 (upgrade.php:41)

SUCCESS: Upgrade step 2020-06-01-08-49-50_RemoveGlobalPhpIniUploadTmpDirSetting.php was successfully done.
SUCCESS: Upgrade step 2020-06-29-03-27-11_UpdateStandardForwardingSitesRewriteRules.php was successfully done.
SUCCESS: Upgrade step 2020-08-05-14-18-02_RemoveFileSharing.php was successfully done.
SUCCESS: Upgrade step 2020-08-12-15-48-00_DeleteObsoletePhpFpmConfigs.php was successfully done.
SUCCESS: Upgrade step 2020-08-20-02-33-26_RepairSmarterMailForwarding.php was successfully done.
SUCCESS: Upgrade step 2020-08-20-07-04-22_UpdateMailGateDefaultSettings.php was successfully done.
SUCCESS: Upgrade step 2020-08-25-03-09-46_EnableRequestSmugglingFilter.php was successfully done.
Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.


Warning: execute post install/upgrade actions

Starting forced Plesk Key upgrade task
ERROR 1054 (42S22) at line 1: Unknown column 'update_ticket' in 'where clause'

I'm trying to install Plesk 18.0.30 on Ubuntu 16.0.4. Is that OS too old?

 

[IgorG]

I'm trying to install Plesk 18.0.30 on Ubuntu 16.0.4. Is that OS too old?

Bad idea. Ubuntu 16.0.4 will be terminated by the vendor 21 April 2021 - Plesk Lifecycle Policy

 

[pipeman1981]

I know, but according to How to perform dist-upgrade procedure on Linux server with Plesk?, upgrading ubuntu is not yet supported. Therefore, I want to upgrade at least Plesk to the current version.

 

[pipeman1981]

Seems to work now.
I deleted some unnecessary DNS settings and after that, the upgrade succeeded, still with yome errors regarding the DB structure. After upgrade, I could not open phpmyadmin out of plesk, the known db structure failure coming up. After a plesk repair db -y everything seems to run fine.
Thank you all for your appreciated help and patience.