Welcome Guest. Please Login or Register  


You are here: Index > Webuzo > General Support > Topic : After Mysql upgrade to 5.6, unable to create new databases



Threaded Mode | Print  

 After Mysql upgrade to 5.6, unable to create new databases (7 Replies, Read 42068 times)
nychos
Group: Member
Post Group: Newbie
Posts: 10
Status:
Hello,

as said in the title i can not create new database after the upgrade, i suspect because the phpmyadmin root password changed but webuzo did not update the file my.conf accordingly.

How can I solve?

thanks
IP: --   

After Mysql upgrade to 5.6, unable to create new databases
Guest
Group: Guest
Status:
Hi,
what is the issue? What is the error? Are you able to see your database list on manage database or what you see, all blank and empty?
IP: --   

After Mysql upgrade to 5.6, unable to create new databases
nychos
Group: Member
Post Group: Newbie
Posts: 10
Status:
Hi,
the database list is empty and i can not create new ones

on the other hand every website work as usual and I can access to already existing databases with the relative username/password

only the webuzo panel database list is empty, I think is the root password not set correctly
IP: --   

After Mysql upgrade to 5.6, unable to create new databases
webuzo_manager
Group: Member
Post Group: Elite Member
Posts: 268
Status:
Hi,

If you facing this issue please follow these steps to change your MySQL root password :

1. Firstly Stop MySQL service, use this command and execute it multiple times untill no mysqld process is running :

service mysqld stop

2. Start MySQL with option:

/usr/local/apps/mysql56/mysqld  --skip-grant-tables

3. Login to MySQL as:

mysql -u root

4. Change database to mysql as:

use mysql;

5. Update root user password as:

update user set password=PASSWORD("NEWPASSWORD ") where user='root';

note: NEWPASSWORD should be replaced with desired password, everything else stays the same...

5.5 Flush the privileges using the following command :

flush privileges;

6. Exit from mysql, using the command:

exit;

7. Stop all MySQL service as (execute it multiple times until no process is present):

killall mysqld

8. Start MySQL service normally as:

service mysqld restart

9. Check whether new password is working fine by loging in as:

mysql -u root -p

note: After this MySQL will prompt you for password. Please enter the NEWPASSWORD set by you above.

10. Update /var/webuzo/my.conf with the new working password.
IP: --   

After Mysql upgrade to 5.6, unable to create new databases
nychos
Group: Member
Post Group: Newbie
Posts: 10
Status:
Thank you nikhil,
unfortunately the console returns a lot of errors like this

2016-06-20 10:56:05 7f36af5fe700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2016-06-20 10:56:05 7f36af5fe700 InnoDB: Recalculation of persistent statistics requested for table "geat_db"."cache" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.

and I can't enter any more commands

there is a way to skip this error check?
IP: --   

After Mysql upgrade to 5.6, unable to create new databases
webuzo_manager
Group: Member
Post Group: Elite Member
Posts: 268
Status:
Quote
2. Start MySQL with option:

/usr/local/apps/mysql56/mysqld  --skip-grant-tables


After executing this command open a new putty or console window and execute the remaining steps till step 7 then close console window in which the skip grant command was executed and continue with remaining steps.

You can ignore the errors which are thrown by the mysqld daemon
IP: --   

After Mysql upgrade to 5.6, unable to create new databases
nychos
Group: Member
Post Group: Newbie
Posts: 10
Status:
THANKS! It worked!

Now, about all that errors, is it something I should worry about? I think they are caused by the upgrade to 5.6
IP: --   

After Mysql upgrade to 5.6, unable to create new databases
webuzo_manager
Group: Member
Post Group: Elite Member
Posts: 268
Status:
Glad to know the steps worked. :)

This shouldn't be the case, the upgrade should be seamless , we will try to replicate the issue on our test server and launch a fix if we find any bugs.
IP: --   

« Previous    Next »

Threaded Mode | Print  



Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is July 6, 2025, 7:55 am.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 10  |  Page Created In:0.038