• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved MariaDB Upgrade via Plesk hangs

Azurel

Azurel

Silver Pleskian
Username:

TITLE

MariaDB Upgrade via Plesk hangs

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

AlmaLinux 8.10 (Cerulean Leopard)
Plesk Obsidian 18.0.68

PROBLEM DESCRIPTION

I started today in Tools & Settings -> Database Servers -> Upgrade (button)

From MariaDB 10.3.x to 10.11.x and it hangs with this screen.
1741591274332-png.28010


When navigating to another Plesk page, the Plesk login screen appears, indicating a timeout.

STEPS TO REPRODUCE

Upgrade MariaDB

ACTUAL RESULT

GUI hangs (Plesk session timeout)

EXPECTED RESULT

Finishing job

ANY ADDITIONAL INFORMATION

Again in Tools & Settings -> Database Servers shows me now version 10.11.11.

Code: 
MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin
It is already upgraded.

Is there anything else that needs to be done here? I have no idea what else would have happened in the GUI.

the linked article was for me not helpful https://support.plesk.com/hc/en-us/...eshooting-Common-MariaDB-MySQL-Upgrade-Issues

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Here the mysql-error.log:
2025-03-10 7:42:22 0 [Note] Starting MariaDB 10.11.11-MariaDB-log source revision e69f8cae1a15e15b9e4f5e0f8497e1f17bdc81a4 server_uid OOrCEtF++9ho2AxSznRyNhgXYEo= as process 1073724
2025-03-10 7:42:22 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2025-03-10 7:42:22 0 [Note] InnoDB: Number of transaction pools: 1
2025-03-10 7:42:22 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2025-03-10 7:42:22 0 [Note] InnoDB: Using Linux native AIO
2025-03-10 7:42:22 0 [Note] InnoDB: Initializing buffer pool, total size = 12.000GiB, chunk size = 192.000MiB
2025-03-10 7:42:22 0 [Note] InnoDB: Completed initialization of buffer pool
2025-03-10 7:42:22 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2025-03-10 7:42:22 0 [Note] InnoDB: Upgrading redo log: 1.000GiB; LSN=24922139745487
2025-03-10 7:42:22 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2025-03-10 7:42:22 0 [Note] InnoDB: 128 rollback segments are active.
2025-03-10 7:42:22 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2025-03-10 7:42:22 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2025-03-10 7:42:22 0 [Note] InnoDB: log sequence number 24922139745487; transaction id 10477413629
2025-03-10 7:42:22 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2025-03-10 7:42:22 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-03-10 7:42:22 0 [Warning] mariadbd: GSSAPI plugin : default principal 'mariadb/web1.mydomain.com@' not found in keytab
2025-03-10 7:42:22 0 [ERROR] mariadbd: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure. Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is nonexistent or empty.
2025-03-10 7:42:22 0 [ERROR] Plugin 'gssapi' registration as a AUTHENTICATION failed.
2025-03-10 7:42:22 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2025-03-10 7:42:22 0 [ERROR] Incorrect definition of table mysql.event: expected column 'definer' at position 3 to have type varchar(, found type char(141).
2025-03-10 7:42:22 0 [ERROR] mariadbd: Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
2025-03-10 7:42:22 0 [Note] /usr/sbin/mariadbd: ready for connections.
Version: '10.11.11-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 0 MariaDB Server
2025-03-10 7:42:22 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2025-03-10 7:42:22 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).

THIS LINES APPEARS 55 TIMES (SHORTED):

2025-03-10 7:42:23 4 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2025-03-10 7:42:23 4 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
2025-03-10 7:42:25 0 [Note] InnoDB: Buffer pool(s) load completed at 250310 7:42:25
2025-03-10 7:57:58 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown
2025-03-10 7:57:58 0 [Note] InnoDB: FTS optimize thread exiting.
2025-03-10 7:57:58 0 [Note] InnoDB: Starting shutdown...
2025-03-10 7:57:58 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2025-03-10 7:57:58 0 [Note] InnoDB: Restricted to 194704 pages due to innodb_buf_pool_dump_pct=25
2025-03-10 7:57:58 0 [Note] InnoDB: Buffer pool(s) dump completed at 250310 7:57:58
2025-03-10 7:57:59 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2025-03-10 7:57:59 0 [Note] InnoDB: Shutdown completed; log sequence number 24922141614734; transaction id 10477415573
2025-03-10 7:57:59 0 [Note] /usr/sbin/mariadbd: Shutdown complete
2025-03-10 7:57:59 0 [Note] Starting MariaDB 10.11.11-MariaDB-log source revision e69f8cae1a15e15b9e4f5e0f8497e1f17bdc81a4 server_uid OOrCEtF++9ho2AxSznRyNhgXYEo= as process 1076704
2025-03-10 7:57:59 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2025-03-10 7:57:59 0 [Note] InnoDB: Number of transaction pools: 1
2025-03-10 7:57:59 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2025-03-10 7:57:59 0 [Note] InnoDB: Using Linux native AIO
2025-03-10 7:57:59 0 [Note] InnoDB: Initializing buffer pool, total size = 20.000GiB, chunk size = 320.000MiB
2025-03-10 7:57:59 0 [Note] InnoDB: Completed initialization of buffer pool
2025-03-10 7:57:59 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2025-03-10 7:57:59 0 [Note] InnoDB: End of log at LSN=24922141614734
2025-03-10 7:57:59 0 [Note] InnoDB: 128 rollback segments are active.
2025-03-10 7:57:59 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2025-03-10 7:57:59 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2025-03-10 7:57:59 0 [Note] InnoDB: log sequence number 24922141614734; transaction id 10477415574
2025-03-10 7:57:59 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2025-03-10 7:57:59 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-03-10 7:57:59 0 [Warning] mariadbd: GSSAPI plugin : default principal 'mariadb/web1.mydomain.com@' not found in keytab
2025-03-10 7:57:59 0 [ERROR] mariadbd: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure. Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is nonexistent or empty.
2025-03-10 7:57:59 0 [ERROR] Plugin 'gssapi' registration as a AUTHENTICATION failed.
2025-03-10 7:57:59 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2025-03-10 7:57:59 0 [Note] /usr/sbin/mariadbd: ready for connections.
Version: '10.11.11-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 0 MariaDB Server
2025-03-10 7:58:02 0 [Note] InnoDB: Buffer pool(s) load completed at 250310 7:58:02
Click to expand...

