1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
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:
><i> Op vrijdag 06 januari 2012 11:21:44 schreef Colin Guthrie:
</I>>><i> Hi,
</I>>><i>
</I>>><i> There are several problems today with mariadb, some more serious than
</I>>><i> others:
</I>>><i>
</I>>><i> Firstly, (a minor problem) the log file:
</I>>><i> Jan 3 14:04:34 jimmy mysqld_safe[10642]: 120103 14:04:34 mysqld_safe
</I>>><i> Logging to '/var/log/mysqld/mysqld.log'.
</I>>><i> Jan 3 14:04:34 jimmy mysqld_safe[10642]: 120103 14:04:34 mysqld_safe
</I>>><i> Starting mysqld daemon with databases from /var/lib/mysql
</I>>><i> Jan 3 14:05:53 jimmy mysqld-prepare-db-dir[11245]: touch: cannot touch
</I>>><i> `/var/log/mysqld.log': Permission denied
</I>>><i> Jan 3 14:05:53 jimmy mysqld-prepare-db-dir[11245]: chown: cannot access
</I>>><i> `/var/log/mysqld.log': No such file or directory
</I>>><i> Jan 3 14:05:53 jimmy mysqld-prepare-db-dir[11245]: chmod: cannot access
</I>>><i> `/var/log/mysqld.log': No such file or directory
</I>>><i>
</I>>><i> As the script is run as the mysql user, it cannot touch the
</I>>><i> (non-existant) log file as the directory is owned by root. Better to do
</I>>><i> this in a %post script to ensure the file is all present and properly
</I>>><i> owned to avoid this error.
</I>><i>
</I>><i> that is strange, this was an error that also mysql has had since ages; and i
</I>><i> fixed for both mysql and mariadb in cauldron, are you using an older my.cnf?
</I>><i> this error was there before and is non-fatal iirc. however, newer my.cnf files
</I>><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?
>><i> Secondly, several plugins were moved to mariadb-obsolete. I have most of
</I>>><i> my databases stored in innodb format and this was one of the plugins
</I>>><i> moved over. Even when I did install the -obsolete package to get
</I>>><i> ha_innodb back, I couldn't use it:
</I>>><i>
</I>>><i> 120106 10:15:02 Percona XtraDB (<A HREF="http://www.percona.com">http://www.percona.com</A>) 1.1.8-20.1
</I>>><i> started; log sequence number 52870027141
</I>>><i> 120106 10:15:02 [ERROR] Function 'InnoDB' already exists
</I>>><i> 120106 10:15:02 [ERROR] Couldn't load plugin named 'InnoDB' with soname
</I>>><i> 'ha_innodb.so'.
</I>>><i>
</I>>><i> Now I believe this is due to XtraDB duplicating the features of InnoDB
</I>>><i> and thus effectively obsoleting it... does this mean I simply shouldn't
</I>>><i> load InnoDB plugin now? Does it mean all the tweaks I made in my.cnf for
</I>>><i> innodb pool sizes etc. now no longer work? What is the fallout from this
</I>>><i> change?
</I>><i>
</I>><i> indeed you shouldn't use the -obsolete ones, the xtradb should nicely use your
</I>><i> innodb database, xtradb is a innodb with extra patches, so any innodb tuning
</I>><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 :)
><i> otoh, loading the ha_innodb.so should overwrite the internal xtradb code, so
</I>><i> i'll have to see why this isn't working.
</I>
Cool, I'll leave that with you :D
>><i> Thirdly, federated was changed to fedaratedx, but federated was still
</I>>><i> shipped in the mariadb-obsolete package... Sadly however the default
</I>>><i> my.cnf still tries to load the ha_federated.so by default and activate
</I>>><i> via a "federated" option in default my.cnf. So not only is a plugin
</I>>><i> activated that is not installed, even when you do install
</I>>><i> mariadb-obsolete, the "federated" option seems to no longer work anyway:
</I>>><i>
</I>>><i> 120106 10:14:16 [ERROR] /usr/sbin/mysqld: unknown option '--federated'
</I>>><i>
</I>>><i> So the "federated" option and the plugin load itself in my.cnf needs to
</I>>><i> be updated somehow, both in the default my.cnf but also some attempt
</I>>><i> should be made to update existing my.cnf too (with a backup).
</I>><i>
</I>><i> only the load plugin should be changed into federatedx.so instead of
</I>><i> federated.so ; the "federated" option is still valid for federatedx
</I>><i>
</I>><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
><i> sadly, my.cnf is a config file, i can provide a newer my.cnf all i want, it's
</I>><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 "sed -i 's/ha_federated\.so/ha_federatedx\.so/g'
/etc/my.cnf" to fix up that issue (which would prevent mysql starting...
looking back, that was probably the fundamental issue I had.
><i> my thoughts on plugins is: "xtradb is internal, because innodb was internal;
</I>><i> federatedx was external, because federated was external"
</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 "sed -i
's/ha_innodb\.so/ha_xtradb\.so/g' m/etc/my.cnf" in the %post also.
><i> can you recheck that a new my.cnf file at the very least works out of the box?
</I>><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.
><i> i'm not sure yet as how to do the upgrade to newer my.cnf other than maybe add
</I>><i> this to errata and maybe README.install.urpmi
</I>><i>
</I>><i> but, if you install using rpmdrake, didn't you get a popup box with the my.cnf
</I>><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>
|
