Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when creating new user on MariaDB 5.5.53 #12757

Closed
vr0 opened this issue Nov 29, 2016 · 8 comments
Closed

Error when creating new user on MariaDB 5.5.53 #12757

vr0 opened this issue Nov 29, 2016 · 8 comments
Assignees
Labels
bug
Milestone

Comments

@vr0
Copy link

@vr0 vr0 commented Nov 29, 2016

Hello,

When trying to create a new user (User accounts -> Add user account) I get the following errors

SHOW PLUGINS SONAME LIKE '%_password_check%'
MySQL said: 1064
You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'SONAME LIKE '%_password_check%'' at line 1.

phpMyAdmin/libraries/server_privileges.lib.php generate this error because SHOW PLUGINS SONAME was introduced in MariaDB 10.0.2

function PMA_checkIfMariaDBPwdCheckPluginActive()
{
if (Util::getServerType() !== 'MariaDB') {
return false;
}

$result = $GLOBALS['dbi']->query(
    'SHOW PLUGINS SONAME LIKE \'%_password_check%\''
);
           
while ($row = $GLOBALS['dbi']->fetchAssoc($result)) {
    if ($row['Status'] === 'ACTIVE') {
        return true;
    }
}    
 
return false;

}

If i change

if (Util::getServerType() !== 'MariaDB') {

to

if (Util::getServerType() !== '5.5.53-MariaDB') {

they query is executed fine and create a new user account.

Server configuration

Operating system: FreeBSD 11.0-RELEASE-p3
Web server: Apache 2.4.23
Database: 5.5.53-MariaDB - FreeBSD Ports
PHP version: 7.0.13
phpMyAdmin version: 4.6.5.1

@nijel nijel added the bug label Nov 30, 2016
lucer pushed a commit to lucer/phpmyadmin that referenced this issue Dec 2, 2016
…or mysql password check plugin

Signed-off-by: Michael Zarubin <mzarubin@gmail.com>
@nijel nijel self-assigned this Dec 3, 2016
@nijel nijel closed this in eeb016b Dec 3, 2016
nijel added a commit that referenced this issue Dec 3, 2016
Signed-off-by: Michal Čihař <michal@cihar.com>
@Steve3100

This comment has been minimized.

Copy link

@Steve3100 Steve3100 commented Dec 30, 2016

I have the same problem. You can you can manually add a new user using the query:
CREATE USER 'user@localhost' IDENTIFIED BY 'password'
If that doesn't work use this query:
CREATE USER 'user@localhost' IDENTIFIED BY ''
Then go to user accounts and change the new users password.
Once the user is created you can link them to the database.

@Blackn0va

This comment has been minimized.

Copy link

@Blackn0va Blackn0va commented Jan 1, 2017

Hi,

The issue isnt repaired. What Can i do to fix this?

@nijel

This comment has been minimized.

Copy link
Member

@nijel nijel commented Jan 2, 2017

The issue is fixed in git for 4.6.6 release. You can also apply eeb016b manually to fix it for you.

@GokulSrinivas

This comment has been minimized.

Copy link

@GokulSrinivas GokulSrinivas commented Jan 18, 2017

This worked! Thanks 👍

@SBA18

This comment has been minimized.

Copy link

@SBA18 SBA18 commented Jan 28, 2017

Hi,

I have the same problem with phpmyadmin 4.6.6 and the manually fix is the same.

@cimba007

This comment has been minimized.

Copy link

@cimba007 cimba007 commented Mar 17, 2017

Well .. seems the fix is not working. I just downloaded XAMPP v5.6.30 .. and replaced the phpmyadmin with 4.6.6 (https://www.phpmyadmin.net/) .. same error.

Same problem on 4.7.0-rc1

This fixed the issue for me: http://stackoverflow.com/a/42078087

@nijel nijel removed their assignment Mar 20, 2017
@nijel nijel reopened this Mar 20, 2017
@nijel

This comment has been minimized.

Copy link
Member

@nijel nijel commented Mar 20, 2017

Creating the folder in the XAMPP did fix the issue? I think you should then rather report this to them than here...

@cimba007

This comment has been minimized.

Copy link

@cimba007 cimba007 commented Mar 20, 2017

Jep, finally creating the folder fixed the issue .. thought it might still be usefull if someone get to this issue and finds a solution ;_)

@nijel nijel self-assigned this Mar 21, 2017
@nijel nijel closed this in 2e448d4 Mar 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.