Trouble problem?is DA bug??

bobpang425

Verified User
Joined
Dec 4, 2006
Messages
8
Discuz! info: Can not connect to MySQL server

Time: 2006-12-2 6:26pm
Script: /index.php

Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (11)
Errno.: 2002


find the log

/var/lib/mysql/localhost.localdomain.err


061002 16:02:02 [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!
061002 16:02:02 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
061002 16:02:03 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...
061002 16:02:03 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
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
061002 16:02:03 InnoDB: Started; log sequence number 0 0
/usr/sbin/mysqld: ready for connections.
Version: '4.1.11-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
A mysqld process already exists at Mon Oct 2 16:02:08 HKT 2006
061002 17:53:28 [Note] /usr/sbin/mysqld: Normal shutdown

061002 17:53:28 InnoDB: Starting shutdown...
061002 17:53:31 InnoDB: Shutdown completed; log sequence number 0 43634
061002 17:53:31 [Note] /usr/sbin/mysqld: Shutdown complete

061002 17:53:31 mysqld ended

until now can't solve the problem @.@
i found many and many times to in GOOGLE..@[email protected]' t solve the problem ? anyone can help me ?i just reboot and then one day ..happy again @.@THX
 
In SSH try typing "service mysqld stop" then "ps ax" and see if you can find any mysqld processes running in its output. If you see any, look at its process id and input "kill (proccess id)" for each one to kill any remaining mysqld processes then type "service mysqld start" and see if that fixes it.
 
Marshall said:
In SSH try typing "service mysqld stop" then "ps ax" and see if you can find any mysqld processes running in its output. If you see any, look at its process id and input "kill (proccess id)" for each one to kill any remaining mysqld processes then type "service mysqld start" and see if that fixes it.

i tried this way before.the mysqld is ok now .
however, later , this problem will happy again ,
any way to solve this problem forever??
thanks for your reply !!
 
Hm not sure why it would keep happening, are you running the latest version? Have you tried re-installing MySQL to see if that would fix it? have you made any adjustments to the config files?

edit - just saw version in your original post, might want to try upgrading to 4.1.22 as there are probably security fixes between 4.1.11 and 4.1.22 and it may fix your problem.
 
Last edited:
Marshall said:
Hm not sure why it would keep happening, are you running the latest version? Have you tried re-installing MySQL to see if that would fix it? have you made any adjustments to the config files?

edit - just saw version in your original post, might want to try upgrading to 4.1.22 as there are probably security fixes between 4.1.11 and 4.1.22 and it may fix your problem.

how to update??
after search the following step updates?
after update, my database will lost??
updates all softwares not just mySQL?

cd /usr/local/directadmin/customapache
./build clean
rm -f configure.*
./build update
./build all
 
You have two ways, you can go to http://www.directadmin.com/forum/showthread.php?s=&threadid=12099 and download his updater script to update MySQL and then rebuild php afterwards

or

Go to the MySQL website and look for your systems OS under their downloads for the 4.1 tree and download the RPM files to your server then run
Code:
rpm -Uvh MySQL*
in their directory. Afterwards you should rebuild your php using the customapache script so that everything is up to date.

I must warn you though, there is a chance something can go wrong during the upgrade so if you arent confident with your level of linux skills, you may want to hire an outside management company to help you out/do it for you.
 
Marshall said:
You have two ways, you can go to http://www.directadmin.com/forum/showthread.php?s=&threadid=12099 and download his updater script to update MySQL and then rebuild php afterwards

or

Go to the MySQL website and look for your systems OS under their downloads for the 4.1 tree and download the RPM files to your server then run
Code:
rpm -Uvh MySQL*
in their directory. Afterwards you should rebuild your php using the customapache script so that everything is up to date.

I must warn you though, there is a chance something can go wrong during the upgrade so if you arent confident with your level of linux skills, you may want to hire an outside management company to help you out/do it for you.

thanks !!you are nice and helpful .
but which ways is more safe?
and update MYSQL to new one , will lost the database data ???
thankS!!!
 
Back
Top