-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I use a local MySQL server (we're using 4.0) for development. It's been
running cleanly for months - and the configuration file has not changed.
This morning we had a major power problem causing the machine to come
down in an unorderly manner. I can
That happens sometimes. Do a mysqladmin shutdown and then try to restart it.
It should start just fine.
--ja
On Wed, 8 Feb 2006, Michael Satterwhite wrote:
I use a local MySQL server (we're using 4.0) for development. It's been
running cleanly for months - and the configuration file has
see if there is a /tmp/mysql.sock file, is there a mysqld process
running (#ps -ef), also you could use #netstat -a to see if there is a
process utilizing port 3306, also has there been any file corruption due to
the outage ( #fsck), does the rest of the machine work well as expected, try
a reboot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| That happens sometimes. Do a mysqladmin shutdown and then try to
restart it. It should start just fine.
|
I ran mysqladmin shutdown which reported that it couldn't connect to the
mysql server (not surprising - the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kishore Jalleda wrote:
We're at least thinking in the same terms.
| see if there is a /tmp/mysql.sock file,
Doesn't exist.
| is there a mysqld process running (#ps -ef),
This was the first thing I checked. No, no mysqld running
also you could
do you have a bind-address = ip-addr option set in your my.cnf file,
also do you have a properly configures loopback address/addresses,
what OS are you running ,
if possible do a system call trace for mysqld_safe with #strace or
#truss, that might give some hint,
also just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kishore Jalleda wrote:
| do you have a bind-address = ip-addr option set in your my.cnf file,
You're a genius! Thanks much.
It was, indeed, a bind problem. I'm now back. You have no idea how much
I appreciate the help. Thanks again.
-BEGIN