Is there anything left to do here?:
2025-03-10 7:42:22 0 [ERROR] Incorrect definition of table mysql.event: expected column 'definer' at position 3 to have type varchar(, found type char(141).
2025-03-10 7:42:22 0 [ERROR] mariadbd: Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
Click to expand...
and
2025-03-10 7:42:22 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2025-03-10 7:42:22 3 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
Click to expand...
 
Thank you for the report, @Azurel . I attempted to reproduce the behavior on a test an Almalinux 8.10 with Plesk 18.0.68 environment, but the upgrade process from MariaDB 10.3.39 to 10.11.11 went through without issues or interruptions. Therefore, I can't quality that as a product bug.

From what I understand you already see the new version listed in the Panel. That indicates that the upgrade is completed. However, to be certain, you may also check the MariaDB version through the command line service mariadb status. What I can suggest is checking for additional MariaDB/phpMyAdmin processes that might be stuck:

ps auxf | grep mariadb
ps auxf | grep phpmyadmin
Click to expand...

If you would like the issue to be further reviewed, I would suggest opening a ticket with Plesk support for an investigation of the issue on your server. To sign-in to support and open a ticket go to:
If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative to get support directly from Plesk:
 
Oh ****, I think I may have found the reason for this issue. Is this new in version 68? I don't remember encountering this behavior before.

As I mentioned, I opened a second window to Plesk (via a bookmark), and the Plesk login page appeared again. This reset the current session, which caused my upgrade process in the GUI to fail.

Steps to reproduce:​

  1. Log in to Plesk.
  2. Open a new tab using a browser bookmark (login_up.php) to access Plesk again.
  3. The login box appears (stop here, do not submit!).
  4. Go back to the previous tab and refresh the page. Result: The login box appears again, and the session is invalid.
Could you add a warning here to prevent accidental calls to "login_up.php" or block it? I have now changed my bookmark to "/cp/home," and it works fine.
 
I am afraid I am having a hard time understanding your point. If you are asking for the MariaDB upgrade tool, it was introduced in January, 2024.

Once the upgrade process is started, closing the current tab/opening a new tab in your browser shouldn't interrupt the upgrade process running in the background, thus that shouldn't be causing the issue regardless of the login URL you are using. If you would like to disable/limit access to the Plesk login page, please check the documentation here.
 
1. Go to https://webpro-lin.demo.plesk.com:8443/login_up.php and login in with user "admin" and password "panel".
Result: You are logged in.

2. Open a second tab in browser and again go to https://webpro-lin.demo.plesk.com:8443/login_up.php DO NOTHING!

3. Switch to first tab and refresh page with F5.
Result: You are logged out.

The second call of https://webpro-lin.demo.plesk.com:8443/login_up.php destroy the session.


That the reason why my upgrade process stopped in GUI. Thats all what I said.

Only call "https://webpro-lin.demo.plesk.com:8443/login_up.php" destroy existing session instead show dashboard (because already logged in), look like a bug.
 
I understand now. Thank you for the clarification, @Azurel . I don't believe the session should be interrupted, but I will double-check with our team if this is by design or a product issue and I will get back to you with confirmation.
 
You must log in or register to reply here.

Similar threads

E
After using Plesk to upgrade Mariadb from 10.5 to 10.11 Wordpress and other apps can no longer connect to 'localhost'
Replies
2
Views
2K
Peter Debik
P
davidds64
Question How to upgrade MariaDB to latest version with Plesk Obsidian on Alma Linux 9
Replies
5
Views
2K
davidds64
davidds64
Dene Wilby
Resolved Upgrading my MariaDB. Issues.
Replies
8
Views
1K
Dene Wilby
Dene Wilby
N
Question What is the proper repo for Alma Mariadb after an upgrade from CentOS7?
Replies
5
Views
891
ShawnOrt
S
J
Resolved MariaDB Upgrade via Plesk
Replies
10
Views
3K
Azurel
Azurel
Back
Top