Trying to install MT 4.1 on RHEL. mt-check reports:



SQLite is version 2.8.17

When I get to the Test Connection step, I receive the following error:

I've searched the KB, the wiki, these forums and the web in general and cant find any information regarding this error. I've also read the entry on MT and RHEL. Any suggestions/ideas?

*update* - I did find the following thread (interestingly, when I searched this forum, that thread did not show up, but did when I searched Google), but in that poster's case, s/he was using MySQL and his/her cgi path was incorrect. I should also note that I tried manually creating a mt-config file, but received the same error message.

*update2* - FIXED! See my post below for the solution.

What database information is in your mt-config file?

Do you have a uncommented ObjectDriver setting?

I was never able to make it through the wizard far enough for it to generate a mt-config file. I installed MT on a similarly configured server, took the mt-config file from that successful installation, changed it to appropriate values for this server, and tried but still receive the same error when I try to access mt.cgi. the contents of the mt-config file is

anyone have any ideas? Or suggestions to try? I'm really at a loss here on what to try next.

I have no idea. But you might find something interesting in this post. RHEL apparently has a bunch of security-related quirks that create complications setting applications up.

Yea, I read through that, and have MT installed on a different RHEL server, just to rule out that as being the problem. So I'm confident that there is something on this server that is different, and causing the problem. But I need to have at least a decent idea of what the cause is before I go talk to the SysAdmin.

ok, after a LOT of digging, I have been able to determine that $driver->dsn at line 54 in DBI.pm is not set, which is causing DBI to substitute the value of the environment variable DBI_DSN in instead, which is also unset.

In addition, I went back to the MT archives and installed v3.36 on the same server with no problems at all. However, I would prefer to be using version 4.

I also tried v4.01 and experieced the same error as I am running into in v4.1.

So does anyone have any ideas on what changed from 3.36 to 4.X branch with the way it handles SQLite that would be causing these issues?

ok, so i FINALLY got it working! As it turns out, the problem had nothing to do with DBI_DSN or the dsn not being set (well, farther down the execution path it did; but that wasnt the root cause). The problem was that MT needed both the directory and the database file's permission set to 777. To further complicate things, suEXEC was supposed to be in place in running, which is why I didnt think about permissions as they were already set to 770. Also, the installation documentation doesnt mention anything about directory/file permission issues when using SQLite.

So, if you get the error I listed above while trying to install MT + SQLite, make sure that the directory and the db file have adequate permissions set.