[opensuse] What happened to mysql? Broken after latest update from BS::/server/database.
Listmates, MySQL died on my laptop after the latest package update. Looking at the logs, I think they are just the old logs and don't show much: [03:05 alchemy:~] # cat mysqld.log-20090411 090410 03:46:55 mysqld ended 090410 03:48:14 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 090410 3:48:17 InnoDB: Started; log sequence number 0 43655 090410 3:48:17 [ERROR] /usr/sbin/mysqld: unknown option '--skip-federated' 090410 3:48:17 [ERROR] Aborting 090410 3:48:17 InnoDB: Starting shutdown... 090410 3:48:21 InnoDB: Shutdown completed; log sequence number 0 43655 090410 3:48:21 [Warning] Forcing shutdown of 1 plugins 090410 3:48:21 [Note] /usr/sbin/mysqld: Shutdown complete 090410 03:48:22 mysqld_safe mysqld from pid file /var/run/mysql/protected/mysqld.pid ended Trying to start mysql results in a failed start: [02:53 alchemy:/home/david] # rcmysql start Updating MySQL privilege database... failed Looking at the installed mysql packages, something is definitely out of whack: [02:55 alchemy:/home/david] # rpm -qa | grep mysql libgda-3_0-mysql-3.1.2-42.1 libmysqlclient15-5.0.67-49.1 libmysqlclient16-5.1.33-26.1 libmysqlclient_r15-5.0.67-49.1 libmysqlclient_r16-5.1.33-26.1 mysql-5.1.33-26.1 mysql-client-5.1.33-26.1 Hmm, an overabundance of libmysqlclient, but how & how to fix? I'll try the removal of the libmysqlclient16 versions and if that fails, all of mysql and reinstall. Where did 16 come from? 03:09 alchemy:~> webpin -u libmysqlclient_r16 ... performing request on http://api.opensuse-community.org/searchservice/Search/Simple/openSUSE_110/l... 5 results (1 packages) found for "libmysqlclient_r16" in openSUSE_110 * libmysqlclient_r16: MySQL Shared Libraries - 5.1.33 [BS::server:/database:/mysql51 | BS::server:/database | BS::home:/NicoK:/server | BS::home:/fchua | BS::home:/bajizs_cnt] <snip> @ http://download.opensuse.org/repositories/server:/database/openSUSE_11.0 Thanks for the -u Anders;-) The biggest question is how did zypper allow this? Seems like installing 2 versions of the same package with foreseeable conflicting library files would have been caught. (1) First attempt at repair: Yast -> SW Management -> Search mysql -> Packages -> All packages in this list -> update if a newer version available Curious, yast didn't complain at all about both versions of libmysqlclient(15/16) being installed at the same time. Result: [03:18 alchemy:/home/david] # rcmysql start Updating MySQL privilege database... failed Nothing in syslog Exit status of rcmysql start: 1 /usr/sbin/rcmysql: # 1 - generic or unspecified error 03:37 alchemy:~> rpm -qa | grep mysql | sort libgda-3_0-mysql-3.1.2-42.1 libmysqlclient15-5.0.67-49.1 libmysqlclient16-5.1.33-27.1 libmysqlclient_r15-5.0.67-49.1 libmysqlclient_r16-5.1.33-27.1 mysql-5.1.33-26.1 mysql-client-5.1.33-26.1 (2) Second Attempt at repair: Yast -> SW Management -> Search mysql -> downgrade to libmysqlclient15-5.0.51a Result: WTF?? [03:48 alchemy:~] # rcmysql start Updating MySQL privilege database... failed [03:48 alchemy:~] # echo $? 1 [03:49 alchemy:~] # rpm -qa | grep mysql | sort libgda-3_0-mysql-3.1.2-42.1 libmysqlclient15-5.0.67-49.1 libmysqlclient_r15-5.0.67-49.1 mysql-5.0.51a-27.2 mysql-client-5.0.51a-27.2 [03:52 alchemy:/var/lib/mysql] # l total 20572 drwxr-xr-x 7 mysql mysql 4096 2009-04-14 03:46 ./ drwxr-xr-x 50 root root 4096 2009-04-13 05:01 ../ -rw-rw---- 1 mysql mysql 10485760 2009-04-14 03:25 ibdata1 -rw-rw---- 1 mysql mysql 5242880 2009-04-14 03:25 ib_logfile0 -rw-rw---- 1 mysql mysql 5242880 2008-07-27 13:12 ib_logfile1 drwx------ 2 mysql mysql 4096 2008-08-28 14:40 mysql/ -rw-rw---- 1 mysql mysql 5427 2009-04-14 03:48 mysqld.log -rw-rw---- 1 mysql mysql 435 2009-04-03 05:02 mysqld.log-20090403.bz2 -rw-rw---- 1 mysql mysql 235 2009-04-07 05:02 mysqld.log-20090407.bz2 -rw-rw---- 1 mysql mysql 249 2009-04-09 05:06 mysqld.log-20090409.bz2 -rw-r--r-- 1 mysql mysql 7 2008-07-27 13:12 mysql_upgrade_info drwx------ 2 mysql mysql 4096 2008-09-19 11:54 .protected/ -rw-r--r-- 1 mysql mysql 0 2009-04-14 03:46 .run-mysql_upgrade drwx------ 2 mysql mysql 4096 2009-03-07 01:34 test/ drwxr-xr-x 2 mysql mysql 4096 2008-09-19 11:54 .tmp/ drwx------ 2 mysql mysql 4096 2009-04-03 01:46 web/ Looks like a bloody mess! Since when are my log files now in /var/lib/mysql? Let's delete .run-mysql_upgrade and give it a go -- nope: [04:01 alchemy:/var/lib/mysql] # rcmysql start Starting service MySQL warning: /var/lib/mysql/mysql.sock didn't appear within 30 seconds done [04:02 alchemy:/var/lib/mysql] # rcmysql status Checking for service MySQL: unused OK, let's wipe everything out and give it another go: [04:05 alchemy:/var/lib] # rm -r mysql/ && rcmysql start Ooops! That was bad, good thing I used the old tar -cjf mysql_upgrade_mess.tar.bz2 (3) Third Attempt at repair: [04:12 alchemy:/var/lib] # tar -xjf /root/mysql_upgrade_mess.tar.bz2 Yast -> Repository Manager -> disable Build service - server Yast -> SW Management -> Search mysql -> downgrade all packages in red Result: 090414 04:16:31 mysqld started 090414 4:16:31 [ERROR] /usr/sbin/mysqld: unknown option '--skip-federated' 090414 04:16:31 mysqld ended WTF is --skip-federated? [04:20 alchemy:/var/lib] # mysqld 090414 4:20:36 [ERROR] mysqld: unknown option '--skip-federated' Alright where is the option my.cnf? [04:20 alchemy:/var/lib] # grep federated /etc/my.cnf skip-federated [04:21 alchemy:/var/lib] # vi /etc/my.cnf #skip-federated [04:22 alchemy:/var/lib] # rcmysql start Starting service MySQL done Well Son-of-a-Bitch, will you look at that! [04:23 alchemy:/var/lib] # mysql Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 5.0.51a SUSE MySQL RPM Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | mysql | | test | | web | +--------------------+ 4 rows in set (0.00 sec) Looks like there was a problem with the openSuSE build service server/database mysql packages. Oh well, just another problem with build service. No use filing a bug report -- WON'T FIX. We'll just let the next guy bitten by the botched mysql packages for 11.0 figure it out himself ;-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote: <big snip> The problem is with the dependencies for the following packages. mysql-administrator-5.0r12-195.1 mysql-gui-tools-5.0r12-195.1 mysql-query-browser-5.0r12-195.1 mysql-workbench-5.0r12-195.1 Update of these packages to the version 5.0r14 pulls in libmysqlclient_r16-5.1.33-26.1 and libmysqlclient16-5.1.33-26.1 and causes the whole bloody mess... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Le April 14, 2009 05:36:27 am David C. Rankin, vous avez écrit :
David C. Rankin wrote:
<big snip>
The problem is with the dependencies for the following packages.
mysql-administrator-5.0r12-195.1 mysql-gui-tools-5.0r12-195.1 mysql-query-browser-5.0r12-195.1 mysql-workbench-5.0r12-195.1
Update of these packages to the version 5.0r14 pulls in libmysqlclient_r16-5.1.33-26.1 and libmysqlclient16-5.1.33-26.1 and causes the whole bloody mess...
-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Yes. It's broken. mysql.sock was moved from /var/lib/mysql to /var/run. mysqldump is hosed, I have better result with the vanilla release from mysql. I azm playing with it since sunday. Andre. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 4/14/2009 at 11:28, "David C. Rankin" <drankinatty@suddenlinkmail.com>
Is it me or are all your mails a little bit 'cranky' ? Might be just me associating it very closely to the name. Whenever I read C. Ranking I already know another cranky mail is coming in. Maybe writing your mails in a more pragmatic and objective way would help everybody: - The mails would be easier to read - They would be much more motivating to actually be read - Any issue found in them might actually also be solved If a package breaks like the one you mention here, then a note to the package maintainer is surely not wrong. If you want a fully supported system, then using a dozen of OBS repos clearly IS wrong. Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dominique Leuenberger wrote:
On 4/14/2009 at 11:28, "David C. Rankin" <drankinatty@suddenlinkmail.com>
Is it me or are all your mails a little bit 'cranky' ? Might be just me associating it very closely to the name. Whenever I read C. Ranking I already know another cranky mail is coming in.
Maybe writing your mails in a more pragmatic and objective way would help everybody: - The mails would be easier to read - They would be much more motivating to actually be read - Any issue found in them might actually also be solved
If a package breaks like the one you mention here, then a note to the package maintainer is surely not wrong. If you want a fully supported system, then using a dozen of OBS repos clearly IS wrong.
Dominique
Probable cause: Lack of sleep from trying to help my favorite distro keep from going over a cliff. I'll try to pull back on the dry sarcasm a bit, but you know as they say, "the truth hurts sometimes..." Further, and in direct response to your statement above, can you please explain to me what is wrong with me using http://download.opensuse.org/repositories/server:/database/ as a repository on my system? I do make heavy use of server apps and do like to stay current with changes so I don't experience culture shock with the wave of changes that come with each new releases. It softens the blow so to speak. Next, also let me know, if it is no longer proper or appreciated for members of the community to try the new packages out and identify any problems with them. I always thought that was rather helpful so that any problem could be corrected and prevented from propagating into the next release. If that's not OK anymore, I'll stop and let someone else do it. I've been managing my boxes in the same manner, with a number of repositories since at least 10.0 (I don't think we had near the number of repos with 8.0-9.3), but it has only been in the last 6 months that packages seem to be broken on a regular basis. I find and document the problems and I find them, put the information out on the list for peer review, and file bug reports when appropriate. I really fail to see an issue with that. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David,
On 4/14/2009 at 12:04, "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote: Probable cause: Lack of sleep from trying to help my favorite distro keep from going over a cliff.
Sleep can be a very good thing and I'm quite sure it helps reducing frustration for everybody.
Further, and in direct response to your statement above, can you please explain to me what is wrong with me using http://download.opensuse.org/repositories/server:/database/ as a repository on my system? I do make heavy use of server apps and do like to stay current with changes so I don't experience culture shock with the wave of changes that come with each new releases. It softens the blow so to speak.
nothing directly 'wrong' with it, BUT: it's a community repository. not maintained with the same QA as openSUSE base repoistories and update repositories. As such, some packages might be published untested. I for example build plenty of packages in OBS (not the ones you were affected yet by luckily) but I have only 2 computers I can test them on, running OSS 11.1 and another one Factory. And in many apps, due to lack of knowledge, I couldn't possibly test if every single feature is working.
Next, also let me know, if it is no longer proper or appreciated for members of the community to try the new packages out and identify any problems with them. I always thought that was rather helpful so that any problem could be corrected and prevented from propagating into the next release. If that's not OK anymore, I'll stop and let someone else do it.
It is PERFECT if the community members help identity problems and REPORT them in a friendly manner, brought to the points, with simple facts. And as you're TESTING, I would say you should even EXPECT breakage (otherwise you would expect them already to be tested!)
I've been managing my boxes in the same manner, with a number of repositories since at least 10.0 (I don't think we had near the number of repos with 8.0-9.3), but it has only been in the last 6 months that packages seem to be broken on a regular basis. I find and document the problems and I find them, put the information out on the list for peer review, and file bug reports when appropriate. I really fail to see an issue with that.
The more repositories, the higher the chances of conflicts. Especially, as most repositories are no longer just 'additional' software but they start replacing base libraries. Just wait for one that will replace glibc on openSUSE 10.3 (this might actually be requested. VLC 1.0-pre1 for example does not compile on 10.3 due to a bug in glibc. And the 'community' is not strong enough (yet) to backport such extensive fixes and will probably just end up creating an updated package...) So as a resume: Keep up the testing work and reporting, but don't forget to get a healthy portion of sleep once in a while. Try to make the mails and reports as helpful as possible. Even if you're annoyed by another breakage: try to stay relaxed when writing a bug report. Maybe it helps to not 'just write' it when you see it, but reflect on it a bit. A report that does not attach a packager from the very beginning on but tells me what is wrong (be it with or without patch) is more likely to get attention than one that calls the packager a fool for not having remarked it by himself (NO: I do NOT say that you told somebody he was a fool! This is just an example to stress the point). Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 14 April 2009 05:38:20 Dominique Leuenberger wrote:
Is it me or are all your mails a little bit 'cranky' ?
It is you. This is an ad hominem. regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-04-14 at 04:28 -0500, David C. Rankin wrote:
090410 3:48:17 [ERROR] /usr/sbin/mysqld: unknown option '--skip-federated' 090410 3:48:17 [ERROR] Aborting
You didn't notice this at first, this seems the main problem. I don't have that option, apparently.
Looking at the installed mysql packages, something is definitely out of whack:
[02:55 alchemy:/home/david] # rpm -qa | grep mysql libgda-3_0-mysql-3.1.2-42.1 libmysqlclient15-5.0.67-49.1 libmysqlclient16-5.1.33-26.1 libmysqlclient_r15-5.0.67-49.1 libmysqlclient_r16-5.1.33-26.1 mysql-5.1.33-26.1 mysql-client-5.1.33-26.1
Hmm, an overabundance of libmysqlclient, but how & how to fix? I'll try the removal of the libmysqlclient16 versions and if that fails, all of mysql and reinstall. Where did 16 come from?
As the base name of libmysqlclient15 and libmysqlclient16 are different, it is not as if rpm recognizes two versions of the same package, but rather, two different packages with different names, probably providing the same services. No conflicts easily detected. The client should know what library to call. Try removing all the low numbered ones. I can tell you what I have, in my 11.0 install, no OBS, so that you can compare: cer@nimrodel:~> rpm -qa | grep -i mysql libmysqlclient15-5.0.51a-27.2 mysql-gui-tools-5.0r12-56 qt3-mysql-3.3.8b-44.1 mysql-query-browser-5.0r12-56.2 mysql-administrator-5.0r12-56 rekall-mysql-2.4.6-107.1 perl-DBD-mysql-4.006-41.1 mysql-tools-5.0.51a-27.2 koffice-database-mysql-1.6.3-215.1 libqt4-sql-mysql-4.4.3-13.1 libmysqlclient_r15-5.0.51a-27.2 mysql-client-5.0.51a-27.2 mysql-workbench-5.0r12-56 mysql-connector-java-3.1.12-239.1 libgda-3_0-mysql-3.1.2-42.1 php5-mysql-5.2.9-0.1 mysql-5.0.51a-27.2 libmysqlclient-devel-5.0.51a-27.2 - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknkasAACgkQtTMYHG2NR9W/lQCbBHrloKDLJOqcaDBZ5BPcrLb/ +TUAn0kCzK0uYJM2lx/Kz19uE0ol1rQu =IQBV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Tuesday, 2009-04-14 at 04:28 -0500, David C. Rankin wrote:
090410 3:48:17 [ERROR] /usr/sbin/mysqld: unknown option '--skip-federated' 090410 3:48:17 [ERROR] Aborting
You didn't notice this at first, this seems the main problem. I don't have that option, apparently.
Looking at the installed mysql packages, something is definitely out of whack:
[02:55 alchemy:/home/david] # rpm -qa | grep mysql libgda-3_0-mysql-3.1.2-42.1 libmysqlclient15-5.0.67-49.1 libmysqlclient16-5.1.33-26.1 libmysqlclient_r15-5.0.67-49.1 libmysqlclient_r16-5.1.33-26.1 mysql-5.1.33-26.1 mysql-client-5.1.33-26.1
Hmm, an overabundance of libmysqlclient, but how & how to fix? I'll try the removal of the libmysqlclient16 versions and if that fails, all of mysql and reinstall. Where did 16 come from?
As the base name of libmysqlclient15 and libmysqlclient16 are different, it is not as if rpm recognizes two versions of the same package, but rather, two different packages with different names, probably providing the same services. No conflicts easily detected. The client should know what library to call. Try removing all the low numbered ones.
I can tell you what I have, in my 11.0 install, no OBS, so that you can compare:
cer@nimrodel:~> rpm -qa | grep -i mysql libmysqlclient15-5.0.51a-27.2 mysql-gui-tools-5.0r12-56 qt3-mysql-3.3.8b-44.1 mysql-query-browser-5.0r12-56.2 mysql-administrator-5.0r12-56 rekall-mysql-2.4.6-107.1 perl-DBD-mysql-4.006-41.1 mysql-tools-5.0.51a-27.2 koffice-database-mysql-1.6.3-215.1 libqt4-sql-mysql-4.4.3-13.1 libmysqlclient_r15-5.0.51a-27.2 mysql-client-5.0.51a-27.2 mysql-workbench-5.0r12-56 mysql-connector-java-3.1.12-239.1 libgda-3_0-mysql-3.1.2-42.1 php5-mysql-5.2.9-0.1 mysql-5.0.51a-27.2 libmysqlclient-devel-5.0.51a-27.2
-- Cheers, Carlos E. R.
Thanks Carlos, What threw me was the date in the mysql.log "090410." I was trying to get it going yesterday 090414 (or this morning if your counting) and couldn't explain why the failures were *not* reflected in the mysql.log. Once I found that the log file location had changed to /var/lib/mysql, the errors made sense. Thanks to Andre, we have a second confirmation on the broken state of the packages in the build service .../server/database repository: "Yes. It's broken. mysql.sock was moved from /var/lib/mysql to /var/run. mysqldump is hosed," ...and by negative implication positive confirmation on my sanity, cranky or not;-) Hopefully this will get straightened out soon. (Small P.S., Just so the record is straight: "I'm in the business of fixing things, ... I'm not in the happiness business. If I were in the happiness business, I would have a red rubber nose, a white face, and size 14 shoes... I don't." -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 14 April 2009 17:05:06 David C. Rankin wrote:
Thanks to Andre, we have a second confirmation on the broken state of the packages in the build service .../server/database repository:
"Yes. It's broken. mysql.sock was moved from /var/lib/mysql to /var/run. mysqldump is hosed,"
...and by negative implication positive confirmation on my sanity, cranky or not;-)
I can confirm also this brocken state of mysql packages. Both 32 and 64 bits versions are affected, in my case. -- Bogdan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Andre Malin -
Bogdan Cristea -
Carl Hartung -
Carlos E. R. -
David C. Rankin -
Dominique Leuenberger