-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Magento 2 1.0.0-beta Merchant Beta1 - Webinstaller / Console Installer - Error "Database user does not have enough privileges" #1813
Comments
This way has always worked for me: |
The problem is on the joker % . On your exemple you specify a database name with GRANT ALL, in development context all databases are named like synbshop_mydatabasename. This type of syntax worked on the magento2-0740beta9 version, what do you suggest ? |
After quick test on magento2-0740beta16, this type of syntax also worked. I have compared the file DbValidatorTest.php (in setup/src/Magento/Setup/Test/Unit/Validator) in magento2-0740beta16 and magento2-merchant1, it seems the function testCheckDatabaseConnectionNotEnoughPrivileges only exist in merchant1 version and the function testCheckDatabaseConnection has been modified with GRANT checks. Also there are GRANT checks in the file DbValidator.php (in setup/src/Magento/Setup/Validator) since the magento2-merchant1 version. |
@magentofaz thank you for the details, we have created MAGETWO-42678 to track this fix internally. |
I confirm this is not fixed yet. I did clear installation from git as is described in the manual. I did create new magento user and database through phpmyadmin by creating user, and clicking the checkbox "create database with the same name" .. it grants all permissions to database for this user, but does not grant it any global permissions. After granting some global permissions the installation moved on, however i clicked ctrl-c in process and it did not create database structure correctly, and now it fails.. now i have to find out how to clear cache or something.. php magento --version shows only "Magento CLI version 1.0.0-beta" not version of magento installed, but these are currently installed packages by composer (you can consider not showing a magento version through console as suggestion for improvement) braintree/braintree_php 2.39.0 Braintree PHP Client Library |
@scholtz thank you for your report. We are still working on this ticket. |
@magentofaz and @scholtz this has been fixed in 2.0.0 Please have a look and create a new issue if necessary. |
[Pangolin] Deliver changes from Sprint 14 - MQE-528: Robo commands should override certain files. - MQE-382: Adding custom "assertElementContainsAttribute" method. - MQE-572: Expose selenium configuration from within our .env file - MQE-513: added attachment (screenshots/logs) support in Allure reporting. - MQE-439: .env.example parameter example comment block - MQE-569: added SampleTests in module blacklist and not allowed to generate them. - MQE-570: Sanitize MAGENTO_BASE_URL (.env file) and Selenium params - MQE-541: Rename mergeKey - MQE-574: Test schema should specify required attributes correctly - MQE-347: Use a remove tag instead of a remove attribute - MQE-386: Ignore _generated folder for mftf code sniffer - MQE-592: Audit Test Cases on Firefox/Chrome on Windows/OSX - MQE-599: Move composer.json, README, etc from EE to CE - MQE-583: set release version to 1.0.0 and updated composer dependencies.
Hi @magentofaz. Thank you for your report.
The fix will be available with the upcoming 2.4.2 release. |
Since the Magento 2 1.0.0-beta, the webinstaller and "console installer" doesn't work anymore at the step adddatabase, I always have the message "Database user does not have enough privileges.". Since previous beta/alpha versions of Magento 2 we use GRANT ALL PRIVILEGES ON
synbshop\_%
.* TO 'synbshop'@'localhost' WITH GRANT OPTION, and now the % is not interpreted. So to bypass this we need to put each database in the GRANT (for exemple GRANT ALL PRIVILEGES ONsynbshop_faz_magento2merchant1
.* TO 'synbshop'@'localhost' WITH GRANT OPTION). Our MySql version is 5.6.23-72.1.Can you fix it ? or find a workaround ?
The text was updated successfully, but these errors were encountered: