On Friday, June 11, 2004 3:14 PM
Jamie L. Penman-Smithson
[Fri Jun 11 13:57:28 2004] [error] GATEWAY_INTERFACE not Perl! at /opt/otrs/scripts/apache2-perl-startup.pl line 5.\nCompilation failed in require at (eval 4) line 1.\n
Comment line 5 in apache2-perl-startup.pl, and add these lines after line 5: # check $ENV{MOD_PERL}, $ENV{GATEWAY_INTERFACE} is deprecated for mod_perl2 $ENV{MOD_PERL} =~ /mod_perl/ or die "MOD_PERL not used!"; Now try again.
[Fri Jun 11 13:57:28 2004] [error] Can't load Perl file: /opt/otrs/scripts/apache2-perl-startup.pl for server solaris.silverdream.org:80, exiting...
Although I realise this is not required for OTRS to run, I'm grasping at straws trying to figure out what's going wrong beyond a blanket segfault. Apache segfaulting each time points to a problem with OTRS but I still
Where is your Perl located? Isn't that at a different location than /usr/bin/perl, say: /usr/local/bin/perl? If so, you should create a link in /usr/bin, pointing to the real location. Alternatively, you may change every bingbang line. These are about 60.
can't find any log entries (I checked in /opt/otrs/var/log/...) to suggest what is going wrong...
Logging goes to syslog usually. These options (=> Config.pm) let you basically change this: # (log backend module) # $Self->{LogModule} = 'Kernel::System::Log::SysLog'; $Self->{LogModule} = 'Kernel::System::Log::File'; # param for LogModule Kernel::System::Log::SysLog # $Self->{'LogModule::SysLog::Facility'} = 'user'; # param for LogModule Kernel::System::Log::File (required!) $Self->{'LogModule::LogFile'} = '/tmp/otrs.log';
Any help would be really appreciated, specifically, are there any debug options for otrs, I checked the docs but that section has yet to be written :)
You may switch on Debugging in many modules. If it would make sense (ie. if it were implemented in the module's code), you will find s.th. like the following towards the head of the file bearing the module: $Self->{Debug} = 0; Atm, this is true for these files: $ grep -lr "\$Self->{Debug} = [0-9]" . ./Kernel/Config/Defaults.pm ./Kernel/Config/.Defaults.pm ./Kernel/Language.pm ./Kernel/Output/HTML/Generic.pm ./Kernel/System/CheckItem.pm ./Kernel/System/Auth/DB.pm ./Kernel/System/Auth/LDAP.pm ./Kernel/System/Auth/HTTPBasicAuth.pm ./Kernel/System/Encode.pm ./Kernel/System/Spelling.pm ./Kernel/System/AuthSession/DB.pm ./Kernel/System/AuthSession/FS.pm ./Kernel/System/AuthSession/IPC.pm ./Kernel/System/CustomerAuth/DB.pm ./Kernel/System/CustomerAuth/LDAP.pm ./Kernel/System/CustomerAuth/HTTPBasicAuth.pm ./Kernel/System/Time.pm ./Kernel/Config.pm Or even: $Self->{Debug} = $Param{Debug} || 0; This instructs the module to inherit the setting from Config.pm. These do so: $ grep -lr "\$Self->{Debug} = [^0-9]" . ./Kernel/Modules/Not4Me.pm ./Kernel/System/DB.pm ./Kernel/System/EmailParser.pm ./Kernel/System/PostMaster.pm ./Kernel/System/Ticket.pm ./Kernel/System/PostMaster/Filter/Match.pm ./Kernel/System/PostMaster/Filter/CMD.pm ./Kernel/System/PostMaster/Filter/MatchDBSource.pm ./Kernel/System/PostMaster/DestQueue.pm ./Kernel/System/PostMaster/FollowUp.pm ./Kernel/System/PostMaster/NewTicket.pm As you see above, you may set this paramter in Config.pm to be valid for a numerous modules. But watch out, enabling Debug in Config.pm may lead to the server no longer responding due to the enormous amount of data being logged then. So it's safest to enable Debugging per module (and switch it off when done, btw). You may use any value above 0 - the higher the value, the higher the amount of information. Most modules do only ask for having Debug > 0, but it won't be unlikely we implement some kind of levelling someday. So using a value of 9 should always show the maximum atow. I hope this helps a bit, Robert Kehl -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Tel. +49 (0)6172 4832388