http://bugzilla.novell.com/show_bug.cgi?id=496196 User mhrusecky@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=496196#c1 Michal Hrusecky changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED Component|Maintenance |Update Problems Version|Final |Factory Product|openSUSE 11.0 |openSUSE 11.2 --- Comment #1 from Michal Hrusecky 2009-04-21 12:55:52 MDT --- Thank you for your report. I'll test upgrade from openSUSE 11.0 and I'll investigate all mentioned things more deeply, but in the meantime I wanted to provide you with some feedback asap. Problem you are experiencing is caused by option --skip-federated. It's most likely caused by 'skip-federated' written in your /etc/my.cnf It was written there by default in previous versions but it is no longer supported with 5.1 builds of MySQL. Your my.cnf file should have been replaced by updated config file unless you changed something by hand. So this is probably cause of your troubles. Log file location should be also set correctly by default configuration file. You can probably fix nearly everything easily by merging your configuration changes from /etc/my.cnf to /etc/my.cnf.rpmnew by hand and replaing /etc/my.cnf with /etc/my.cnf.rpmnew after that. As for socket file, I moved it away from /var/lib/mysql to make MySQL package more LSB compliant and it is also more intuitive to look for socket file in /var/run. But unfortunately I forgot to adjust settings of mysqldump. It can be easily fixed by adding socket = /var/run/mysql/mysql.sock into mysqldump section of my.cnf or by using command line option --socket=/var/run/mysql/mysql.sock I'll fix it in default my.cnf and I'll try to do something about the rest of reported issues after some more investigation. -- 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.

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 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.

