CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • Drupal Installations (Moderator: Piotr Szotkowski) »
  • migration woes
Pages: [1]

Author Topic: migration woes  (Read 1388 times)

case

  • I’m new here
  • *
  • Posts: 13
  • Karma: 1
migration woes
March 23, 2008, 06:57:36 pm
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.

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: migration woes
March 24, 2008, 12:24:29 pm
Have you verified that the $civicrm_root and CIVICRM_UF_BASEURL values are set properly for your new install location in both copies civicrm.settings.php (the admin and front-end copies)?

Another thing to look at / try is setting the value of civicrm_domain.config_backend to NULL in your new install's DB. This column holds a number of configuration settings which are server location specific - and CiviCRM will assign new defaults if the column is empty.
Protect your investment in CiviCRM by  becoming a Member!

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • Drupal Installations (Moderator: Piotr Szotkowski) »
  • migration woes

This forum was archived on 2017-11-26.