August 13th, 2000, 02:10 PM
Im running into an interesting problem, I am installing mysql-3.22.32.tar.gz on redhat 6.2
My install goes fine, all the way to where i need to run "./safe_mysqld &" this command does not work properly as the server daemon dies right after the command. I check the log file and it tells me that the port is already in use and asks if there is another mysql server running. I don't believe there is another server running so i'm trying to figure out one, how do I find out what ports are currently being used, and what other ports can i install mysql on? I have a sneaky feeling that problem is related to having postgesSQL on the same box, but i can't seem to figure out how to install or reconfigure that either...
Any help would be greatly appreicated.
August 14th, 2000, 01:18 AM
You say you don't believe there is another mySQL server running... why not check it out? Use the command 'top' in a terminal and see if there is an instance of mysql running. RedHat has come with mysql as an install option for years, so it wouldn't surprise me if you do have a slightly older version of mysql running. (Especially if you chose the 'everything' install) If so, that would explain the port use. I don't think there are any "standard" unix daemons that use that port by default.
August 28th, 2000, 10:49 AM
if its an install problem, then
1. login as root, or use "su"
2. ftp to ftp.mysql.com username=anonymous password=(your email address)
3. change directory to MySQL-3.22 (note, it is case sensitive)
4. get MySQL-client-3.22.32-1.i386.rpm (note, it is case sensitive)
5.exit from ftp with "bye"
6. go to http://www.mysql.com/documentation/m...tion=Linux-RPM
7.follow the instructions step by step.
8. DO NOT RESTART mysqld until you are sure it will restart, this happened to me, and i had to spend quite a while getting it back up.
this will save you alot of trouble, it is much, much, harder to do a correct tar.gz installation than to do an RPM installation
August 28th, 2000, 10:53 AM
its not a problem with ports, im not exactly sure what it is, maybe safe_mysqld has low self esteem or something...