• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Updated MariaDB from 10.6 to 12.3; Plesk update now reports errors. "ERROR while trying to detect MySQL service name"

LTUser

Regular Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.82 Web Pro Edition
MariaDB/MySQL is running without any issues; however, Plesk updates are no longer working.


/opt/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --show-upgradable-components --enable-xml-output

"**** Product prep-install started.
Create user 'psaadm' and group 'psaadm'
Group 'psaadm' already exists
Checking for the user 'psaadm'...
User 'psaadm' already exists
Create group 'swkey-data'
Group 'swkey-data' already exists
Trying to add supplementary group 'swkey-data' for user 'psaadm'... already there
Create group 'psaserv'
Group 'psaserv' already exists
Trying to add supplementary group 'psaserv' for user 'psaadm'... already there
Create group 'psacln'
Group 'psacln' already exists
Trying to got legacy variables... done
config updated
===> Updated /etc/psa/psa.conf
Trying to save legacy variables... done

ERROR while trying to detect MySQL service name

Check the error reason (see log file: /var/log/plesk/install/plesk_18.0.82_installation.log), fix and try again
***** problem report *****
ERROR while trying to detect MySQL service name
Bootstrapper has finished action (exec time: 2 sec.): parent_name='panel', sequence='prep', stage='execute', sequence_order='0', operation='install', exec_cmd='/opt/psa/bootstrapper/pp18.0.82-bootstrapper/bootstrapper.sh prep-install BASE'', m_arch='', exit code: 1, output:
**** Product prep-install started.
Create user 'psaadm' and group 'psaadm'
Group 'psaadm' already exists
Checking for the user 'psaadm'...
User 'psaadm' already exists
Create group 'swkey-data'
Group 'swkey-data' already exists
Trying to add supplementary group 'swkey-data' for user 'psaadm'... already there
Create group 'psaserv'
Group 'psaserv' already exists
Trying to add supplementary group 'psaserv' for user 'psaadm'... already there
Create group 'psacln'
Group 'psacln' already exists
Trying to got legacy variables... done
config updated
===> Updated /etc/psa/psa.conf
Trying to save legacy variables... done

ERROR while trying to detect MySQL service name

***** problem report *****
ERROR while trying to detect MySQL service name

[2026-10-29 11:45:24.122156] Bootstrapper has finished action (exec time: 0 sec.): parent_name='PLESK_18_0_82', sequence='prep', stage='rollback', sequence_order='1', operation='install', exec_cmd='rm -f /run/psa-bootstrapper-mode.flag; rm -f /run/plesk-panel-maintenance-mode.flag; rm -f /run/plesk-panel-upgrade-failure.flag; :'', m_arch='', exit code: 0, output: ~empty
 
root@work:~# systemctl status mysql
● mariadb.service - MariaDB 12.3.3 database server
Loaded: loaded (/etc/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/mariadb.service.d
└─90-performance-booster.conf
/etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
/etc/systemd/system/mysql.service.d
└─override.conf
Active: active (running) since Thu 2026-10-29 11:54:45 CET; 43min ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 1727 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 1818 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 1848 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && >
Process: 2169 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 2171 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
Main PID: 1870 (mariadbd)
Status: "Taking your SQL requests now..."
Tasks: 29 (limit: 38327)
Memory: 4.0G
CPU: 2min 1.548s
CGroup: /system.slice/mariadb.service
└─1870 /usr/sbin/mariadbd

Any Help?
 
Checking the structure of the Plesk database

Wrong attributes for the column 'content' in the table
'CopilotMessages': ................................................ [ERROR]
- The attribute 'type' value mismatch: mediumtext in the original
schema and text in the Plesk database.
Creating a database dump ........................................
Execution failed.
Command: mysqldump.sh
Arguments: Array
(
[0] => --title
[1] => preresolve
)

Details:
***** problem report *****
ERROR while trying to detect MySQL service name

Check the error reason (see log file: /var/log/plesk/mysqldump.log), fix and try again
 
If no one helps you and navigating through support structures and associated accounts proves too complicated, then help yourself. (Always remember to create backups first!)
Solution:
My problem, described above, recently only affected the upgrade packages: plesk-roundcube and psa-phpmyadmin.

It seems the developers, in a script in /etc/init.d, are only checking for the presence of "mysql," even though mariadb is installed there, and therefore—for whatever reason—only "mariadb" is found in that directory.

Long story short, you change to the same directory in the root console with: "cd /etc/init.d" and create a symbolic link to the missing Mysql installation: "ln -s mysql mariadb". This resolves the "ERROR while trying to detect MySQL service name" error.

It's completely incomprehensible to me how a professional developer could possibly use this method to check if and which SQL server is installed. The developers of a product like Plesk should be able to do better than this...

Problem/Issue is fixed.
(Sorry, translated by Google. English is not my native language.)
 
Hi @LTUser,

thanks for posting your solution.

One important correction, because the command as written cannot work:

The syntax is "ln -s TARGET LINKNAME".

Your command
Code:
ln -s mysql mariadb
would create a link called "mariadb" pointing to "mysql".
But according to your description, /etc/init.d/mariadb already exists and /etc/init.d/mysql is the missing one.

So the link needs to go the other way round:
Code:
ls -l /etc/init.d/ | grep -Ei 'mysql|maria'
Code:
ln -s /etc/init.d/mariadb /etc/init.d/mysql
Background: the Plesk bootstrapper detects the database service via the legacy SysV init script /etc/init.d/mysql.

Newer MariaDB packages (here 12.3.3) no longer provide it, even though the systemd unit works fine. That is why the autoinstaller and mysqldump.sh abort with "ERROR while trying to detect MySQL service name".

After creating the link, please verify:
Code:
plesk repair installation
Code:
/opt/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --show-upgradable-components

The CopilotMessages error (mediumtext vs. text) is a separate schema mismatch and should be handled by:
Code:
plesk repair db

Please make a backup first:
Code:
plesk db dump psa > /root/psa-backup.sql

Note that this symlink is only a workaround. Please also check whether MariaDB 12.3 is officially supported by your Plesk version, as unsupported DB versions may cause further problems with future updates.

Could you post the output of the commands above after the fix, so others can confirm it works?

Regards
Tessa
 
Back
Top