summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-January/011029.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-January/011029.html')
-rw-r--r--zarb-ml/mageia-dev/2012-January/011029.html217
1 files changed, 217 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-January/011029.html b/zarb-ml/mageia-dev/2012-January/011029.html
new file mode 100644
index 000000000..72f6dc456
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-January/011029.html
@@ -0,0 +1,217 @@
+<!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=%3C201201061332.29783.alien%40rmail.be%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="011012.html">
+ <LINK REL="Next" HREF="011030.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Numerous mariadb issues today.</H1>
+ <B>Maarten Vanraes</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Numerous%20mariadb%20issues%20today.&In-Reply-To=%3C201201061332.29783.alien%40rmail.be%3E"
+ TITLE="[Mageia-dev] Numerous mariadb issues today.">alien at rmail.be
+ </A><BR>
+ <I>Fri Jan 6 13:32:29 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="011012.html">[Mageia-dev] Numerous mariadb issues today.
+</A></li>
+ <LI>Next message: <A HREF="011030.html">[Mageia-dev] Numerous mariadb issues today.
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#11029">[ date ]</a>
+ <a href="thread.html#11029">[ thread ]</a>
+ <a href="subject.html#11029">[ subject ]</a>
+ <a href="author.html#11029">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Op vrijdag 06 januari 2012 11:21:44 schreef Colin Guthrie:
+&gt;<i> Hi,
+</I>&gt;<i>
+</I>&gt;<i> There are several problems today with mariadb, some more serious than
+</I>&gt;<i> others:
+</I>&gt;<i>
+</I>&gt;<i> Firstly, (a minor problem) the log file:
+</I>&gt;<i> Jan 3 14:04:34 jimmy mysqld_safe[10642]: 120103 14:04:34 mysqld_safe
+</I>&gt;<i> Logging to '/var/log/mysqld/mysqld.log'.
+</I>&gt;<i> Jan 3 14:04:34 jimmy mysqld_safe[10642]: 120103 14:04:34 mysqld_safe
+</I>&gt;<i> Starting mysqld daemon with databases from /var/lib/mysql
+</I>&gt;<i> Jan 3 14:05:53 jimmy mysqld-prepare-db-dir[11245]: touch: cannot touch
+</I>&gt;<i> `/var/log/mysqld.log': Permission denied
+</I>&gt;<i> Jan 3 14:05:53 jimmy mysqld-prepare-db-dir[11245]: chown: cannot access
+</I>&gt;<i> `/var/log/mysqld.log': No such file or directory
+</I>&gt;<i> Jan 3 14:05:53 jimmy mysqld-prepare-db-dir[11245]: chmod: cannot access
+</I>&gt;<i> `/var/log/mysqld.log': No such file or directory
+</I>&gt;<i>
+</I>&gt;<i> As the script is run as the mysql user, it cannot touch the
+</I>&gt;<i> (non-existant) log file as the directory is owned by root. Better to do
+</I>&gt;<i> this in a %post script to ensure the file is all present and properly
+</I>&gt;<i> owned to avoid this error.
+</I>
+that is strange, this was an error that also mysql has had since ages; and i
+fixed for both mysql and mariadb in cauldron, are you using an older my.cnf?
+this error was there before and is non-fatal iirc. however, newer my.cnf files
+should have the correct path
+
+&gt;<i> Secondly, several plugins were moved to mariadb-obsolete. I have most of
+</I>&gt;<i> my databases stored in innodb format and this was one of the plugins
+</I>&gt;<i> moved over. Even when I did install the -obsolete package to get
+</I>&gt;<i> ha_innodb back, I couldn't use it:
+</I>&gt;<i>
+</I>&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;<i> started; log sequence number 52870027141
+</I>&gt;<i> 120106 10:15:02 [ERROR] Function 'InnoDB' already exists
+</I>&gt;<i> 120106 10:15:02 [ERROR] Couldn't load plugin named 'InnoDB' with soname
+</I>&gt;<i> 'ha_innodb.so'.
+</I>&gt;<i>
+</I>&gt;<i> Now I believe this is due to XtraDB duplicating the features of InnoDB
+</I>&gt;<i> and thus effectively obsoleting it... does this mean I simply shouldn't
+</I>&gt;<i> load InnoDB plugin now? Does it mean all the tweaks I made in my.cnf for
+</I>&gt;<i> innodb pool sizes etc. now no longer work? What is the fallout from this
+</I>&gt;<i> change?
+</I>
+indeed you shouldn't use the -obsolete ones, the xtradb should nicely use your
+innodb database, xtradb is a innodb with extra patches, so any innodb tuning
+is still valid for xtradb.
+
+otoh, loading the ha_innodb.so should overwrite the internal xtradb code, so
+i'll have to see why this isn't working.
+
+
+&gt;<i> Thirdly, federated was changed to fedaratedx, but federated was still
+</I>&gt;<i> shipped in the mariadb-obsolete package... Sadly however the default
+</I>&gt;<i> my.cnf still tries to load the ha_federated.so by default and activate
+</I>&gt;<i> via a &quot;federated&quot; option in default my.cnf. So not only is a plugin
+</I>&gt;<i> activated that is not installed, even when you do install
+</I>&gt;<i> mariadb-obsolete, the &quot;federated&quot; option seems to no longer work anyway:
+</I>&gt;<i>
+</I>&gt;<i> 120106 10:14:16 [ERROR] /usr/sbin/mysqld: unknown option '--federated'
+</I>&gt;<i>
+</I>&gt;<i> So the &quot;federated&quot; option and the plugin load itself in my.cnf needs to
+</I>&gt;<i> be updated somehow, both in the default my.cnf but also some attempt
+</I>&gt;<i> should be made to update existing my.cnf too (with a backup).
+</I>
+only the load plugin should be changed into federatedx.so instead of
+federated.so ; the &quot;federated&quot; option is still valid for federatedx
+
+getting this error, means that you don't have any of them both loaded.
+
+sadly, my.cnf is a config file, i can provide a newer my.cnf all i want, it's
+not like i can modify the my.cnf file for existing upgrades?
+
+
+my thoughts on plugins is: &quot;xtradb is internal, because innodb was internal;
+federatedx was external, because federated was external&quot;
+
+can you recheck that a new my.cnf file at the very least works out of the box?
+and is this x86_64 or i586?
+
+i'm not sure yet as how to do the upgrade to newer my.cnf other than maybe add
+this to errata and maybe README.install.urpmi
+
+but, if you install using rpmdrake, didn't you get a popup box with the my.cnf
+differences?
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="011012.html">[Mageia-dev] Numerous mariadb issues today.
+</A></li>
+ <LI>Next message: <A HREF="011030.html">[Mageia-dev] Numerous mariadb issues today.
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#11029">[ date ]</a>
+ <a href="thread.html#11029">[ thread ]</a>
+ <a href="subject.html#11029">[ subject ]</a>
+ <a href="author.html#11029">[ 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>