CustomerCentrix

From version 3.23 to 4.0, this installation is reputed to cause some difficulties with Plesk. Not having done much with Linux, I waited until we had a new server that would be easy to restore if necessary and not affect any needed sites or applications. Found and copied these files to the server:

MySQL-shared-compat-4.0.26-0.i386.rpm
MySQL-server-4.0.26-0.i386.rpm

The first was necessary because of a dependency issue with shared libs. Ran RPM -U with these and got a warning (MySQL-server-4.0.26-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5) but otherwise seemed to work ok. Plesk still works until I tried restarting and now gives this error without even showing the login screen:

ERROR: Unable to connect to database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) 0: /usr/local/psa/admin/auto_prepend/auth.php3:81 psaerror(string "Unable to connect to database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)")

The grant tables script did not work, although I suspect that I might have done something wrong and will have to come back to this. I searched Plesk and found this page with some instructions. This gives an error similar to that above:

2005-09-12 23:15:10.490 ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)

The next day we still aren't quite sure how to make this work. It is always best, although not always possible, to plan as we did for not needing the machine for a few days when doing something like this. We have needs for this machine (or we wouldn't have signed up for it) but nothing that is immediate. Restoring the machine is a last resort since it doesn't solve our need of MySQL 4.0 with Plesk.

It seems that ignoring Plesk for now is the right thing to do, since I don't think that MySQL is working. So, get MySQL to work and (possibly) Plesk will work too. Some possibly relevant files and paths with some of their contents:

/etc/rs.d/init.d/mysql (startup script)
/etc/my.cnf (mysql configuration)
  [mysqld]
  safe-show-database
  innodb_data_file_path=ibdata1:10M:autoextend
  datadir=/var/lib/mysql
  socket=/var/lib/mysql/mysql.sock
  skip-networking
  [mysql.server]
  user=mysql
  basedir=/var/lib
  [safe_mysqld]
  err-log=/var/log/mysqld.log
  pid-file=/var/run/mysqld/mysqld.pid
/var/log/mysqld.log (error log)
  050913 15:32:56 mysqld started
  Fatal error: Can't change to run   as user 'mysql'. Please check that the user exists!
  050913 15:32:56 Aborting
  050913 15:32:56 /usr/sbin/mysqld: Shutdown Complete
  050913 15:32:56 mysqld ended

At least the error log helps to narrow things down. It seems that something in the upgrade removes the mysql user. I added the user back to the /etc/passwd and /etc/group files from the passwd- and group- (backup) files. Now all seems to be working. Relief!

Not too sure at this point about configuration or features, but Plesk works including adding databases and users. phpMyAdmin also works allowing me to add tables, so basic db functionality is back.