This may not strictly be an installation problem but I thought this forum might have the right expertise, so my situation is as follows:
I have been using MT sucessfully for quite a few months now but my Hosting company recently decided to upgrade their server. They re-published my site for me (I am abroad and unable to do it myself) and all the archive files etc appear to be there but I am no longer able to access the MT admin interface, write new postings or use the comments functionality. Attempting any of these gives me the error message below. I have checked the config file for paths to perl and my db folder and they are still correct. Can anyone suggest what I can do to fix it, or what my Hosting company might have done to cause it if the first place?
============
Got an error: Unsupported driver MT::ObjectDriver::DBM: Can't locate DB_File.pm in @INC (@INC contains: ./extlib ./lib /usr/lib/perl5/5.6.1/i386-linux /usr/lib/perl5/5.6.1 /usr/lib/perl5/site_perl/5.6.1/i386- linux /usr/lib/perl5/site_perl/5.6.1 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.6.1/i386-linux /usr/lib/perl5/vendor_perl/5.6.1 /usr/lib/perl5/vendor_perl .) at lib/MT/ObjectDriver/DBM.pm line 9. BEGIN failed--compilation aborted at lib/MT/ObjectDriver/DBM.pm line 9. Compilation failed in require at (eval 3) line 1. BEGIN failed--compilation aborted at (eval 3) line 1.
Full Version: Error: Unsupported driver - db issue
Well, after several fruitless messages to and from my hosting company's tech support they are saying that from their own testing on the new server, MT will not work with DB_File any more and that I have to change to mySQL. I am happy to do that (and it will most likely be quicker than trying to insist they sort out the DB_File stuff) but don't quite know how to go about doing it.
1) what do I need to do/install/edit to make the change from Berkley db to mySQL - is it simply a change to the mt.cfg file or is there more to it than that?
2) how do I make all my existing blogs and templates work with the new db? ...and before you ask, no I stupidly haven't got any backups! (I'm travelling South America at the moment and haven't had very regular/good access to manage my site for the past 2 months!)
My site currently has all of the files it did before MT stopped working - it's just the DB_File module that's missing as far as I know.
Please help!
Emma
1) what do I need to do/install/edit to make the change from Berkley db to mySQL - is it simply a change to the mt.cfg file or is there more to it than that?
2) how do I make all my existing blogs and templates work with the new db? ...and before you ask, no I stupidly haven't got any backups! (I'm travelling South America at the moment and haven't had very regular/good access to manage my site for the past 2 months!)
My site currently has all of the files it did before MT stopped working - it's just the DB_File module that's missing as far as I know.
Please help!
Emma
Hi Donna,
I have upgraded my version of MT to 2.64 which has the conversion script in it. I altered my cfg file as per the tutorial to work with mysql and then ran the script but now have the following problems...
1) MT is telling me I have no authors and therefore won't let me log in. I have run mt-medic and all that does is confirm that I have no authors...I have no idea how to actually add new ones.
2) Because of the lack of DB_File.pm on my server the conversion script just throws an error, so I have been unable to convert my old blogs into the new sql version of MT.
...any suggestions?
To be honest, at this point, I would be happy just to get a new blog up and running. I haven't been able to add anything to my site for a month and it's very frustrating!
I have upgraded my version of MT to 2.64 which has the conversion script in it. I altered my cfg file as per the tutorial to work with mysql and then ran the script but now have the following problems...
1) MT is telling me I have no authors and therefore won't let me log in. I have run mt-medic and all that does is confirm that I have no authors...I have no idea how to actually add new ones.
2) Because of the lack of DB_File.pm on my server the conversion script just throws an error, so I have been unable to convert my old blogs into the new sql version of MT.
...any suggestions?
To be honest, at this point, I would be happy just to get a new blog up and running. I haven't been able to add anything to my site for a month and it's very frustrating!
Well, shoot. 
Without DB_File, you are going to have problems. The only other option I can think of: if you have access to the old HTML pages, you can cut-and-paste the text for each entry (I know, I know ) into entries in a fresh install, or itno Notepad and then into a fresh install.
I'm sorry - I wish I had an easier answer!
Donna
Without DB_File, you are going to have problems. The only other option I can think of: if you have access to the old HTML pages, you can cut-and-paste the text for each entry (I know, I know ) into entries in a fresh install, or itno Notepad and then into a fresh install.I'm sorry - I wish I had an easier answer!
Donna
Hmm, if I have to do it that way I will but I cannot even login at the moment (no authors issue - posted on another topic, so don't worry about that for now!)
The latest I have from my hosting company is that they do actually have DB_File installed but that ...
Presumably they mean all the mt cgis...does that make any sense to you!?!
The latest I have from my hosting company is that they do actually have DB_File installed but that ...
QUOTE
DB_file.pm is a server file that cannot be pointed to directly. If you want to use that Perl Module, then your script needs to be placed in the Perl folder instead of the cgi-bin.
Presumably they mean all the mt cgis...does that make any sense to you!?!
Good grief, I'm a far cry from a Perl expert, but I've never heard of this. If you set the path to Perl in the first line of the cgi scripts, then that tells it where to find DB_File.pm (i.e., in the Perl directory).
Look at the error message: it's searching in all the Perl locations on your server - unless they're saying it's in a non-standard location all by its lonesome?
You ought to ask them where the Perl folder is located - I'm curious as to whether it's a path already reflected in the error message.
Maybe someone more Perl-fluent can let us in on whether this is a reasonable thing for them to say?? I'm just using my logical but uneducated brain here.
Look at the error message: it's searching in all the Perl locations on your server - unless they're saying it's in a non-standard location all by its lonesome?
You ought to ask them where the Perl folder is located - I'm curious as to whether it's a path already reflected in the error message.
Maybe someone more Perl-fluent can let us in on whether this is a reasonable thing for them to say?? I'm just using my logical but uneducated brain here.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.