I just had the same problem.
- I Upgraded 6.0.1 to 7.0
- I had a lot of problem after that. So I decided to backup everything with the server-manager on a workstation. I use XOOPS. So I decided to use mysqldump to backup my database.
- I installed SME-7.0
- I backup /root directory of the new SME-7.0 to a temp directory. I include all the files even all the . files.
- Then I restored manually from the files in the tar file.
- I restored manually the /root directory, including the .files and I overwrote all the files. even the my.cnf (this was the problem). After that I was no more able to access mysql.
- I search the forum and I found this thread. In it there was somebody saying something about that file.
- I compared the my.cnf that was created with the new SME-7.0 with the one that server-manager backed-up.
- The encrypted passwords were different.
- I put back the my.cnf created with the new SME-7.0 to its original place in /root.
- Victory on the western front. I was now able to access mysql.
So definitively the my.cnf was the problem. - I didn't reboot yet... because of
#------------------------------------------------------------
# DO NOT MODIFY THIS FILE! It is updated automatically by the
# e-smith server and gateway software. Instead, modify the source
# template in the /etc/e-smith/templates directory. For more
# information, see
http://www.e-smith.org.
#
# copyright (C) 1999-2001 e-smith, inc.
#------------------------------------------------------------
I will send this reply, reboot, and see what will happen
Another funny thing I noticed is the size of my database for XOOPS. There is about 30KB difference between the one I did with mysqldump and the one server-manager did. My web page looks OK. Both backup of the database were done with about 10 minutes difference.
Micronator