Error creating the database using MySQL Management
- Thread starter Dudik
- Start date
SeLLeRoNe
Super Moderator
The problem is that i wanna try to make you delete the mysql database which is the one that store all the user/pass for access mysql, that means that once removed none of the website would work untill we reinstall mysql and reimport all the mysql related stuff from da backups.
And it's quite risking to do that via forum, i'm leaving the office in 20 minutes and i'll hardly be available after, so maybe we should think about do that tomorrow and check if someone else add some ideas to fix the issue?
Regards
And it's quite risking to do that via forum, i'm leaving the office in 20 minutes and i'll hardly be available after, so maybe we should think about do that tomorrow and check if someone else add some ideas to fix the issue?
Regards
SeLLeRoNe
Super Moderator
Ok cool, i was going to do the same but since you did there is no reason for me to 
Best regards
Best regards
DA Support told me to check /etc/my.cnf
There was some code:
[mysqld]
local-infile=0
innodb_file_per_table
When I delete it and save, the file changed to my.cnf~ and new my.cnf (clean) become.
When I login the phpmyadmin with root, there is error:
" The phpMyAdmin configuration storage is not completely configured, some extended features have been deactivated. Find out why.
Or alternately go to 'Operations' tab of any database to set it up there."
There was some code:
[mysqld]
local-infile=0
innodb_file_per_table
When I delete it and save, the file changed to my.cnf~ and new my.cnf (clean) become.
When I login the phpmyadmin with root, there is error:
" The phpMyAdmin configuration storage is not completely configured, some extended features have been deactivated. Find out why.
Or alternately go to 'Operations' tab of any database to set it up there."
kaufenpreis
Verified User
- Joined
- Aug 24, 2014
- Messages
- 40
I just encountered these precise symptoms when upgrading from 5.5 to 5.6, and it turned out to be a service reachability issue.
Even though the cli MySQL client could connect to my local DB instance with only a -u and -p provided, I also needed to specify -h 127.0.0.1 for mysql_upgrade as it was attempting a socket file connection and failing miserably in the attempt.
Even though the cli MySQL client could connect to my local DB instance with only a -u and -p provided, I also needed to specify -h 127.0.0.1 for mysql_upgrade as it was attempting a socket file connection and failing miserably in the attempt.
Last edited: