summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-January/011030.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-January/011030.html')
-rw-r--r--zarb-ml/mageia-dev/2012-January/011030.html277
1 files changed, 277 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-January/011030.html b/zarb-ml/mageia-dev/2012-January/011030.html
new file mode 100644
index 000000000..78289e7de
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-January/011030.html
@@ -0,0 +1,277 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Numerous mariadb issues today.
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Numerous%20mariadb%20issues%20today.&In-Reply-To=%3C4F06F739.1050907%40colin.guthr.ie%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="011029.html">
+ <LINK REL="Next" HREF="011031.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Numerous mariadb issues today.</H1>
+ <B>Colin Guthrie</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Numerous%20mariadb%20issues%20today.&In-Reply-To=%3C4F06F739.1050907%40colin.guthr.ie%3E"
+ TITLE="[Mageia-dev] Numerous mariadb issues today.">mageia at colin.guthr.ie
+ </A><BR>
+ <I>Fri Jan 6 14:29:29 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="011029.html">[Mageia-dev] Numerous mariadb issues today.
+</A></li>
+ <LI>Next message: <A HREF="011031.html">[Mageia-dev] Numerous mariadb issues today.
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#11030">[ date ]</a>
+ <a href="thread.html#11030">[ thread ]</a>
+ <a href="subject.html#11030">[ subject ]</a>
+ <a href="author.html#11030">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>'Twas brillig, and Maarten Vanraes at 06/01/12 12:32 did gyre and gimble:
+&gt;<i> Op vrijdag 06 januari 2012 11:21:44 schreef Colin Guthrie:
+</I>&gt;&gt;<i> Hi,
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> There are several problems today with mariadb, some more serious than
+</I>&gt;&gt;<i> others:
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Firstly, (a minor problem) the log file:
+</I>&gt;&gt;<i> Jan 3 14:04:34 jimmy mysqld_safe[10642]: 120103 14:04:34 mysqld_safe
+</I>&gt;&gt;<i> Logging to '/var/log/mysqld/mysqld.log'.
+</I>&gt;&gt;<i> Jan 3 14:04:34 jimmy mysqld_safe[10642]: 120103 14:04:34 mysqld_safe
+</I>&gt;&gt;<i> Starting mysqld daemon with databases from /var/lib/mysql
+</I>&gt;&gt;<i> Jan 3 14:05:53 jimmy mysqld-prepare-db-dir[11245]: touch: cannot touch
+</I>&gt;&gt;<i> `/var/log/mysqld.log': Permission denied
+</I>&gt;&gt;<i> Jan 3 14:05:53 jimmy mysqld-prepare-db-dir[11245]: chown: cannot access
+</I>&gt;&gt;<i> `/var/log/mysqld.log': No such file or directory
+</I>&gt;&gt;<i> Jan 3 14:05:53 jimmy mysqld-prepare-db-dir[11245]: chmod: cannot access
+</I>&gt;&gt;<i> `/var/log/mysqld.log': No such file or directory
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> As the script is run as the mysql user, it cannot touch the
+</I>&gt;&gt;<i> (non-existant) log file as the directory is owned by root. Better to do
+</I>&gt;&gt;<i> this in a %post script to ensure the file is all present and properly
+</I>&gt;&gt;<i> owned to avoid this error.
+</I>&gt;<i>
+</I>&gt;<i> that is strange, this was an error that also mysql has had since ages; and i
+</I>&gt;<i> fixed for both mysql and mariadb in cauldron, are you using an older my.cnf?
+</I>&gt;<i> this error was there before and is non-fatal iirc. however, newer my.cnf files
+</I>&gt;<i> should have the correct path
+</I>
+Ahh yes my my.cnf file didn't have the:
+
+[mysqld_safe]
+log-error=/var/log/mysqld/mysqld.log
+pid-file=/var/run/mysqld/mysqld.pid
+
+bits.
+
+If the default my.cnf file ships with that path (don't know if it does
+or if it's patched in our packages) then perhaps the
+mysqld-prepare-db-dir script should also be updated to use that as the
+default?
+
+&gt;&gt;<i> Secondly, several plugins were moved to mariadb-obsolete. I have most of
+</I>&gt;&gt;<i> my databases stored in innodb format and this was one of the plugins
+</I>&gt;&gt;<i> moved over. Even when I did install the -obsolete package to get
+</I>&gt;&gt;<i> ha_innodb back, I couldn't use it:
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> 120106 10:15:02 Percona XtraDB (<A HREF="http://www.percona.com">http://www.percona.com</A>) 1.1.8-20.1
+</I>&gt;&gt;<i> started; log sequence number 52870027141
+</I>&gt;&gt;<i> 120106 10:15:02 [ERROR] Function 'InnoDB' already exists
+</I>&gt;&gt;<i> 120106 10:15:02 [ERROR] Couldn't load plugin named 'InnoDB' with soname
+</I>&gt;&gt;<i> 'ha_innodb.so'.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Now I believe this is due to XtraDB duplicating the features of InnoDB
+</I>&gt;&gt;<i> and thus effectively obsoleting it... does this mean I simply shouldn't
+</I>&gt;&gt;<i> load InnoDB plugin now? Does it mean all the tweaks I made in my.cnf for
+</I>&gt;&gt;<i> innodb pool sizes etc. now no longer work? What is the fallout from this
+</I>&gt;&gt;<i> change?
+</I>&gt;<i>
+</I>&gt;<i> indeed you shouldn't use the -obsolete ones, the xtradb should nicely use your
+</I>&gt;<i> innodb database, xtradb is a innodb with extra patches, so any innodb tuning
+</I>&gt;<i> is still valid for xtradb.
+</I>
+OK, cool. As long as it still reads e.g. innodb_* from my.conf then all
+will be well I think :)
+
+&gt;<i> otoh, loading the ha_innodb.so should overwrite the internal xtradb code, so
+</I>&gt;<i> i'll have to see why this isn't working.
+</I>
+Cool, I'll leave that with you :D
+
+&gt;&gt;<i> Thirdly, federated was changed to fedaratedx, but federated was still
+</I>&gt;&gt;<i> shipped in the mariadb-obsolete package... Sadly however the default
+</I>&gt;&gt;<i> my.cnf still tries to load the ha_federated.so by default and activate
+</I>&gt;&gt;<i> via a &quot;federated&quot; option in default my.cnf. So not only is a plugin
+</I>&gt;&gt;<i> activated that is not installed, even when you do install
+</I>&gt;&gt;<i> mariadb-obsolete, the &quot;federated&quot; option seems to no longer work anyway:
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> 120106 10:14:16 [ERROR] /usr/sbin/mysqld: unknown option '--federated'
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> So the &quot;federated&quot; option and the plugin load itself in my.cnf needs to
+</I>&gt;&gt;<i> be updated somehow, both in the default my.cnf but also some attempt
+</I>&gt;&gt;<i> should be made to update existing my.cnf too (with a backup).
+</I>&gt;<i>
+</I>&gt;<i> only the load plugin should be changed into federatedx.so instead of
+</I>&gt;<i> federated.so ; the &quot;federated&quot; option is still valid for federatedx
+</I>&gt;<i>
+</I>&gt;<i> getting this error, means that you don't have any of them both loaded.
+</I>
+Hmm, I thought I had tried all combinations, but I obviously didn't try
+the ha_federatedx.so + federated option... gah, sorry about that. Still
+the plugin name in the conf does still need updating, so at least I'm
+not completely daft :D
+
+&gt;<i> sadly, my.cnf is a config file, i can provide a newer my.cnf all i want, it's
+</I>&gt;<i> not like i can modify the my.cnf file for existing upgrades?
+</I>
+There are various things you can do with sed/awk on upgrades... I'd at
+very least suggest a &quot;sed -i 's/ha_federated\.so/ha_federatedx\.so/g'
+/etc/my.cnf&quot; to fix up that issue (which would prevent mysql starting...
+looking back, that was probably the fundamental issue I had.
+
+&gt;<i> my thoughts on plugins is: &quot;xtradb is internal, because innodb was internal;
+</I>&gt;<i> federatedx was external, because federated was external&quot;
+</I>
+Hmm? innodb was not internal before was it? I thought it was a plugin
+since a very long time (I pretty sure I remember panicking when Oden
+enabled it for the first time a year or two back). Perhaps I'm wrong tho'.
+
+
+If you do make xtradb a plugin, then I'd suggest doing a &quot;sed -i
+'s/ha_innodb\.so/ha_xtradb\.so/g' m/etc/my.cnf&quot; in the %post also.
+
+
+&gt;<i> can you recheck that a new my.cnf file at the very least works out of the box?
+</I>&gt;<i> and is this x86_64 or i586?
+</I>
+It doesn't. It mentions ha_federated.so as mentioned above rather than
+ha_federatedx.so, so this needs to be fixed. This is on x86_64 but I
+guess that doesn't matter here.
+
+&gt;<i> i'm not sure yet as how to do the upgrade to newer my.cnf other than maybe add
+</I>&gt;<i> this to errata and maybe README.install.urpmi
+</I>&gt;<i>
+</I>&gt;<i> but, if you install using rpmdrake, didn't you get a popup box with the my.cnf
+</I>&gt;<i> differences?
+</I>
+I did get the popup, but of course as the ha_federated.so thing was the
+same, this is probably why I ran into trouble.
+
+Cheers
+
+Col
+
+--
+
+Colin Guthrie
+colin(at)mageia.org
+<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
+
+Day Job:
+ Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
+Open Source:
+ Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
+ PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
+ Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="011029.html">[Mageia-dev] Numerous mariadb issues today.
+</A></li>
+ <LI>Next message: <A HREF="011031.html">[Mageia-dev] Numerous mariadb issues today.
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#11030">[ date ]</a>
+ <a href="thread.html#11030">[ thread ]</a>
+ <a href="subject.html#11030">[ subject ]</a>
+ <a href="author.html#11030">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>