Sounds? Yes, it did appear to sound good. Great for that matter, although we were unaware at the time of our last post that we had no control of new database driven site creation, until later.
Since we last posted, we've been using a test server (after first restoring our production server) to try to see what's up with this.
For those of you that may or might experience this problem and are using Plesk 7.5.4 - DO NOT USE
Code: Select all
/usr/bin/mysql_fix_privilege_tables --user=admin --password=`cat /etc/psa/.psa.shadow`
or you may find yourselves in the same fix of lost connections to current databases and/or the ability to create new database driven sites.
We tested this by using our 1and1 server re-image and then running yum update for php and mysql. When the SQL error showed up, we ran the mysql fix and found ourselves back in the same place.
We then re-imaged and manually upgraded the server using (ART) php and mysql via rpm and found no problems, again and until we ran the mysql_fix.
Once that command is run (with us anyway), we loose connection to current databases and also unable to create new database driven sites.
Up to this point we have manually rebuilt the server to php 4.4.0-3.rhfc2.art and mysql 4.1.12-1.rhfc2.art, and again have no problems other than the mysqld.log entry listed below. Our next step is to run a yum update to the latest ART to see if the problem still exists. Of course without running the fix.
Currently we are running three domains on the test server and the only error we are receiving is:
Code: Select all
051224 19:19:00 [Warning] mysql.user table is not updated to new password format; Disabling new password usage until mysql_fix_privilege_tables is run
No matter, we are having no problems with the server and/sites presently.
When going through these steps we tried it with and without using mod_security, firewalls or other security precautions.
We're still unsure whether it is a php and mysql problem or a 1and1 thing but we're determined to find out one way or another. Reflecting on a previous post on ART by Scott (not verbatim) -- don't blame SW-Soft....it's a xxxxx problem.
Thank you, Scott - you're not unappreciated, but most respected for your hard work and determination.