MySQL Problem

itsit

New member
Joined
Sep 27, 2007
Messages
3
After I have edit my.cnf in the etc/ directory I restart mysql. But Mysql won't restart.


I have changed my hostname before.

This is the log file:
070928 00:03:25 mysqld started
070928 0:03:25 [Warning] Asked for 196608 thread stack, but got 126976
070928 0:03:25 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
070928 0:03:25 [ERROR] Do you already have another mysqld server running on port: 3306 ?
070928 0:03:25 [ERROR] Aborting

070928 0:03:25 [Note] /usr/sbin/mysqld: Shutdown complete

070928 00:03:25 mysqld ended

This is the server output (what I have done):
[root@server ~]# cd "/usr/local/lib"
[root@server lib]# /etc/rc.d/init.d/mysqld restart
MySQL PID file could not be found! [FAILED]
Starting MySQL................................... [FAILED]
[root@server lib]# /etc/rc.d/init.d/mysqld restart
MySQL PID file could not be found! [FAILED]
Starting MySQL.^[OA^[OD..........
[root@server lib]# /etc/rc.d/init.d/mysql start
-bash: /etc/rc.d/init.d/mysql: No such file or directory
[root@server lib]# /etc/rc.d/init.d/mysql start
-bash: /etc/rc.d/init.d/mysql: No such file or directory
[root@server lib]#
Broadcast message from root (Fri Sep 28 00:10:01 2007):

The system is going down for reboot NOW!

Error when I am going to my site that uses MySQL:
Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)

Deleting my.cnf didn't help
Rebooting the system didn't help me out too with the problem to start MySQL.
Please help me out.
 
Last edited:
Ok, first, check whether you have another process of mysql running in port 3306.

netstat -ano|grep :3306|grep LISTEN

It should return no result to you but if it does, that's mean something is listening to the port.

Now show me your /etc/my.cnf

cat /etc/my.cnf

That's all for now :)
 
The error PHPMyAdmin gives me:
#2002 - the server is not responding (or the local MySQL server's socket is not correctly configured

Now MySQL will start in my console (not in DA):
[root@server ~]# /etc/rc.d/init.d/mysqld restart
MySQL PID file could not be found! [FAILED]
is fixed in...
[root@server ~]# /etc/rc.d/init.d/mysqld start
Starting MySQL [ OK ]



[root@server ~]# netstat -ano|grep :3306|grep LISTEN
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN off (0.00/0/0)
[root@server ~]# cat /etc/my.cnf
# Example MySQL config file for very large systems.
#
# This is for a large system with memory of 1G-2G where the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /var/lib/mysql) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
#password = your_password
port = 3306
socket = /var/lib/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port = 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
key_buffer = 384M
max_allowed_packet = 1M
table_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 32M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin

# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 384M
#bdb_max_lock = 100000

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /var/lib/mysql/
#innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend
#innodb_log_group_home_dir = /var/lib/mysql/
#innodb_log_arch_dir = /var/lib/mysql/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 384M
#innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 100M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
 
Last edited:
so can you connect to mysql now?
Thanks, I can connect to mysql now and phpMyAdmin works fine again!

By the way, in DA I can only Start or Stop mysqld and not Restart/Reload. Is this normal?

Thanks for your help. It was a long night for me. ;)
 
Hello,

This is the key to the original problem:
I have changed my hostname before.
The problem is that the pid file that mysql uses includes the hostname of the server. So when the hostname is changed, the script can't find the old pid file, as it uses the new hostname in the path. When this happens, you have to do things manually to shut down mysql. Normally, this isn't a big deal as it doesn't affect the currently running mysql (until you want to shut it off).

Manual shutdown
Code:
killall mysqld
killall mysqld_safe
wait about 5 seconds, then do a forced shutodwn to make sure it's dead:
Code:
killall -9 mysqld
killall -9 mysqld_safe
and then start up mysqld normally.

John
 
Back
Top