<div dir="ltr">Thanks, this all sounds insightful. I hope we're getting close, though personally I still don't have much of a clue.<br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 10, 2013 at 10:09 PM, Bill Meek <span dir="ltr"><<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I appears to me that the script that's failing is:<br>
<br>
/var/lib/dpkg/info/mysql-<u></u>server-5.5.postinst<br></blockquote><div><br></div><div style>I had a look inside that file</div><div style><a href="http://pastebin.com/vVvUyjJT">http://pastebin.com/vVvUyjJT</a><br></div>
<div style>and the following error message caught my attention:</div><div style><br></div><div style><ol style="margin:0px;padding:0px 0px 0px 48px;color:rgb(172,172,172);font-family:Consolas,Menlo,Monaco,'Lucida Console','Liberation Mono','DejaVu Sans Mono','Bitstream Vera Sans Mono',monospace,serif;font-size:12px;line-height:21px;background-color:rgb(248,248,248)">
<li class="" style><div class="" style="padding:0px 5px;vertical-align:top;color:rgb(0,0,0);border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);background-color:rgb(255,255,255)"><span class="" style="font-weight:bold">if</span> you<span class="" style="color:rgb(255,0,0)">'re reading this, it'</span>s most likely because you had replaced <span class="" style="font-weight:bold">/</span>var<span class="" style="font-weight:bold">/</span>lib<span class="" style="font-weight:bold">/</span>mysql</div>
</li><li class="" style><div class="" style="padding:0px 5px;vertical-align:top;color:rgb(0,0,0);border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);background-color:rgb(255,255,255)">with a symlink, <span class="" style="font-weight:bold">then</span> upgraded to a new version of mysql, and <span class="" style="font-weight:bold">then</span> <span class="" style="color:rgb(194,12,185);font-weight:bold">dpkg</span></div>
</li><li class="" style><div class="" style="padding:0px 5px;vertical-align:top;color:rgb(0,0,0);border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);background-color:rgb(255,255,255)">removed your symlink <span class="" style="color:rgb(122,8,116);font-weight:bold">(</span>see <span class="" style="color:rgb(102,102,102);font-style:italic">#182747 and others). the mysql packages noticed</span></div>
</li><li class="" style><div class="" style="padding:0px 5px;vertical-align:top;color:rgb(0,0,0);border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);background-color:rgb(255,255,255)">that this happened, and <span class="" style="color:rgb(194,12,185);font-weight:bold">as</span> a workaround have restored it. however, because</div>
</li><li class="" style><div class="" style="padding:0px 5px;vertical-align:top;color:rgb(0,0,0);border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);background-color:rgb(255,255,255)"><span class="" style="font-weight:bold">/</span>var<span class="" style="font-weight:bold">/</span>lib<span class="" style="font-weight:bold">/</span>mysql seems to have been re-created <span class="" style="font-weight:bold">in</span> the meantime, and because</div>
</li><li class="" style><div class="" style="padding:0px 5px;vertical-align:top;color:rgb(0,0,0);border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);background-color:rgb(255,255,255)">we don<span class="" style="color:rgb(255,0,0)">'t want to rm -rf something we don'</span>t know <span class="" style="color:rgb(194,12,185);font-weight:bold">as</span> much about, we<span class="" style="color:rgb(255,0,0)">'re going</span></div>
</li><li class="" style><div class="" style="padding:0px 5px;vertical-align:top;color:rgb(0,0,0);border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);background-color:rgb(255,255,255)"><span class="" style="color:rgb(255,0,0)">to leave this unexpected directory here. if your database looks normal,</span></div>
</li><li class="" style><div class="" style="padding:0px 5px;vertical-align:top;color:rgb(0,0,0);border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);background-color:rgb(255,255,255)"><span class="" style="color:rgb(255,0,0)">and this is not a symlink to your database, you should be able to blow</span></div>
</li><li class="" style><div class="" style="padding:0px 5px;vertical-align:top;color:rgb(0,0,0);border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);background-color:rgb(255,255,255)"><span class="" style="color:rgb(255,0,0)">this all away.</span></div>
</li></ol></div><div><br></div><div style>Now, to be sure, I didn't replace /var/lib/mysql with a symlink, and I didn't upgrade to a NEW version of mysql, and I'm not aware of /var/lib/mysql ever having been a symlink; but perhaps what I did do (copying /var to another physical drive, deleting it and then changing /etc/fstab to point to the new /var) was equally upsetting to this poor script?</div>
<div><br></div><div style>And it's just as well it didn't rm -rf it because /var/lib/mysql/ (now /var/lib/mysql.bak/) is where mythconverg was. But not any more, now that I've moved the directory.</div><div style>
<br></div><div style><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Also when you did:<div class="im">
<br>
<br>
# ls -l /var/log/mysql<br>
total 92<br>
-rw-r----- 1 mysql adm 55463 Mar 10 17:33 error.log<br>
<br></div>
I looks like there's a lot of information in error.log,<br>
so did you look (or can you pastebinit the log?)<br></blockquote><div><br></div><div style>It's here, <a href="http://pastebin.com/vi1g23vW">http://pastebin.com/vi1g23vW</a> , but it looks like it's merely a gazillion repetitions of the following stanza, which personally doesn't tell me much:</div>
<div style><br></div><div style><div>130310 17:33:42 [Note] Plugin 'FEDERATED' is disabled.</div><div>130310 17:33:42 InnoDB: The InnoDB memory heap is disabled</div><div>130310 17:33:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins</div>
<div>130310 17:33:42 InnoDB: Compressed tables use zlib 1.2.7</div><div>130310 17:33:42 InnoDB: Using Linux native AIO</div><div>130310 17:33:43 InnoDB: Initializing buffer pool, size = 128.0M</div><div>130310 17:33:43 InnoDB: Completed initialization of buffer pool</div>
<div>InnoDB: Error: auto-extending data file ./ibdata1 is of a different size</div><div>InnoDB: 0 pages (rounded down to MB) than specified in the .cnf file:</div><div>InnoDB: initial 640 pages, max 0 (relevant if non-zero) pages!</div>
<div>130310 17:33:43 InnoDB: Could not open or create data files.</div><div>130310 17:33:43 InnoDB: If you tried to add new data files, and it failed here,</div><div>130310 17:33:43 InnoDB: you should now edit innodb_data_file_path in my.cnf back</div>
<div>130310 17:33:43 InnoDB: to what it was, and remove the new ibdata files InnoDB created</div><div>130310 17:33:43 InnoDB: in this failed attempt. InnoDB only wrote those files full of</div><div>130310 17:33:43 InnoDB: zeros, but did not yet use them in any way. But be careful: do not</div>
<div>130310 17:33:43 InnoDB: remove old data files which contain your precious data!</div><div>130310 17:33:43 [ERROR] Plugin 'InnoDB' init function returned error.</div><div>130310 17:33:43 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.</div>
<div>130310 17:33:43 [ERROR] Unknown/unsupported storage engine: InnoDB</div><div>130310 17:33:43 [ERROR] Aborting</div><div><br></div><div>130310 17:33:43 [Note] /usr/sbin/mysqld: Shutdown complete</div><div><br></div></div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
As to: # cat /etc/init.d/mysql, the actual script that<br>
starts mysqld is: /etc/init/mysql.conf. The one in /etc/init.d<br>
just 'points' to it.<br></blockquote><div><br></div><div style>And this one is here:</div><div style><a href="http://pastebin.com/wmfeNY0b">http://pastebin.com/wmfeNY0b</a><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Consider that the dpkg information is stored in the new filesystem<br>
you just created. Did you copy the old /var there with something<br>
that preserves timestamps, e.g. cp -aR? </blockquote><div><br></div><div style>I seem to recall that I did. There are files in /var/backups with a date of before the copy---is that sufficient evidence?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
It might be worth it to<br>
attempt to remove some package you never use, just to see if this<br>
is really mysql issue or a generic dpkg one (and then reinstall<br>
the package.)</blockquote><div><br></div><div style>How can I guess the name of a package that I never use (and more importantly that the system never uses, if it's not one I installed explicitly) and yet is on my system? Would it be ok if I first did </div>
<div style> apt-get install somerubbish</div><div style>and then tried to remove it? Oh well, I tried that, and yes, I got an unexpected complaint about mysql---at some point it even asked me to configure the mysql password! So, good guess, I suppose; though it's slightly more involved: it's a generic dpkg issue BUT one which makes it always complain about mysql...</div>
<div style><br></div><div style><br></div><div style><div># apt-get install gnome-mahjongg</div><div>Reading package lists... Done</div><div>Building dependency tree </div><div>Reading state information... Done</div>
<div>gnome-mahjongg is already the newest version.</div><div>0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.</div><div>2 not fully installed or removed.</div><div>After this operation, 0 B of additional disk space will be used.</div>
<div>Do you want to continue [Y/n]? n</div><div>Abort.</div><div># apt-get install mahjongg</div><div>Reading package lists... Done</div><div>Building dependency tree </div><div>Reading state information... Done</div>
<div>mahjongg is already the newest version.</div><div>0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.</div><div>2 not fully installed or removed.</div><div>After this operation, 0 B of additional disk space will be used.</div>
<div>Do you want to continue [Y/n]? </div><div>Setting up mysql-server-5.5 (5.5.29-0ubuntu0.12.10.1) ...</div><div>start: Job failed to start</div><div>invoke-rc.d: initscript mysql, action "start" failed.</div>
<div>dpkg: error processing mysql-server-5.5 (--configure):</div><div> subprocess installed post-installation script returned error exit status 1</div><div>dpkg: dependency problems prevent configuration of mysql-server:</div>
<div> mysql-server depends on mysql-server-5.5; however:</div><div> Package mysql-server-5.5 is not configured yet.</div><div><br></div><div>dpkg: error processing mysql-server (--configure):</div><div> dependency problems - leaving unconfigured</div>
<div>No apport report written because the error message indicates its a followup error from a previous failure.</div><div> Errors were encountered while processing:</div><div> mysql-server-5.5</div>
<div> mysql-server</div><div>E: Sub-process /usr/bin/dpkg returned an error code (1)</div><div># </div><div><br></div><div><br></div><div><div>Thank you very much for your patience and perseverance with all this, Bill and everyone else! I'm really at the end of my guesses and your support is greatly appreciated!</div>
<div><br></div></div></div></div></div></div>