Hi All, I'm actually trying to make otrs 2.0.1 run on our Apache 2.0.54 installation with mod_perl 2.0.1 freshly installed as a loadable module. So "two dot something" everywhere. Unfortunately it fails. I've seen a couple of old posts in this mailing list archive, but so far nothing worked in my case. So, I still need to investigate, but I'd like to be sure that either otrs 2.0.1 is made for mod_perl 2 (that is, it uses the new API and not depreciated 1's functions), or if it still contains calls "a la" mod_perl 1 and needs the "PerlModule Apache2::compat" stuff, plus what I still don't know. Notice that I'm running Solaris/SPARC, but nothing was installed from some Sun's packages. They were all fresh tarballs that I compiled on the machine. Note also that otrs (which works nice in cgi mode, runs in a virtual host) Thanks for any pointer, experience sharing, etc... Best regards, Eric
Hi Eric, On Fri, Aug 12, 2005 at 04:58:06PM +0200, Eric Voisard wrote:
I'm actually trying to make otrs 2.0.1 run on our Apache 2.0.54 installation with mod_perl 2.0.1 freshly installed as a loadable module. So "two dot something" everywhere.
What's the version of CGI.pm? With mod_perl2 2.x you should use at least
CGI.pm 3.10. Also try the following settings in your apache config, that
works for me on debian unstable:
-----
ScriptAlias /otrs/ "/opt/otrs/bin/cgi-bin/"
Alias /otrs-web/ "/opt/otrs/var/httpd/htdocs/"
Perlrequire /opt/otrs/scripts/apache2-perl-startup.pl
# Apache::Reload - Reload Perl Modules when Changed on Disk
PerlModule Apache2::Reload
PerlInitHandler Apache2::Reload
PerlModule Apache2::RequestRec
Unfortunately it fails.
Are you getting error messages?
I've seen a couple of old posts in this mailing list archive, but so far nothing worked in my case.
So, I still need to investigate, but I'd like to be sure that either otrs 2.0.1 is made for mod_perl 2 (that is, it uses the new API and not depreciated 1's functions), or if it still contains calls "a la" mod_perl 1 and needs the "PerlModule Apache2::compat" stuff, plus what I still don't know.
The problem is the compartibility between mod_perl and CGI.pm amd not OTRS. Because the API of mod_perl2 changed somehwere around 1.999.x you have to use CGI.pm till 3.05, if you are using mod_perl2 1.x. With mod_perl2 2.x you should the newest CGI.pm.
Notice that I'm running Solaris/SPARC, but nothing was installed from some Sun's packages. They were all fresh tarballs that I compiled on the machine. Note also that otrs (which works nice in cgi mode, runs in a virtual host)
That should be all OK. I'd need more error messages, maybe I can help you better then. Best regards, Chistian -- ((otrs)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!
Hi Christian, Thanks for the follow-up!
On Fri, Aug 12, 2005 at 04:58:06PM +0200, Eric Voisard wrote:
I'm actually trying to make otrs 2.0.1 run on our Apache 2.0.54 installation with mod_perl 2.0.1 freshly installed as a loadable module. So "two dot something" everywhere.
What's the version of CGI.pm? With mod_perl2 2.x you should use at least CGI.pm 3.10. Also try the following settings in your apache config, that works for me on debian unstable:
I think that was it, at least partly. I've seen a notice on the mod_perl site that was saying CGI.pm 3.10 was needed. My version was older...
----- ScriptAlias /otrs/ "/opt/otrs/bin/cgi-bin/" Alias /otrs-web/ "/opt/otrs/var/httpd/htdocs/"
Perlrequire /opt/otrs/scripts/apache2-perl-startup.pl
# Apache::Reload - Reload Perl Modules when Changed on Disk PerlModule Apache2::Reload PerlInitHandler Apache2::Reload PerlModule Apache2::RequestRec
# ErrorDocument 403 /otrs/customer.pl AllowOverride None ErrorDocument 403 /otrs/index.pl SetHandler perl-script PerlResponseHandler ModPerl::Registry Options +ExecCGI PerlOptions +ParseHeaders PerlOptions +SetupEnv Order allow,deny Allow from all </Location> ...
I've been able to make it work with mod_perl2. Also, I made my httpd.conf the same as yours, but apache2-perl-startup.pl keeps failing when loaded (as it always did). Failure is: [Tue Aug 16 08:51:43 2005] [error] Can't locate object method "require_version" via package "DBI" (perhaps you forgot to load "DBI"?) at /usr/perl5/site_perl/5. 6.1/Apache/DBI.pm line 10.\nCompilation failed in require at /WWW/otrs/scripts/a pache2-perl-startup.pl line 27.\nBEGIN failed--compilation aborted at /WWW/otrs/ scripts/apache2-perl-startup.pl line 27.\nCompilation failed in require at (eval 2) line 1.\n Though, DBI is a fresh 1.48 and Apache::DBI is 0.94. Apparently everything works when I #'out apache2-perl-startup.pl.
So, I still need to investigate, but I'd like to be sure that either otrs 2.0.1 is made for mod_perl 2 (that is, it uses the new API and not depreciated 1's functions), or if it still contains calls "a la" mod_perl 1 and needs the "PerlModule Apache2::compat" stuff, plus what I still don't know.
The problem is the compartibility between mod_perl and CGI.pm amd not OTRS. Because the API of mod_perl2 changed somehwere around 1.999.x you have to use CGI.pm till 3.05, if you are using mod_perl2 1.x. With mod_perl2 2.x you should the newest CGI.pm.
Ok, I got the point. Btw, before to reach this running stage, I had to modify ./bin/cgi-bin/index.pl to not to use FindBin, and I hardcoded the lib paths with my otrs' root, as FindBin was returning '/' for actual script's path and was causing: [Tue Aug 16 10:59:28 2005] [error] Can't locate Kernel/System/Web/InterfaceAgent .pm in @INC (@INC contains: //../../Kernel/cpan-lib //../.. /usr/perl5/5.6.1/lib /sun4-solaris-64int /usr/perl5/5.6.1/lib /usr/perl5/site_perl/5.6.1/sun4-solaris -64int /usr/perl5/site_perl/5.6.1 /usr/perl5/site_perl /usr/perl5/vendor_perl/5. 6.1/sun4-solaris-64int /usr/perl5/vendor_perl/5.6.1 /usr/perl5/vendor_perl . /us r/local/apache2) at /WWW/otrs/bin/cgi-bin/index.pl line 44.\nBEGIN failed--compi lation aborted at /WWW/otrs/bin/cgi-bin/index.pl line 44.\n When ran alone from the command prompt in a test script, FindBin is returning a correct working directory... Well, my Perl install is 5.6. It's the only piece of software which is still "old" after all the chained updates I had to do. I think the best would be to update this as well, and see... It'll be after a short trip to my company's HQ, in Bad Homburg/Germany. OTRS's place it seems :-) Thanks again, Eric
participants (2)
-
Christian Schoepplein -
Eric Voisard