Well, I have found a simple workaround. I thought of this before but wanted to find a *real* fix. I simply created a symbolic link from the location of my mysql socket file to /tmp/mysql.sock. Everything seems to be working fine now, and the speed improvement is remarkable. Much faster! Not sure what the problem was.. why when using mod_perl2 does otrs start looking for /tmp/mysql.sock instead of what it was looking for before which I assume was the correct location of the socket, or using TCP. I suspect that it may have to do with the environment and the MYSQL_UNIX_PORT variable or lack thereof, but I don't have time to dig around through the code. I'll keep you posted if I run into any other problems. Please let me know if anyone knows how to fix this the right way. Thanks, Matt M. Matt M wrote:
Hi All,
I'm having trouble with OTRS with mod_perl 2. Thanks to looking through the archives and reading posts on the subject I was able to get this far. The problem now is that I get a DB error which follows:
<error>
Traceback: ERROR: OTRS-CGI-99 Perl: 5.8.3 OS: linux Time: Thu Nov 17 13:55:51 2005
Message: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
Traceback (23108): Module: Kernel::System::DB::new (v1.44) Line: 168 Module: Kernel::System::Web::InterfaceAgent::Run (v1.8) Line: 150 Module: ModPerl::ROOT::ModPerl::Registry::usr_local_apache2_otrs_bin_cgi_2dbin_index_2epl::handler (v) Line: 47 Module: (eval) (v1.80) Line: 203 Module: ModPerl::RegistryCooker::run (v1.80) Line: 203 Module: ModPerl::RegistryCooker::default_handler (v1.80) Line: 169 Module: ModPerl::Registry::handler (v1.99) Line: 30
</error>
[...]