Resolved Plesk updato to 18.0.69 error

[totti240282]

Server operating system version

Ubuntu 24.04.2 LTS

Plesk version and microupdate number

18.0.68

Hello,
i try to update Plesk and obtain this error:

===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp18.0.69-bootstrapper/migrations/
Migration failed: 18.0.69/2025-04-04-16-09-23_add_id_to_sessions.php
Error on rename of './psa/sessions' to './psa/#sql-backup-65c-1efa8' (errno: 168 "Unknown (generic) error from engine")

===> Plesk database scheme was not upgraded completely.

Applying migrations from: /opt/psa/bootstrapper/pp18.0.69-bootstrapper/migrations/
Migration failed: 18.0.69/2025-04-04-16-09-23_add_id_to_sessions.php
Error on rename of './psa/sessions' to './psa/#sql-backup-65c-1efa8' (errno: 168 "Unknown (generic) error from engine")
***** problem report *****
===> Plesk database scheme was not upgraded completely.

 

[Raul A.]

Try to run a Plesk repair:

plesk repair  db -v

Looks like you might have a broken table in the psa database.

 

[totti240282]

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

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

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

 

[totti240282]

is it possible to decrypt the php file to understand what changes it needs to add to the table?

 

[Raul A.]

Unfortunately, it's not possible to decrypt the Plesk PHP files.

Can you select data from the sessions table?

 

[totti240282]

Can someone please tell me which fields were added to that table?
Maybe I'll try to do it manually.

 

[totti240282]

Unfortunately, it's not possible to decrypt the Plesk PHP files.

Can you select data from the sessions table?

Yes.

 

[Raul A.]

I've just upgraded on my AlmaLinux 8 server and it worked.

===> Plesk database scheme upgrade has been started.
Applying migrations from: /usr/local/psa/bootstrapper/pp18.0.69-bootstrapper/migrations/
Migration 18.0.69/2025-04-04-16-09-23_add_id_to_sessions.php applied
===> Plesk database scheme upgrade has been completed.

This is what the table looks like on Plesk Obsidian 18.0.68.2

| sessions | CREATE TABLE `sessions` (
  `sess_id` varchar(33) NOT NULL,
  `type` smallint(5) unsigned NOT NULL DEFAULT 0,
  `login` varchar(255) DEFAULT NULL,
  `ip_address` varchar(39) DEFAULT NULL,
  `ip_dual_stack` varchar(39) DEFAULT NULL,
  `login_time` int(10) unsigned DEFAULT NULL,
  `modified` int(10) unsigned DEFAULT NULL,
  `lifetime` int(10) unsigned DEFAULT NULL,
  PRIMARY KEY (`sess_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_general_ci |

and this is what it looks like on Plesk Obsidian 18.0.69.0

| sessions | CREATE TABLE `sessions` (
  `sess_id` varchar(33) NOT NULL,
  `type` smallint(5) unsigned NOT NULL DEFAULT 0,
  `login` varchar(255) DEFAULT NULL,
  `ip_address` varchar(39) DEFAULT NULL,
  `ip_dual_stack` varchar(39) DEFAULT NULL,
  `login_time` int(10) unsigned DEFAULT NULL,
  `modified` int(10) unsigned DEFAULT NULL,
  `lifetime` int(10) unsigned DEFAULT NULL,
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  PRIMARY KEY (`id`),
  UNIQUE KEY `sess_id` (`sess_id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_general_ci |

You can get the table structure using:

plesk db "show create table sessions"

 

[totti240282]

ok is this line: `id` int(10) unsigned NOT NULL AUTO_INCREMENT,

Many many thanks

 

[totti240282]

I did it, I edited the table by hand and made the file 2025-04-04-16-09-23_add_id_to_sessions.php be ignored