MySQL Server 5.1.30 has been released

the phpmyadmin error means you need to rebuild php and specifically set the configure flags to point to the mysql 5.1 library files then that will be fixed.
 
Edit options.conf and set mysql=5.1, mysql_inst=yes. Save the file and run "./build mysql".
 
Got an error: can't connect to /var/lib/mysql/mysql.sock , searched for mysql.sock but didn't find it, reinstalled mysql but still got the same error. Just downgraded it to 5.0.67, and it's workin' fine. Anyone else has the same problem?
 
Martynas is a great guy, and it doesn't surprise me that he did this for you.
 
suddenly, Mr Martinas (himself!!!) contacted me via ICQ and gave important advise "how-to", so all things are safe and running well.
That what I call - Good Support.
Thank you, sir :)

Yeah, he's a great guy. Do you mind letting us know what was wrong?
 
Same here, Look what I got:

Code:
root@qcweb:/usr/local/directadmin/custombuild# pico options.conf
root@qcweb:/usr/local/directadmin/custombuild# ./build update_versions
Updating MySQL.
Stopping mysqld ...
Stopping mysqld:                [ OK ]
Starting mysqld:                [ OK ]
Giving mysqld a few seconds to start up...
Looking for 'mysql' as: /usr/local/mysql/bin/mysql
Looking for 'mysqlcheck' as: /usr/local/mysql/bin/mysqlcheck
Running 'mysqlcheck'...
/usr/local/mysql/bin/mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) when trying to connect
FATAL ERROR: Upgrade failed
Restarting MySQL.
Stopping mysqld:                [ FAILED ]
Starting mysqld:                [ OK ]
It is recommended to do "./build php n" after MySQL update.
root@qcweb:/usr/local/directadmin/custombuild# mysql --version
mysql  Ver 14.14 Distrib 5.1.30, for pc-linux-gnu (i686) using readline 5.1
root@qcweb:/usr/local/directadmin/custombuild# /etc/init.d/mysqld start
Starting mysqld:                [ OK ]

MySQL seems to be installed but not working...
When I enter the command to start it, I get a OK but MySQLD is stopped...
I tried to ./build php n but I have the same problem.

Thanks
 
Hello,

For that error, the sock file is what we want to look at.

For FreeBSD/Debian, it will be /tmp/mysql.sock.
For all other OS's, it should be /var/lib/mysql/mysqld.sock

And since your error is referring to /var/run/mysqld/mysqld.sock.. which isn't one of those 2 paths, I would then assume that there is a my.cnf somewhere causing problems, changing the location.

1) make sure you don't have:
/etc/init.d/mysql

It should be:
/etc/init.d/mysqld

with a d at the end. If you have 2.. delete the one without the d.

If the "mysql" had booted mysql, it may have command line options telling mysqld to create the sock file somewhere else on the system.


2) check for /etc/my.cnf. If you have that, edit it.. check for any mysql.sock paths, and ensure they're all set to use /var/lib/mysql/mysqld.sock (or /tmp/mysql.sock).
Have no values set in there is fine, it will default to the correct place.


Anyway, once you've confirmed it's all good.. try
Code:
killall -9 mysqld mysqld_safe
/etc/init.d/mysqld start
and then give it another go.

Check to see where your sock actually lives
Code:
netstat -lnp |grep mysql
John
 
Just a few minutes ago I had the same problem with mysqlcheck and UPGRADE FAILED. All I had to do is rename (or remove) /etc/my.cnf to /etc/my_backup.cnf and it started again.
 
Back
Top