<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 8/29/12 10:25 AM,
[[w:en:User:Madman]] wrote:<br>
</div>
<blockquote
cite="mid:CABRYoDBFBmWhS9SvZMWY73uoBJ59jK=2u0E_jt53+vStHayMFA@mail.gmail.com"
type="cite">
<pre wrap="">On Tue, Aug 28, 2012 at 10:45 AM, Steve Slevinski <a class="moz-txt-link-rfc2396E" href="mailto:slevin@signpuddle.net"><slevin@signpuddle.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi list,
The upgrade seems to have confused mysql on my instance.
After a lot of investigation and poking around and a few reboots, I was able
to produce the error:
(Can't contact the database server: Unknown database 'testwiki' (localhost))
</pre>
</blockquote>
<pre wrap="">
It wasn't the upgrade; this is just probably the first time your MySQL
server's restarted. There's been an issue with the MySQL manifest for
some time. The issue can be reproduced by creating a new instance,
running puppetd -tv, then restarting MySQL; this causes the problem
you report.</pre>
</blockquote>
Thanks for keeping tabs on this bug. I believe that I fixed it a
few weeks ago, with these patches:<br>
<br>
<a class="moz-txt-link-freetext" href="https://gerrit.wikimedia.org/r/#/c/17619/">https://gerrit.wikimedia.org/r/#/c/17619/</a><br>
<a class="moz-txt-link-freetext" href="https://gerrit.wikimedia.org/r/#/c/20913/">https://gerrit.wikimedia.org/r/#/c/20913/</a><br>
<br>
<br>
Of course, those fixes don't help folks who set up their instances
during the period of breakage. That problem can (probably) be
addressed by adding the puppet var
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
mysql_datadir and changing it to point to the desired data dir.<br>
<br>
(Although, I don't believe that that change helped Steve S, so I may
be misinformed or he may have something else going on.)<br>
<br>
<blockquote
cite="mid:CABRYoDBFBmWhS9SvZMWY73uoBJ59jK=2u0E_jt53+vStHayMFA@mail.gmail.com"
type="cite">
<pre wrap="">
If I recall correctly, MyISAM files are in /var/lib/mysql, which is
the server's initial data directory when it starts successfully, then
it's changed to /mnt/mysql and that's where InnoDB files are(?). I
believe I ended up moving testwiki to /mnt/mysql and running
mysql_install_db to recreate the mysql directory in that data
directory. I reported this on August 8th to a root who was already
aware of the problem. *shrug*</pre>
</blockquote>
Sorry that this fix didn't get publicized. If there's a bugzilla
entry about it, please refer me to it and I will update accordingly!<br>
<br>
-Andrew<br>
<br>
<br>
</body>
</html>