The server was brought yesterday from scratch, because I thought there was a problem in the configuration. I am running CentOS 5.5 64, and DirectAdmin. Ideas to solve this problem, I have already gone: (
netix, please read the quick reference guide before installing, it'll save you a lot of aggro. The guide explicitly states that if you have a web hosting CP like DirectAdmin (or CPanel, Plesk, etc.) that you should not run the command you ran. In fact, it says this in big bold letters so that you won't miss it, and it's the very first paragraph under "Quick Installation".
Oh man??? WTF? Why would you force us to use your mysql server install... screw pre-built stacks this sucks we dont want to have to wait for your company to make updates justy to get mysql updated to the latest security patches... why would you go and screw with what is already a great rpm management system?
SwiftLayer, you do realize that you're responding to someone who does not represent Centova Technologies, right? And that they're wrong?
We do not provide a MySQL installation with Centova Cast. That's just silly.
Centova Cast's installer can OPTIONALLY run the commands to install the MySQL server packages (and a bunch of other standard packages) from the Debian/Red Hat/CentOS repositories as a convenience for you during the installation process. These come straight from the Debian/RHEL/CentOS repositories using apt-get or yum, and have nothing to do with us.
The problem is that CPanel/Plesk/DirectAdmin provide their OWN MySQL server packages that do NOT come from the official repositories. So if you tell Centova Cast to install MySQL from the official repos for you, the official MySQL package is going to conflict with your CPanel/Plesk/DirectAdmin MySQL package.
The quickref guide does clearly explain this and also gives you instructions for installing without clobbering your existing MySQL server.