CA: "Unknown table engine 'InnoDB' - Request halted."
Posted: Sat Dec 13, 2014 11:29 pm
[PROBLEM]
After tweaking around on my Debian server, the CollectiveAccess Providence (v1.4) installation suddenly didn't work, and presented only this error message:
[SOLUTION]
Make sure your /tmp directory is read/writeable by anyone. I've got the "/tmp" for a virtual machine mounted externally from an ext4 partition. Therefore the trouble.
In order to fix the permissions and make them permanent, mount your /tmp partition manually once.
Then change the permissions:
That should do the trick.
NOTE: fstab mount options like "umask/dmask/fmask" are only necessary to filesystems that store their permissions differently (e.g. ntfs, smbfs, etc).
Using them on ext*-filesystems will even cause the mount to fail with the following error message:
After tweaking around on my Debian server, the CollectiveAccess Providence (v1.4) installation suddenly didn't work, and presented only this error message:
Error 250: Invalid SQL statement
Unknown table engine 'InnoDB' (in Db->mysql->execute())
Request halted.
[SOLUTION]
Make sure your /tmp directory is read/writeable by anyone. I've got the "/tmp" for a virtual machine mounted externally from an ext4 partition. Therefore the trouble.
In order to fix the permissions and make them permanent, mount your /tmp partition manually once.
Then change the permissions:
Code: Select all
$ sudo chmod 1777 /tmpNOTE: fstab mount options like "umask/dmask/fmask" are only necessary to filesystems that store their permissions differently (e.g. ntfs, smbfs, etc).
Using them on ext*-filesystems will even cause the mount to fail with the following error message:
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so