Stop the process you currently have or start up the server on a port other
than 3306.
-----Original Message-----
From: Kevin H. Phillips [mailto:kh-phillips@stripped]
Sent: Tuesday, June 24, 2003 1:46 PM
Cc: mysql@stripped
Subject: Re: mysql.sock doesn't exist
The output of the grep is:
[root@mail root]# ps -ax | grep mysqld
4578 ? S 0:00 /bin/sh /usr/bin/mysqld_safe
--defaults-file=/etc/my.cnf
4601 ? S 0:01 /usr/libexec/mysqld
--defaults-file=/etc/my.cnf --basedir=/usr --datadir=/var/lib/mysql
--user=mysql --pid-file=/var/lib/mysql/mail.9-5usa.org.pid --skip-locking
10785 pts/0 S 0:00 grep mysqld
The /var/log/boot.log files shows this for the last few entries:
un 24 13:27:15 mail mysqld: Stopping MySQL: failed
Jun 24 13:27:15 mail mysqld: Starting MySQL: succeeded
Jun 24 13:31:30 mail mysqld: Stopping MySQL: failed
Jun 24 13:31:30 mail mysqld: Starting MySQL: succeeded
The /var/log/mysqld.log files shows this (it hasn't registered anything
since yesterday so maybe it isn't logging???):
030623 11:16:53 mysqld ended
030623 11:17:06 mysqld started
030623 11:17:06 Can't start server: Bind on TCP/IP port: Address
already in use
030623 11:17:06 Do you already have another mysqld server running on
port: 3306 ?
030623 11:17:06 Aborting
030623 11:17:06 /usr/libexec/mysqld: Shutdown Complete
030623 11:17:06 mysqld ended
It seems I'm locked out of doing anything at all with it.
Kevin
John Nichel wrote:
> If you get a failed when the script is stopping the server, it's more
> than likely that the server is dying right after it's started. When you
> think it's running do a....
>
> ps -ax | grep mysqld
>
> If that doesn't return anything (or it only returns the grep), then the
> server isn't running. Check your logs to see why it's dying.
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=1
