Hello.
> and restarted MySQL with /etc/init.d/mysql start, I get the following: > > Starting MySQL database server: mysqld. > Checking for crashed MySQL tables in the background. > /usr/bin/mysqladmin: connect to server at 'localhost' failed > error: 'Access denied for user: '[EMAIL PROTECTED]' (Using password: > YES)' Is there something in MySQL error log? See: http://dev.mysql.com/doc/refman/5.0/en/error-access-denied.html http://dev.mysql.com/doc/mysql/en/Error_log.html Hal Vaughan wrote: > I'm using MySQL 4.0.24-10 on Debian Sarge (Linux, and the stable branch of > Debian, just to clarify). I had a setup of a program I've been working on > for several years that is on a RAID. I changed MySQL's data directory so it > will be on the same RAID and backed up, along with all my other data and > programs. Originally this was set up under a Debian-based distro that was > based on the testing and unstable branches of Debian. Before putting the > server into production, I wanted to change it to Debian Stable (Sarge) for > safety. (I'll sleep easier at night if it's on Sarge with regular security > updates than depending on unstable packages!) > > So I backed up all the data on the RAID, wiped the original boot/system > drive, > installed Debian Sarge, did an fsck on the RAID, found errors, wiped it out, > restored the original data, including the MySQL db files. When I installed > MySQL on the re-done system, it worked. When altered the line > in /etc/mysql/my.cnf from: > > datadir = /var/lib/mysql > > to: > > datadir = /thresh/tNet/db > > and restarted MySQL with /etc/init.d/mysql start, I get the following: > > Starting MySQL database server: mysqld. > Checking for crashed MySQL tables in the background. > /usr/bin/mysqladmin: connect to server at 'localhost' failed > error: 'Access denied for user: '[EMAIL PROTECTED]' (Using password: > YES)' > /usr/bin/mysqladmin: connect to server at 'localhost' failed > error: 'Access denied for user: '[EMAIL PROTECTED]' (Using password: > YES)' > > However, after I got this, I entered "mysql" and got a connection. The > databases and tables seemed intact. > > I checked, and it turned out that somewhere in the backup/restore process the > ownership of the files was changed. I went through and changed the ownership > of /thresh/tNet/db to mysql:mysql and changed the ownership > of /thresh/tNet/db/mysql to mysql:root. Basically, I changed the ownership > of the files in the new data directory to match what I found > in /var/lib/mysql, then I stopped and restarted MySQL. I still got the same > error messages. > > While MySQL is working, I don't want to do anything with it because I'm not > clear why debian-sys-maint needs access, as opposed to just the user mysql. > To test, I made sure all the files from the db directory on down were set for > all to read and write and all directories set for all to read, write, and > execute. That doesn't help. > > So what is wrong, what do I need to do, and why didn't I get this error when > using the same database directory before? > > Thanks for any help! > > Hal > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
