MySQL-server won't start, port conflick

[KR-data]

Hi

I've tried to get my MySQL-server to work, but I got the problem that I can't start my server.

I'll make this one short and give you the console output, and the log, and then some simple questions:

Console output:
Starting mysqld daemon with databases from /usr/local/mysql/data
STOPPING server from pid file /usr/local/mysql/data/stine.pid
041121 22:26:24 mysqld ended

Log file:
041121 22:26:24 mysqld started
041121 22:26:24 [Warning] Asked for 196608 thread stack, but got 126976
041121 22:26:24 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
041121 22:26:24 [ERROR] Do you already have another mysqld server running on port: 3306 ?
041121 22:26:24 [ERROR] Aborting

041121 22:26:24 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

041121 22:26:24 mysqld ended





To me it seem like I have another server running at that port, how can I check if that is true?

Are there anyone, who have the solution to my problem (I know I know, close the server that uses the port, but I don't know which server), and how?

Sorry for my bad english, and thank you in advance.

Best regards
Rohde

[KR-data]

Now I made it work, some buggy version of MySQL preinstalled, I managed to stop it, and start my new installation, but still I won't work

I tried to connect to the MySQL through the console with the command 'mysql'

And I got this result
ERROR 2002: Can't connect to local MySQL server through socket '/var/run/mysql/mysql.sock' (2)


The log-file

041121 22:49:19 mysqld started
041121 22:49:19 [Warning] Asked for 196608 thread stack, but got 126976
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
041121 22:49:19 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
041121 22:49:19 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
041121 22:49:19 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new

I'll send you a log more in the next post, without the table things.

[cjl7]

Hi,

What distro are you running?

If you are running RedHat/Fedora install and start there server first then put your (later version) of mysql on and change the /etc/init.d/mysql to start you mysqld (normally under /usr/local/mysql/bin).

//jonas

[KR-data]

My problem is solved.

I found that the server was running corrrectly, but the /var/run/mysql/mysql.sock didn't exist, and after a while I found that it was created in /tmp/mysql.sock, so I simply made an symlink to the /tmp/mysq.sock

I'm running Slackware 10.0, thanks for trying to help, it's appreciated

Best regards
Rohde

Ps. do any of you know a good program to plan databases?

[cjl7]

Hi,

This might help you a bit, trying to "normalize" the database should be your goal.

http://www.samspublishing.com/articl...e.asp?p=102167

Normazising a database is done in several steps, but in short one could describe it as "only searching on numerical values, don't store string values in your search table."

The other tip I would give you is to use indexes and query_cache.

Good luck

Jonas

[wassy121]

Also, instead of making a link, there is a configuration value in /etc/my.cnf that you could change to let the client, as well as the server know that the mysql.sock file is in /tmp . Do a search for sockfile at mysql.com , they have _excellent_ documentation.

Best,

Samuel

[thebomani]

Hi

I've tried to get my MySQL-server to work, but I got the problem that I can't start my server.

I'll make this one short and give you the console output, and the log, and then some simple questions:

Console output:
Starting mysqld daemon with databases from /usr/local/mysql/data
STOPPING server from pid file /usr/local/mysql/data/stine.pid
041121 22:26:24 mysqld ended

Log file:
041121 22:26:24 mysqld started
041121 22:26:24 [Warning] Asked for 196608 thread stack, but got 126976
041121 22:26:24 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
041121 22:26:24 [ERROR] Do you already have another mysqld server running on port: 3306 ?
041121 22:26:24 [ERROR] Aborting

041121 22:26:24 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

041121 22:26:24 mysqld ended





To me it seem like I have another server running at that port, how can I check if that is true?

Are there anyone, who have the solution to my problem (I know I know, close the server that uses the port, but I don't know which server), and how?

Sorry for my bad english, and thank you in advance.

Best regards
Rohde

I had the same problem with Mysql 4.1.12 after recieving a SELinux update throught the RedHat Network. Editing /etc/selinux/config so the it says:

SELINUX=permissive


Fixed my problem.

[thebomani]

Hi

I've tried to get my MySQL-server to work, but I got the problem that I can't start my server.

I'll make this one short and give you the console output, and the log, and then some simple questions:

Console output:
Starting mysqld daemon with databases from /usr/local/mysql/data
STOPPING server from pid file /usr/local/mysql/data/stine.pid
041121 22:26:24 mysqld ended

Log file:
041121 22:26:24 mysqld started
041121 22:26:24 [Warning] Asked for 196608 thread stack, but got 126976
041121 22:26:24 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
041121 22:26:24 [ERROR] Do you already have another mysqld server running on port: 3306 ?
041121 22:26:24 [ERROR] Aborting

041121 22:26:24 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

041121 22:26:24 mysqld ended





To me it seem like I have another server running at that port, how can I check if that is true?

Are there anyone, who have the solution to my problem (I know I know, close the server that uses the port, but I don't know which server), and how?

Sorry for my bad english, and thank you in advance.

Best regards
Rohde

I had the same problem with Mysql 4.1.12 after recieving a SELinux update throught the RedHat Network. Editing /etc/selinux/config so the it says:

SELINUX=permissive


Fixed my problem.