Segmentation Fault on Debian Sarge with PHP 5.1.2

[kgt]

I ran into segmentation fault problems left and right when trying to run on RedHat and derivatives, and indications seemed to me that packaged RPMs from RedHat were the problem, and threads in this forum agree with me. I switched to Debian. I compiled PHP myself. I started running into segmentation faults, only now I was getting them when I even tried just logging in to Sugar. At least before I was having issues only on opportunities edit and user management.

When I set up the current machine, I made sure to install recommended versions of everything (Sugar v 4.2.1). Relevant version info:

crm:~# mysql -V
mysql Ver 14.12 Distrib 5.0.24, for pc-linux-gnu (i686) using readline 5.0
crm:~# apachectl -v
Server version: Apache/2.0.59
Server built: Aug 25 2006 12:54:42
crm:~# php -v
PHP 5.1.2 (cli) (built: Aug 29 2006 11:52:54)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies

I am in the process of upgrading mysql, apache, and PHP for sugar 4.5.0 so I can test with newest version, but I'm afraid it may be a waste of time. I have found mention that the problem stems from issues in precompiled packages shipped with RedHat. What exactly was the problem, and how do I avoid it when I compile myself?

[jlanawalt]

I don't have answers for your questions, but I can confirm that the following setup works without segfaults on this different Debian 3.1 setup:

Debian 3.1 (Sarge)
mysql-server-4.1 4.1.11a-4sarge7
php4 4.3.10-16
apache 1.3.33-6sarge3
libapache-mod-php4 4.3.10-16
SugarCRM 4.5.0f (Build 1202)

What worker model are you using with Apache2? Have you tried prefork?

Debian's libapache2-mod-php5 package specifically states that is is not compiled thread-safe and must be used with prefork. If you aren't using the module feature but using PHP as a CGI then that may not matter.

[simple]

Hi

we are using the same deps as Jacob and it works without any problems, although PHP 4.3.11 is required.

Actually we noticed one problem in Studio, displaying history versions which might be because of 4.3.10. But I'm not sure and it's not a must have feature (at the moment). see http://www.sugarcrm.com/forums/showthread.php?t=18322

[kgt]

Thanks for the response. Apache, PHP and MySQL are all custom compiled, so I'm not using a package. Apache is compiled prefork, and PHP is installed as an apache module, not CGI.

This setup did work for Sugar for about a week before problems began.


crm:~/httpd-2.0.59# httpd -V
Server version: Apache/2.0.59
Server built: Aug 25 2006 12:54:42
Server's Module Magic Number: 20020903:12
Server loaded: APR 0.9.12, APR-UTIL 0.9.12
Compiled using: APR 0.9.12, APR-UTIL 0.9.12
Architecture: 32-bit
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/prefork"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_SYSVSEM_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D HTTPD_ROOT="/usr/local/apache2"
-D SUEXEC_BIN="/usr/local/apache2/bin/suexec"
-D DEFAULT_PIDLOG="logs/httpd.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_LOCKFILE="logs/accept.lock"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf"


Did your working setup come from debian.org/distrib/packages or did you get any packages from elsewhere?

[simple]

We installed only packages from debian.org (and mirrors), starting with Debian 3.1 r3 CD 1

[jlanawalt]

All the packages I listed are official Debian packages. "It just works" (tm). I haven't tried it with an apache2 setup.