http://bugzilla.novell.com/show_bug.cgi?id=496196 User drankinatty@suddenlinkmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=496196#c3 --- Comment #3 from David Rankin <drankinatty@suddenlinkmail.com> 2009-05-13 11:02:23 MDT --- Michal, A new mysql bug was introduced with the update to mysql-5.1.34-29.1. The update through buildservice breaks the mysql install by putting the mysql.sock and mysqld.pid in /var/run/mysql instead of /var/lib/mysql as normal. This occurs with the packages for 10.3. In addition to /etc/my.cnf, the init script in /usr/sbin/rcmysql is messed up as well. In /usr/sbin/rcmysql the variables setting the socket and pid dir are: basedir=/usr datadir=/var/lib/mysql mysql_daemon_user=mysql mysql_daemon_group=mysql pid_file=/var/run/mysql/mysqld.pid socket=/var/run/mysql/mysql.sock print_defaults=/usr/bin/my_print_defaults upgrade_log=/var/log/mysql_upgrade.log That's not right. The have always been: basedir=/usr datadir=/var/lib/mysql mysql_daemon_user=mysql mysql_daemon_group=mysql pid_file=/var/lib/mysql/mysqld.pid socket=/var/lib/mysql/mysql.sock print_defaults=/usr/bin/my_print_defaults After you make the needed changes to /etc/my.cnf and /usr/sbin/rcmysql and restart the server, mysql works properly again and your database apps work again. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.