Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

User could not be added to the database error

Discussion in 'Database Discussions' started by maestroc, Aug 11, 2017.

  1. maestroc

    maestroc Active Member

    Joined:
    Aug 23, 2012
    Messages:
    41
    Likes Received:
    0
    Trophy Points:
    6
    cPanel Access Level:
    Reseller Owner
    Recently I have ran into the problem on all of the accounts on my server when using WHM's MySQL Database Wizard to create a new database and user. The database and the user are created (I can see them in the list if I go back to the MySQL Databases screen), but in the final step of the wizard when it is time to assign permissions to that new user I get an error every time and on every account. The error message is

    User “xyz_pdq” could not be added to the database “xyz_pdq". (XID hu6cmw) The system received an error from the “MySQL” database “mysql”: ER_PASSWORD_NO_MATCH (Can't find any matching row in the user table)

    I found this posting on another forum that suggests a fix:

    linuxadminonline.com/issue-system-received-error-mysql-database-mysql-er_password_no_match-cant-find-matching-row-user-table/

    He says to comment out the skip-name-resolve variable in my.cnf

    but I don't want to turn that off in case it is important somehow. Any idea what I should do to fix this problem? As I said it happens server wide, even on newly created accounts.
     
    #1 maestroc, Aug 11, 2017
    Last edited by a moderator: Aug 11, 2017
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,165
    Likes Received:
    1,371
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    The use of this entry is unsupported. Could you remove the entry, and then restart MySQL, to verify it solves the issue?

    Thank you.
     
Loading...

Share This Page