CiviCRM Community Forums (archive)

Hi all. I've been trying to import into a fresh CiviCRM install, but I'm not having much luck. The import source is a database query pulling data from an ~8,000 row db table.

When I complete the mapping step, and click 'Continue', the httpd process jumps up to 100% CPU utilization, and sits there until PHP eventually times out, without ever making it to the preview step. While this is happening, it doesn't look like any queries are hitting MySQL. Also, there are no messages in the Apache error log file...

I have a fairly long PHP timeout set up - long enough that I was able to shower and return to my system before the script timed out.

I'd appreciate any thoughts on what's causing this - please let me know if there is any more information I can provide!

• CiviCRM 3.1.5
• Drupal 6.17
• MySQL 5.0.77
• PHP 5.2.10

any reason why u think its not making any queries? are u monitoring the query log?

lobo

That was based on the observation that mysql never showed up on top. It could actually be making queries, but what I intended to convey was that the load was all in httpd, not mysql.

What LAMP environment are you running on?

Shared hosting?
Dedicated hosting?
localhost (wampp, xampp, etc)

The reason I ask is because my hosting environment does the same thing, it never gets to the preview stage if the import file is fairly large. If the import file is large enough I won't even be able to pass the first step of uploading the import file.

I'm on a Rackspace clouds server. Note that this happens whatever setting I select for dupe checking.

Thanks for the responses so far, folks!

Lol,

I'm on Rackspace as well,

This issue is well documented, it is not a timeout issue but a load balancer issue. Everything times out* (or actually just switches your site to another server node) after 30 seconds because if the load balancer does not receive any html outputs. To avoid that, I have used the cron and shell_exec to do a lot of processing to avoid this system restriction.

However, if you go into your database you should see that actually the process finishes running and you will have a temporary table created in your CiviCRM DB with all the records populated. This is because even if the load balancer switches you to another node* (server), the original node should still finish run whatever script that was processing.

It is because CiviCRM import process is a multistep process that's why it doesn't work for any big import,


Read my thread here
http://forum.civicrm.org/index.php/topic,13630.0.html

And my blog post
http://civicrm.org/blogs/xcf33/scaling-contact-import-process-civicrm-perspective-and-solution


Hopefully it helps