CiviCRM Community Forums (archive)

I've spent a few days now trying to figure this one out so would appreciate some help if possible.

I'm doing a fairly simple (so I thought) task of moving a CiviCRM 1.9 installation from one server to another. As far as I can tell everything on the two servers is identical. But after I move my Joomla database to the new server and attempt to access CiviCRM in the admin back end I get the following in my apache error log and only a black page displays:

[Mon Mar 24 12:29:05 2008] [notice] child pid 30159 exit signal Segmentation fault (11)

No other errors even when I turn on php errors and set the apache logging to debug.

Here's some details:
CentOS 5.1 O/S
Apache 2.2.3
PHP 5.2
Joomla 1.0.15
civicrm-1.9.11960-joomla-php5

I just copied everything over from one server to the other and that worked fine for the joomla site but CiviCRM wasn't working so I:

uninstalled CiviCRM with the component installer
reinstalled civicrm setting the upgrade=true variable in the configure.php file

After two days of trying various things I just can't get it to work. I should mention that I did try setting upgrade=false when reinstalling CiviCRM and then everything worked fine but of course I had none of my data. If I try importing the data I run in to all the foreign key errors.

I have a feeling there might be an issue with the data itself but it does run fine on the old server and as I said things are very close between these two boxes. I've had a very good look at the collation values etc of the database and it's identical. One server is our development box and CiviCRM has run fine from it for quite some time but I've finally moved our site to the production box where it belongs and now this issue with CiviCRM.

Can anyone offer any advice on what I could try next or tests that I can run to determine the issue?

Cheers.

I double checked that the two servers are running the same version of php. They are. However, I decided to run phpinfo() to check all the settings and sure enough 'safe mode' was set to 'on' on the production server but not the development server. I changed this setting to 'off' and CiviCRM worked fine. I even managed to upgrade it from ver 1.9 to ver 2.

So thanks for the advice as it gave me the lead I needed to find the issue. I really appreciate your time.

are the php and mysql version exactly the same on the two boxes?

a segmentation fault is incredibly hard to debug But most of the times it also reproducible quite nicely in the same version. So i suspect your php version do not match in the two servers

Can you check?

Can you also enable the mysql query log and see where php is segfaulting

lobo