<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 26 January 2016 at 14:36, David L <span dir="ltr"><<a href="mailto:idht4n@gmail.com" target="_blank">idht4n@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"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 25, 2016 at 11:07 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.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"><span>On 01/25/2016 01:07 PM, David L 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">
<br>
I have had mythtv installed on that backend for ~6 years and don't recall ever specifying a temp directory for MySQL. I assume it's using whatever the default directory was configured when I originally installed it. In any case, it doesn't look like any of my partitions are full.<br>
<br>
udev 2.0G 4.0K 2.0G 1% /dev<br>
tmpfs 404M 1.3M 402M 1% /run<br>
/dev/sda1 92G 80G 7.7G 92% /<br>
none 4.0K 0 4.0K 0% /sys/fs/cgroup<br>
none 5.0M 0 5.0M 0% /run/lock<br>
none 2.0G 246M 1.8G 13% /run/shm<br>
none 100M 24K 100M 1% /run/user<br>
/dev/sdb1 459G 413G 23G 95% /var/lib/mythtv<br>
/dev/sdc1 1.8T 1.6T 163G 91% /sdc1<br>
/dev/sda6 265G 229G 23G 91% /sda6<br>
/dev/sda5 1.9G 518M 1.2G 30% /var/log<br>
</blockquote>
<br></span>
It's also possible your file system is out of inodes. You can check with df -i .<br></blockquote><div><br></div><div>That is not the problem:</div><div><br></div><div><div>df -i</div><div>Filesystem Inodes IUsed IFree IUse% Mounted on</div><div>udev 205701 648 205053 1% /dev</div><div>tmpfs 211853 733 211120 1% /run</div><div>/dev/sda1 6111232 709377 5401855 12% /</div><div>none 211853 2 211851 1% /sys/fs/cgroup</div><div>none 211853 5 211848 1% /run/lock</div><div>none 211853 5 211848 1% /run/shm</div><div>none 211853 19 211834 1% /run/user</div><div>/dev/sda6 17645568 495118 17150450 3% /sda6</div><div>/dev/sdb1 30531584 8626 30522958 1% /var/lib/mythtv</div><div>/dev/sdc1 122101760 9882 122091878 1% /sdc1</div><div>/dev/sda5 122160 896 121264 1% /var/log</div></div><div><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">
<br>
That said, it looks like your temp file is being stored in the same directory as your mythconverg database files. The specific error:<span><br>
<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">
error : Can't create new tempfile: './mythconverg/program.TMD'<br>
</blockquote>
<br></span>
could also indicate that there's already a program.TMD file in the directory owned by someone else (or even that the user running mysqld doesn't have permission to create new files in the mythconverg directory). If that's there, delete it, then re-run mysqlcheck.</blockquote><div>I haven't found any directory named mythconverg in /tmp or elsewhere, so I don't know where to look for a permission problem.</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"><span><br>
<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">
The repair program runs without any obvious errors:<br>
<br>
Repaired/Optimized: `mythconverg`.`archiveitems`<br>
Analyzed: `mythconverg`.`archiveitems`<br>
<snip><br>
Repaired/Optimized: `mythconverg`.`program`<br>
Analyzed: `mythconverg`.`program`<br>
<snip><br>
Repaired/Optimized: `mythconverg`.`websites`<br>
Analyzed: `mythconverg`.`websites`<br>
<br>
But it doesn't seem to fix anything. Per your link to the temp dir configuration, I tried setting the TMPDIR environment variable to a partition with lots of free space:<br>
sudo mkdir /sdc1/tmp<br>
sudo chmod a+rwX /sdc1/tmp/<br>
export TMPDIR=/sdc1/tmp/<br>
df -h $TMPDIR<br>
Filesystem Size Used Avail Use% Mounted on<br>
/dev/sdc1 1.8T 1.6T 163G 91% /sdc1<br>
</blockquote>
<br></span>
and you restarted mysqld from an environment that contained said TMPDIR? Otherwise, it wouldn't affect anything (it's the MySQL server's temp, not the mysqlcheck script's temp that's the problem).<span><br>
<br></span></blockquote><div>Oops... my bad.</div><div><br></div><div>So now I have changed my.cnf to point to /sdc1/tmp for tmpdir and rebooted. But mysqld won't even run:</div><div><br></div><div><div>sudo /usr/sbin/mysqld</div><div>160125 19:28:14 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.</div><div>160125 19:28:14 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0ubuntu0.14.04.2) starting as process 6699 ...</div><div>160125 19:28:14 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.</div><div>160125 19:28:14 [Note] Plugin 'FEDERATED' is disabled.</div><div>160125 19:28:14 InnoDB: The InnoDB memory heap is disabled</div><div>160125 19:28:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins</div><div>160125 19:28:14 InnoDB: Compressed tables use zlib 1.2.8</div><div>160125 19:28:14 InnoDB: Using Linux native AIO</div><div>/usr/sbin/mysqld: Can't create/write to file '/sdc1/tmp/ibDadC00' (Errcode: 13)</div><div>160125 19:28:14 InnoDB: Error: unable to create temporary file; errno: 13</div><div>160125 19:28:14 [ERROR] Plugin 'InnoDB' init function returned error.</div><div>160125 19:28:14 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.</div><div>160125 19:28:14 [ERROR] Unknown/unsupported storage engine: InnoDB</div><div>160125 19:28:14 [ERROR] Aborting</div><div><br></div><div>160125 19:28:14 [Note] /usr/sbin/mysqld: Shutdown complete</div></div><div><br></div><div><br></div><div>I have verified that /sdc1/tmp/ibDadC00 can be written to:</div><div><div>dd if=/dev/zero of=/sdc1/tmp/ibDadC00 bs=8192 count=8192</div><div>8192+0 records in</div><div>8192+0 records out</div><div>67108864 bytes (67 MB) copied, 0.3417 s, 196 MB/</div></div></div></div></div></blockquote></div></div><div class="gmail_extra"><br></div><div class="gmail_extra">It needs to be able to be written to by the mysql user. Check the permissions.<div><br></div><div>The mythconverg directory you mention will likely be based in the database are, possibly under /var/lib/mysql, but this depends on your distro and setup.</div><div><br></div><div>Check the output of:</div><div> locate mythconverg</div><div>when logged in as root (or run it via sudo).</div><div><br></div><div>Lets take a step back here, you're making change after change without really narrowing down what your actual original issue was, and creating furthe issues as you go. This "resolution" path seems to be spiralling into oblivion!</div><div><br></div><div>When you had your initial issue, what was in the mysql log file? There should be some clues there.</div></div></div>