2

I had to change the tmpdir directory from /tmp to /db/tmp/ folder due to the fact I didn't have enough space. When I changed my path and I ran SHOW ENGINES; I got below result;

  1. ARCHIVE
  2. MRG_MYISAM
  3. CSV
  4. MYISAM
  5. MEMORY

But, when I changed the directory back to /tmp my Innodb engine came back. SHOW ENGINES;

  1. ARCHIVE
  2. MRG_MYISAM
  3. CSV
  4. MYISAM
  5. MEMORY
  6. InnoDB

Does anyone know why MySQL is acting strange like that? This is a show stopper for me and causing my production server to crash.

  • What is in that tmp folder? Anything with .001 .002 .003, etc? --Nevermind, I read tables, you were asking about engines. – Tim Dec 21 '11 at 19:52
  • there is nothing there – Kourosh Samia Dec 21 '11 at 19:56
  • 1
    can you check mysqld.log and see if any problems logged into log file? – Michael Dec 21 '11 at 20:17
0

You should add the following to /etc/my.cnf

[mysqld]
tmpdir=/db/tmp

then service mysql restart (For tmpdir, restart is required)

Also, run this in Linux just in case:

$ chown mysql:mysql /db/tmp
$ chmod 777 /db/tmp

Give it a Try !!!

  • Done that but still same issue! – Kourosh Samia Dec 21 '11 at 23:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.