MYSQL PASSWORD ROOT ERROR

joniyoku

its correct password but i cannot logged in

aaPanel_Kern

Hello, what version of mysql are you using? If it is mysql, can I change the root password in the database interface and then use the new password to log in? Is it normal?

joniyoku

aaPanel_Kern mariadb 10.11

see even I can't delete/edit the existing database here

aaPanel_Kern

Hello, currently mariaDB does not support changing the password on the panel. It is recommended that you use the command line to manually reset the root password.

joniyoku

aaPanel_Kern i cannot logged to mysql server, how to change root password

aaPanel_Kern

stop:
/etc/init.d/mysqld stop

Password-free login
/www/server/mysql/bin/mysqld_safe --skip-grant-tables &
mysql -u root

change Password

use mysql;
update user set password=PASSWORD('new_password') where user='root';
flush privileges;
exit;

Stop and start:

/etc/init.d/mysqld stop
/etc/init.d/mysqld start

joniyoku

aaPanel_Kern

joniyoku
try
stop:
/etc/init.d/mysqld stop

Password-free login
/www/server/mysql/bin/mysqld_safe --skip-grant-tables &
mysql -u root

change Password

use mysql;
ALTER USER 'root'@'localhost' IDENTIFIED BY 'new_password';
flush privileges;
exit;

Stop and start:

/etc/init.d/mysqld stop
/etc/init.d/mysqld start

aaPanel_Kern

joniyoku
try
stop:
/etc/init.d/mysqld stop

Password-free login
/www/server/mysql/bin/mysqld_safe --skip-grant-tables &
mysql -u root

change Password

use mysql;
FLUSH PRIVILEGES;
ALTER USER 'root'@'localhost' IDENTIFIED BY 'new_password';
flush privileges;
exit;

Stop and start:

/etc/init.d/mysqld stop
/etc/init.d/mysqld start

joniyoku

aaPanel_Kern

Hello, this problem has been optimized. Can you please try the repaired version?

aaP_centrewebdesign

Hi. Sorry for posting on an old thread. Where is the up to date information about handling this issue?

I've installed an used aaPanel several times on various Debian based systems, Arch, etc. This is the first i've encountered this seemingly insurmountable error.

I too have followed your instructions here, and my own notes which are quite the same. The mysql_safe seems to not function as desired.