Support

Hello, I'm posting this to give a hint on the problem showed up on the tickets https://www.akeeba.com/support/site-restoration/37003-restoring-database-access-denied-you-need-at-least-one-of-the-super-privilege-s-for-this-operation-1.html and https://www.akeeba.com/support/site-restoration/36772-restoring-database-access-denied-you-need-at-least-one-of-the-super-privilege-s-for-this-operation.html

I hope these infos can help you in debugging since I've already solved changing the PHP version:
the issue was happening when the selected PHP version was 8.1.3; switching back to 8.0.16 I was able to restore the database.

This was the environment as you requested in the previous ticket:
Mysql driver: Mysqli
DB server: Percona Server 5.7.32-35-log - Percona Server (GPL), Release 35, Revision 5688520
PHP: 8.1.3
Provider: Aruba, italian shared hosting company (imposed by the client)

I don't know at which point of restoration the error occurred since I don't have access to db logs, but it seems was happening at connection (no percentage of restoration was reached, and the error was quite immediate).

I hope this helps,
regards.

Hello Nicholas,

This host doesn't provide access to db user management, anyways the users have full privileges on their databases, in fact there's no issue in restoring the db UNLESS on PHP 8.1.

Don't you think there should be something related to the PHP version, since with PHP < 8.1 your restoring script works again fine, without touching the db and user priveleges of course?

Reporting you this just for your knowledge, if it can be useful for your debug or for other users, since as I stated I (like the user of the 25/4 ticket) already restored the db lowering the PHP version.

Regards.

The restoration script version is 7.3.1, I am aware is outdatet,
The actual situation is that I am installing for a client a joomla template quickstart package bought on themeforest, including Angie. So I am not using updated versions of softwares, but what it comes with the template installation bundle that I cannot change.

I am happy you have already solved this in next versions, I just thought my test scenario could have been useful for your investigation, and as a reference for future users that may encounter this error in these particular situations. For me the ticket can be closed.

Regards.