[rt-users] DBIx::SearchBuilder Errors

[Mathew Snyder]

Trying to get a development server going using v3.6.5. The idea being
that I install that, port over a relatively recent backup of the
database and then upgrade to v3.8.6. Everything is installed: mysql,
apache, postfix, mod_perl, RT and all the necessary modules.

The database is created properly and to ensure it I logged in with the
rt user/pass.

Apache starts up with no errors.

The problem I'm having is with the dreaded Internal Server Error message
that I'm getting. Looking at the rt_error log that is being generated
I'm seeing:

[Mon Dec 07 22:00:27 2009] [error] [client 192.168.4.208] Unable to load
DBIx::SearchBuilder database handle for 'mysql'.\nPerhaps you've picked
an invalid database type or spelled it incorrectly.\nCan't locate
DBIx/SearchBuilder/Handle/mysql.pm in @INC (@INC contains:
/opt/rt3/local/lib /opt/rt3/lib
/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7
/usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5
/usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7
/usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5
/usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi
/usr/lib/perl5/5.8.8 . /etc/httpd) at (eval 242) line 1.\nBEGIN
failed--compilation aborted at (eval 242) line 1.\nCompilation failed in
require at /opt/rt3/lib/RT.pm line 216.\n

I've verified that DBIx::SearchBuilder::mysql resides at
/usr/lib/perl5/site_perl/5.8.8/DBIx/SearchBuilder/Handle/mysql.pm

I've also verified that RT_SiteConfig.pm holds the proper DB name, DB
user/pass and has been configured with our org. name.

So what might the problem be? The module is there, the servers are
configured. I'm at a loss.

-Mathew