On Debian 5 32bit if you have set mysql_inst=yes in the options file of custombuild instead of downloading mysql-5.0.90-linux-i686.tar.gz it downloads mysql-5.0.90-linux-x86_64.tar.gz causing the mysql server to stop working.
If you have the same problem, to restart mysql do the following:
cd /usr/local
rm mysql (to remove the symbolic link)
Check your previous version doing ls -la. In our case it was mysql-5.0.89-linux-i686, so:
cd /usr/local
ln -s /usr/local/mysql-5.0.89-linux-i686 /usr/local/mysql
rm -r -f mysql-5.0.90-linux-x86_64
rm mysql-5.0.90-linux-x86_64.tar.gz
Then change the settings of custombuild
cd /usr/local/directadmin/custombuild
pico option*
mysql_inst=no
and CTRL+O to save CTRL+x to exit
./build update
./build update_data
./build update_versions
./build php n
and finally restart.
Anyway I don't understand why it downloads the wrong file. We have 12 servers and all had the same problem. If you have any clues please let me know.
If you have the same problem, to restart mysql do the following:
cd /usr/local
rm mysql (to remove the symbolic link)
Check your previous version doing ls -la. In our case it was mysql-5.0.89-linux-i686, so:
cd /usr/local
ln -s /usr/local/mysql-5.0.89-linux-i686 /usr/local/mysql
rm -r -f mysql-5.0.90-linux-x86_64
rm mysql-5.0.90-linux-x86_64.tar.gz
Then change the settings of custombuild
cd /usr/local/directadmin/custombuild
pico option*
mysql_inst=no
and CTRL+O to save CTRL+x to exit
./build update
./build update_data
./build update_versions
./build php n
and finally restart.
Anyway I don't understand why it downloads the wrong file. We have 12 servers and all had the same problem. If you have any clues please let me know.