MySQL-phpmyadmin help: "access denied for user root"
 

Fresh Debian install with Apache, MySQL, PhP, Perl and Python.

I can get into MySql manually, but anytime I try to import a database I get and error 1044 saying "Access denied for user root @ localhost" for information_schema.

I looked trough numerous posts and arguments on numerous boards, but I'm not finding a solution.

The thing is, I don't understand what causes this. I don't ever recall having it before, or I might have some memory of how to fix it.

The other problem is that I don't even have clue as to how to troubleshoot this. Can anyone point me to a troubleshooting tree or condition table that will allow me to track this error down? It must come from somewhere!

I am able to add databases, both through the mysql cli and phpmyadmin. I can apparently add tables and data to these databases, both ways.

However, I cannot seem to restore a database that was stored in a .sql file.

If we can get a list of verification steps or a troubleshooting tree or a decision table, I will post it somewhere where we will all be able to get to it.

Mike

More info
 

I'm sure to be asked if I actually set the password, granted the privileges, etc., etc... The answer is yes, I'm pretty sure I did all that. The interesting thing is that phpmyadmin shows that I have full privileges on the information_schema database.

So, one question worth answering is, "Why does having no access to the information_schema database prevent me from importing the database?

The import file is named, localhost.sql and the tech exported it from phpmyadmin on the original webhosting system.
I built a new (local) server so we could have root access and develop new goodies for the website. I have just verified again that I can add databases, create tables and add data to the tables manually.

I just created a small test website and can load data from a login screen and a data screen, BUT, I can't export that data and reload it from a .sql file.

Thank you for your help.

Did you create EVENT in INFORMATION_SCHEMA?

But what I found in some other forums, it seems to be a bug.