Segfault with Apache 2.0, PHP 5.2.1, and Roundcube 20070303 or 20070318

[rkrenzis]

I'm running FreeBSD 5.4 with the latest ports tree. I have the following installed:

php5-5.2.1_3
apache-2.0.59
roundcube-0.1-20070303

After uninstalling, and reinstalling, and RTFM'ing, and uninstalling, and reinstalling, then RTFM'ing again...I'm left with the following messages any time I try to launch the index.php page when trying to bring up Roundcube:

[Mon Apr 02 04:24:58 2007] [notice] child pid 56391 exit signal Segmentation fault (11)
[Mon Apr 02 04:24:58 2007] [notice] child pid 56390 exit signal Segmentation fault (11)
[Mon Apr 02 04:24:58 2007] [notice] child pid 56389 exit signal Segmentation fault (11)
[Mon Apr 02 04:24:59 2007] [notice] child pid 59566 exit signal Segmentation fault (11)
[Mon Apr 02 04:24:59 2007] [notice] child pid 59565 exit signal Segmentation fault (11)
[Mon Apr 02 04:34:58 2007] [notice] child pid 59569 exit signal Segmentation fault (11)
[Mon Apr 02 04:34:59 2007] [notice] child pid 59574 exit signal Segmentation fault (11)

I've tried rebuilding all PHP dependencies and PHP5 itself. I've googled and found "issues" with people running 5.2 and apache 2.x segfaulting but no resolution.

Thoughts...
Ideas...

TIA.

[[email protected]]

Not that it helps you much, but I'm running roundcubemail-nightly-20070318 under FreeBSD 5.2.1 with Apache 2.2.4 and PHP 5.2.1 (compiled from source) without issue.

[rkrenzis]

I'm going to try and upgrade to Apache 2.2 and rebuild PHP 5.2. I'll post the results.

[rkrenzis]

Removed the apache20 package
Installed the apache22 package
Fixed the package database with 'pkgdb -F' per recommendation of portupgrade
Rebuilt PHP5 for apache22

Still segfaulting at load. Ideas?

[[email protected]]

Can Apache open any .php file or is it just RC's index.php that crashes Apache? E.g. does the following, put into a .php file, crash Apache?

phpinfo()
?>

[mokr]

....
[Mon Apr 02 04:24:59 2007] [notice] child pid 59566 exit signal Segmentation fault (11)
[Mon Apr 02 04:24:59 2007] [notice] child pid 59565 exit signal Segmentation fault (11)
[Mon Apr 02 04:34:58 2007] [notice] child pid 59569 exit signal Segmentation fault (11)
[Mon Apr 02 04:34:59 2007] [notice] child pid 59574 exit signal Segmentation fault (11)

I've tried rebuilding all PHP dependencies and PHP5 itself. I've googled and found "issues" with people running 5.2 and apache 2.x segfaulting but no resolution.

Thoughts...
Ideas...

It seems that you don't have mysql-server installed on the same system.

ktrace httpd -X shows at least this
......
 84452 httpd  CALL break(0x8683000)
 84452 httpd  RET  break 0
 84452 httpd  CALL stat(0xbfbf7920,0xbfbf7880)
 84452 httpd  NAMI "/usr/local/share/mysql/charsets/Index.xml"
 84452 httpd  RET  stat -1 errno 2 No such file or directory
 84452 httpd  PSIG SIGSEGV SIG_DFL

'share/mysql/charsets' directory is within mysql-server package, just obtain it from package or another server and signal 11 goes away.

SM

[rkrenzis]

In reply to the previous two posts:

1.

phpinfo()
?>

yields the phpinfo page without errors.

2. It seems that you don't have mysql-server installed on the same system.

ktrace httpd -X shows at least this
......
 84452 httpd  CALL break(0x8683000)
 84452 httpd  RET  break 0
 84452 httpd  CALL stat(0xbfbf7920,0xbfbf7880)
 84452 httpd  NAMI "/usr/local/share/mysql/charsets/Index.xml"
 84452 httpd  RET  stat -1 errno 2 No such file or directory
 84452 httpd  PSIG SIGSEGV SIG_DFL

'share/mysql/charsets' directory is within mysql-server package, just obtain it from package or another server and signal 11 goes away.

Reply Below:

The mysql server is on the same host. A ktrace httpd -X results in a 'Segmentation fault' and apache httpd exits without showing any messages. The "/usr/local/share/mysql/charsets" directory exists. The Index.xml file exists as well.

I've upgraded to the latest 20070318 nightly build. Ideas?

[lcx]

I also have segfaults on my installation since updating to 1.2beta.
I am running Apache 2.2.3-4+etch5, php 5.2.0-8+etch13, Debian 4.0 on a adm64 machine.
The strange thin is, if I shut down apache and start it again, it works for one day (wild guess, it could also be that it works for just some requests I usually notice it not working the next day)
All other php stuff with https works fine. Any idea how to narrow it down to find out what is going on?

LE: I found my problem. eAccelerator! as soon as I empty the cache, roundcubemail works for a while.