[Resolved] Apache2 segmentation fault on MODx manager login

Hi All,

I’am dealing with a annoying issue here: Apache2 gets an segmentation fault (according to apache error.log) every time one uses the manager for login. The user expierences a very long login period...one could almost drink a cup of coffee before login is through. (Apache is being restarted i assume). It’s only on the manager login part. The rest of the site is running smooth...even the backend is running smooth once logged in. (For as far as i know on this moment).

The problem first occured when i moved my MODx .htaccess directives from .htaccess to my apache2.conf.

I’am certain the issue is related to the Rewrite directives. (With the Rewrite directives commented out the issue is gone).

Anyone familiair with this problem ? Any suggestions on how to modify the apache2.conf ? (I would prefer the apache directives in my apache2.conf rather than in an .htaccess file).

My current configuration is below:

Apache/2.0.55 (Ubuntu) PHP/5.1.2 MySQL 5.0.22-Debian_0ubuntu6.06

<Directory /var/www/>
<LimitExcept GET POST>
deny from all
</LimitExcept>

Options FollowSymLinks
php_flag zlib.output_compression On
php_value zlib.output_compression_level 5

Redirect /administrator http://<server ip>/manager

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule ^(.*)$ /index.php?q=$1 [L,QSA]

</Directory>

Thanks !!

The manager folder should actually have the rewrite engine off. There’s another htaccess file there.

Ryan, thanks for your reply ! I’ve overlooked  the different .htaccess file in the manager directory.
I’ve changed my apache2.conf file to RewriteEngine Off for the manager directory. However te problem is still there...

The concerning directory lines in my apache2 file now read this:

<Directory /var/www/>
        <LimitExcept GET POST>
                deny from all
        </LimitExcept>

        Options FollowSymLinks
        php_flag zlib.output_compression On
        php_value zlib.output_compression_level 5

        Redirect /administrator http://<server ip>/manager

        RewriteEngine On
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d

        RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

</Directory>

<Directory /var/www/manager>

        <Limit GET>
                Order deny,allow
                Deny from all
                Allow from <client ip>
                Allow from <client ip>
                Allow from <client ip>
                Allow from <client ip>
                Allow from <client ip>
        </Limit>

        RewriteEngine Off

</Directory>

However this doesn’t fix te problem.

On two Ubuntu server systems running MODx i keep facing the problem:

Tue Nov 07 16:12:43 2006] [notice] child pid 7190 exit signal Segmentation fault (11)

Notifications of a segmentation faults in the Apache2 error_log.

The concerning Apache2 versions are:

apache2 2.0.55-4ubuntu2.1
apache2-mpm-prefork 2.0.55-4ubuntu2.1

On one server i used
libapache2-mod-php4 4.4.2-1build1
And on the other:
libapache2-mod-php5 5.1.2-1ubuntu3.4

I’am using the ’out-of-the box’ .htaccess files shipped with MODx except for one line: Allow Override All (For the use of .htaccess files).

Because of the segmentation faults page loading time is seriously increased. Because both servers are ’a little bit aged’ (a PII 400 en a Cel. 400) the increased page loading time is quite noticable.

On a Pentium D is very little loading time noticable because of the high processing speed. The segmentation faults are there however!

Today i’ve compiled Apache 2.0.59 and PHP 5.2.0 from source but even in these version the problem is still there!

I’ve got the idea that the segfault’s are initiated with the processing of POST requests. (By logging on to the MODx manager for instance).

Are some people over here familiar with the segmentational error 11? For the people who have got access to the error_log on their servers: how do does your error_log look?

First of all, what version of MODx is this occuring with?

I test MODx on a lot of different systems, and the only time I’ve seen segmentation faults in Apache is when the system was either resolving host names using the MODx native visitor logging on Windows, or something else to do with the native visitor logging that was included in 0.9.2.x. This has been completely removed in 0.9.5.x and I’d be curious to see if that has anything to do with the problem. If you are running 0.9.5, I’m going to have to say this is likely an issue with the interaction of Apache and the PHP configuration.

I’am using MODx versions 0.9.2.1 and 0.9.2.2.

I’ll try 0.9.5 and will report what happens..

Problem solved with 0.9.5 RC2!!! Thanks for the tip OpenGeek!! No more segfault 11’s!