http://bugzilla.novell.com/show_bug.cgi?id=496196 Michal Hrusecky changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |drankinatty@suddenlinkmail. | |com -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=496196 User drankinatty@suddenlinkmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=496196#c6 --- Comment #6 from David Rankin 2009-05-28 01:31:28 MDT --- The mysql packages are still screwed up. I just upgraded mysql on 10.3 and my webserver is now *dead*. The following packages were updated: Overall download size: 15.0 M. After the operation, 8.8 M will be freed. Continue? [yes/no]: yes Downloading package MyODBC-unixODBC-3.51.27r695-5.3.x86_64, 1.3 M (4.5 M unpacked) Downloading: MyODBC-unixODBC-3.51.27r695-5.3.x86_64.rpm * Downloading [100%] * Installing: MyODBC-unixODBC-3.51.27r695-5.3 [100%] Downloading package libmysqlclient16-5.1.34-29.1.x86_64, 684.2 K (1.5 M unpacked) Downloading: libmysqlclient16-5.1.34-29.1.x86_64.rpm * Downloading [100%] * Installing: libmysqlclient16-5.1.34-29.1 [100%] Downloading package libmysqlclient_r16-5.1.34-29.1.x86_64, 693.2 K (1.5 M unpacked) Downloading: libmysqlclient_r16-5.1.34-29.1.x86_64.rpm * Downloading [100%] * Installing: libmysqlclient_r16-5.1.34-29.1 [100%] Downloading package mysql-client-5.1.34-29.1.x86_64, 204.5 K (440.3 K unpacked) Downloading: mysql-client-5.1.34-29.1.x86_64.rpm * Downloading [100%] * Installing: mysql-client-5.1.34-29.1 [100%] Downloading package libmysqlclient-devel-5.1.34-29.1.x86_64, 199.1 K (754.4 K unpacked) Downloading: libmysqlclient-devel-5.1.34-29.1.x86_64.rpm * Downloading [100%] * Installing: libmysqlclient-devel-5.1.34-29.1 [100%] Downloading package mysql-5.1.34-29.1.x86_64, 12.0 M (27.7 M unpacked) Downloading: mysql-5.1.34-29.1.x86_64.rpm * Downloading [100%] * Installing: mysql-5.1.34-29.1 [100%] Trying to access my server, returns: "Couldn't connect to server" because the mysql access log for the server dies due to the messed up locations for the pid and sock files. It is still not fixed. Seems simple really, just build the packages again with the pid and sock configuration in /var/lib like they have always been. Thanks. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=496196 User mhrusecky@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=496196#c8 --- Comment #8 from Michal Hrusecky 2009-06-01 10:48:58 MDT --- Ok, I just updated spec file, so after MySQL will get rebuild, socket file will be back in old location (/var/lib) for older distributions (older then 11.2) so it will be able to coexist with packages expecting socket there. It will be in /var/run for factory and for non-suse packages. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=496196 User drankinatty@suddenlinkmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=496196#c10 --- Comment #10 from David Rankin 2009-06-25 13:16:04 MDT --- Michal, I'll go do a quick install and report back.. Thanks. --- Comment #11 from David Rankin 2009-06-25 13:16:05 MDT --- Michal, I'll go do a quick install and report back.. Thanks. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=496196 User drankinatty@suddenlinkmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=496196#c12 David Rankin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|drankinatty@suddenlinkmail. | |com | --- Comment #12 from David Rankin 2009-06-25 14:06:10 MDT --- [14:19 ecstasy:/home/david] # zypper up -t package -r database Downloading repository 'openSUSE BuildService - Database' metadata [done] Building repository 'openSUSE BuildService - Database' cache [done] Reading installed packages... The following packages are going to be upgraded: mysql-client mysql libmysqlclient16 libmysqlclient_r16 Overall download size: 10.7 M. After the operation, 2.1 M will be freed. Continue? [YES/no]: Downloading package libmysqlclient16-5.1.35-32.1.x86_64 (1/4), 490.0 K (1.4 M unpacked) Downloading: libmysqlclient16-5.1.35-32.1.x86_64.rpm [done (75.5 K/s)] Installing: libmysqlclient16-5.1.35-32.1 [done] Downloading package libmysqlclient_r16-5.1.35-32.1.x86_64 (2/4), 494.0 K (1.4 M unpacked) Downloading: libmysqlclient_r16-5.1.35-32.1.x86_64.rpm [done (94.8 K/s)] Installing: libmysqlclient_r16-5.1.35-32.1 [done] Downloading package mysql-client-5.1.35-32.1.x86_64 (3/4), 157.0 K (372.0 K unpacked) Downloading: mysql-client-5.1.35-32.1.x86_64.rpm [done (65.3 K/s)] Installing: mysql-client-5.1.35-32.1 [done] Downloading package mysql-5.1.35-32.1.x86_64 (4/4), 9.6 M (26.0 M unpacked) Downloading: mysql-5.1.35-32.1.x86_64.rpm [done (132.3 K/s)] Installing: mysql-5.1.35-32.1 [done] Seems to be an issue with the "rcmysql status" response: [14:29 ecstasy:/home/david] # rcmysql restart Restarting service MySQL Shutting down service MySQL done Starting service MySQL done [14:30 ecstasy:/home/david] # rcmysql status Checking for service MySQL: It isn't reporting that it is running for some reason?? Let's see: [14:31 ecstasy:/etc] # l /var/run/mysql/ total 12 -rw-rw---- 1 mysql mysql 6 2009-06-25 14:30 mysqld.pid [14:31 ecstasy:/etc] # l /var/lib/mysql | grep sock srwxrwxrwx 1 mysql mysql 0 2009-06-25 14:30 mysql.sock= pid is in /var/run/mysql/ .sock is in /var/lib/mysql/, seem to work fine that way. I can get to all the database driven apps without any problems. So that is fixed! OK, let's test 10.3: Current version: Server version: 5.0.67 SUSE MySQL RPM [14:39 providence/home/david] # l /var/lib/mysql/ total 20556 drwxr-xr-x 6 mysql mysql 4096 2009-06-25 14:39 ./ drwxr-xr-x 50 root root 4096 2009-06-25 02:33 ../ -rw-rw---- 1 mysql mysql 10485760 2009-06-25 14:18 ibdata1 -rw-rw---- 1 mysql mysql 5242880 2009-06-25 14:39 ib_logfile0 -rw-rw---- 1 mysql mysql 5242880 2009-06-25 14:17 ib_logfile1 drwx------ 2 mysql mysql 4096 2009-06-25 14:17 mysql/ -rw-rw---- 1 mysql mysql 2059 2009-06-25 14:39 mysqld.log -rw-rw---- 1 mysql mysql 6 2009-06-25 14:39 mysqld.pid srwxrwxrwx 1 mysql mysql 0 2009-06-25 14:39 mysql.sock= -rw-r--r-- 1 mysql mysql 6 2009-06-25 14:17 mysql_upgrade_info Prior to upgrade both .sock and .pid are in /var/lib/mysql/ Uh, Oh... Houston, we have a problem with 10.3: [14:41 providence/home/david] # zypper up -t package -r database Refreshing 'openSUSE BuildService - Database' * Cleaning repository 'openSUSE BuildService - Database' cache * Building repository 'openSUSE BuildService - Database' cache * Reading repository 'openSUSE BuildService - Database' cache * Reading installed packages [100%] The following packages are going to be upgraded: mysql-client mysql The following NEW packages are going to be installed: libmysqlclient16 libmysqlclient_r16 Overall download size: 12.7 M. After the operation, additional 4.9 M will be used. Continue? [yes/no]: yes Downloading package libmysqlclient16-5.1.35-32.1.i586, 637.7 K (1.3 M unpacked) Downloading: libmysqlclient16-5.1.35-32.1.i586.rpm * Downloading [100%] * Installing: libmysqlclient16-5.1.35-32.1 [100%] Downloading package libmysqlclient_r16-5.1.35-32.1.i586, 648.5 K (1.3 M unpacked) Downloading: libmysqlclient_r16-5.1.35-32.1.i586.rpm * Downloading [100%] * Installing: libmysqlclient_r16-5.1.35-32.1 [100%] Downloading package mysql-client-5.1.35-32.1.i586, 183.7 K (317.0 K unpacked) Downloading: mysql-client-5.1.35-32.1.i586.rpm * Downloading [100%] * Installing: mysql-client-5.1.35-32.1 [100%] Downloading package mysql-5.1.35-32.1.i586, 11.3 M (24.7 M unpacked) Downloading: mysql-5.1.35-32.1.i586.rpm * Downloading [100%] * Installing: mysql-5.1.35-32.1 [100%] [14:45 providence/home/david] # mysql ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) [14:45 providence/home/david] # rcmysql status Checking for service MySQL: unused [14:45 providence/home/david] # rcmysql start Will update MySQL now, if you encounter any problems, please read following file: /usr/share/doc/packages/mysql/README.SuSE Running protected MySQL... error: /var/run/mysql/protected/mysql.sock file didn't appeared... failed [14:48 providence/home/david] # rcmysql status Checking for service MySQL: unused [14:48 providence/home/david] # l /etc/my.* -rw-rw---- 1 mysql mysql 6336 2009-06-25 14:41 /etc/my.cnf -rw-rw---- 1 mysql mysql 6273 2009-06-23 13:48 /etc/my.cnf.rpmnew [14:48 providence/home/david] # mv /etc/my.cnf /etc/my.cnf.sav [14:49 providence/home/david] # cp /etc/my.cnf.rpmnew /etc/my.cnf [14:49 providence/home/david] # rcmysql start Will update MySQL now, if you encounter any problems, please read following file: /usr/share/doc/packages/mysql/README.SuSE Running protected MySQL... Upgrading MySQL... Looking for 'mysql' as: /usr/bin/mysql Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Running 'mysqlcheck'... Running 'mysqlcheck'... mysql.columns_priv OK mysql.db OK mysql.func OK <snip> Running 'mysql_fix_privilege_tables'... OK Starting service MySQL done OK, except for the situation where the /etc/my.cnf has been modified forcing the creation of /etc/my.cnf.rpmnew, the new packages work great! For this response I did upgrades on 3 servers one 11.0 and two 10.3. All worked fine after changing the my.cnf. I don't know how you handle the my.cnf issue. The biggest problem that remains is that upon install, no notice is given that mysql hasn't restarted until you manually check or hit one of your web pages. Then, there needs to be something that tells the admin that the location of the .pid file has changed and that to restart mysql, he will need to update my.cnf or simply copy my.cnf.rpmnew over the existing my.cnf and restart mysql to restore operation. Without some kinds of notice, the poor guy could be left scratching his head for a while, checking mailing lists, googling bugs, etc. unless he is told what has changes. Adding a post-install script that provides that WARNING would be a great way to resolve the issue for this -- and -- then next few updates (in case the user misses one or two of the updates) With that, I think this bug is squashed! -- 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.