Apache keeps restarting after updating to OTRS 4

[TheRon]

Hello, the Apache service keeps restarting automatically after I updated to OTRS 4 last week. See below a part of the apache logs:

[Mon Dec 29 11:02:05 2014] [notice] Parent: child process exited with status 255 -- Restarting.
[Mon Dec 29 11:02:05 2014] [warn] module perl_module is already loaded, skipping
[Mon Dec 29 11:02:08 2014] [warn] module perl_module is already loaded, skipping
[Mon Dec 29 11:02:10 2014] [warn] pid file C:/otrs/Apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Dec 29 11:02:10 2014] [notice] Apache/2.2.25 (Win32) mod_perl/2.0.4 Perl/v5.12.3 configured -- resuming normal operations
[Mon Dec 29 11:02:10 2014] [notice] Server built: Jul 10 2013 01:52:12
[Mon Dec 29 11:02:10 2014] [notice] Parent: Created child process 4908
[Mon Dec 29 11:02:10 2014] [warn] module perl_module is already loaded, skipping
[Mon Dec 29 11:02:13 2014] [warn] module perl_module is already loaded, skipping
[Mon Dec 29 11:02:15 2014] [notice] Child 4908: Child process is running
[Mon Dec 29 11:02:15 2014] [notice] Child 4908: Acquired the start mutex.
[Mon Dec 29 11:02:15 2014] [notice] Child 4908: Starting 64 worker threads.
[Mon Dec 29 11:02:15 2014] [notice] Child 4908: Starting thread to listen on port 80.

Does someone have an idea on where I should start looking to fix this problem?

[TheRon]

Some additional info on this, I suspect the problem to be in httpd.conf of Apache. The OTRS configuration in Apache's httpd.conf looks now like this:

# ---
# OTRS configuration
# ---

# load modules for OTRS
LoadModule deflate_module modules/mod_deflate.so
LoadModule headers_module modules/mod_headers.so

LoadFile "C:\otrs\StrawberryPerl\perl\bin\perl512.dll"
LoadModule perl_module modules/mod_perl.so
LoadModule perl_module modules/mod_perl-2.0.so
LoadModule apreq_module modules/mod_apreq2.so

# include the OTRS configuration
Include 'C:/otrs/OTRS/scripts/apache2-httpd.include.conf'

# redirect / to the Agent interface
# just use customer.pl if you want the Customer interface as default
RedirectMatch ^/$ /otrs/index.pl

The part in bold was outcommented in the previous version of OTRS (3.2.9). If I leave it outcommented, I get a "Internal Server Error
" in the browser, the error log of Apache says:

[Tue Dec 30 09:33:45 2014] [error] [client 127.0.0.1] (OS 2)The system cannot find the file specified. : couldn't create child process: 720002: index.pl
[Tue Dec 30 09:33:45 2014] [error] [client 127.0.0.1] (OS 2)The system cannot find the file specified. : couldn't spawn child process: C:/otrs/OTRS/bin/cgi-bin/index.pl

[viorelme]

Causes and symptoms
We encountered this error after installing the 4.0 version of OTRS. When those lines were not commented in httpd.conf:

Code: Select all

LoadFile 'D:/otrs/StrawberryPerl/perl/bin/perl512.dll'
LoadModule perl_module modules/mod_perl.so
LoadModule apreq_module modules/mod_apreq2.so

The pages, tickets, everything opened, but we would randomly get a restart of Apache, usually too often to make it usable. Then we figured commenting those lines, but this caused these errors to appear:
[Thu Mar 05 12:02:59 2015] [error] [client 127.0.0.1] (OS 2)The system cannot find the file specified. : couldn't create child process: 720002: index.pl
[Thu Mar 05 12:02:59 2015] [error] [client 127.0.0.1] (OS 2)The system cannot find the file specified. : couldn't spawn child process: D:/otrs/otrs/bin/cgi-bin/index.pl

This happened even when only the mod_perl.so line was commented, apparently because Apache could not find Perl.

The solution
After commenting the lines in httpd.conf:

Code: Select all

#LoadFile 'D:/otrs/StrawberryPerl/perl/bin/perl512.dll'
#LoadModule perl_module modules/mod_perl.so
#LoadModule apreq_module modules/mod_apreq2.so

We replaced the shebang lines in the perl files of OTRS (which is the first line in the .pl files) from:

Code: Select all

#!/usr/bin/perl

To:

Code: Select all

#!D:/otrs/StrawberryPerl/perl/bin/perl

Which is the path to the exe file of our Perl installation, please note the extra /perl in the path, that is the executable file without the .exe extension. This seems to have worked as I could not get the aforementioned exceptions after going berserk on the left mouse button, except for maybe the Apache thread limit, but this is something different.