Answers.Body: <p>I found the solution to my issue. The php.ini was causing another issue with my site. When I renamed it, I was able to import as expected. </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-22T22:29:26.680Z
Answers.Text: Renaming php.ini doesn't really "fix" anything, though. What it does is prevent the settings in that file from being used by the system, causing it to fall back on defaults or settings set elsewhere in the environment; on someone else's server, this might easily have no effect or make things worse. It would be more helpful to pinpoint a relevant setting like memory_limit, max_execution_time, or max_input_nesting_level to tune.
Answers.UserDisplayName: choster
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-23T02:36:02.850Z
Answers.Text: Yes, I thought of that, too, choster. For many situations, finding the root cause within the php.ini would be the way to do. In my case, the php.ini was left over from previous hosting and doesn't need to be added with my new hosting. So, I deleted it. Done.
Answers.UserDisplayName: dooley
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-22T19:31:44.020Z
Answers.LastActivityDate: 2018-06-22T19:31:44.020Z
Answers.UserDisplayName: dooley
Body: <p>Getting a 500 error on importing CSV content. Consulted with web host, who found the cause of the 500 Internal Server Error. When I click on the import more than 30 processes is spawned from my account. The limit on my plan is 30 processes and this causes the error as the limit is exceeded. The processes are:</p>
  
  <p>Code:
  php admin.php</p>
  
  <p>They advised me to contact Civi or check the import settings in order to lower the number of processes spawned simultaneously. You should configure it to wait for the process to complete and then spawn new ones. </p>
  
  <p>How do I do this? </p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-06-21T11:22:50.337Z
Comments.Text: It's almost always cheaper & easier to change hosting than to try to get CiviCRM to fit with a cheap hosting plan (which I assume is what you have) - there are a number of CiviCRM providers that provide CiviCRM-optimised hosting - some are pretty cheap
Comments.UserDisplayName: user4278
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-06-21T19:50:01.227Z
Comments.Text: That makes sense in many situations I'm sure. I'm a developer running Civi for my own education on an account with 40+ sites on it, which I won't move for the sake of Civi. I'm looking to make it work with my hosting, which is otherwise very good, rather than buying additional hosting.
Comments.UserDisplayName: dooley
Tags: <import><500>
Title: Import exceeding max. number of processes on host
ThreadText: # Import exceeding max. number of processes on host
  
  (Asked by: username_0 on 2018-06-20)
  
  Getting a 500 error on importing CSV content. Consulted with web host, who found the cause of the 500 Internal Server Error. When I click on the import more than 30 processes is spawned from my account. The limit on my plan is 30 processes and this causes the error as the limit is exceeded. The processes are:
  
  Code:
  php admin.php
  
  They advised me to contact Civi or check the import settings in order to lower the number of processes spawned simultaneously. You should configure it to wait for the process to complete and then spawn new ones.
  
  How do I do this?
  
  **Tags:** import, 500
  
  > **Comments:**
  > **username_1**: It's almost always cheaper & easier to change hosting than to try to get CiviCRM to fit with a cheap hosting plan (which I assume is what you have) - there are a number of CiviCRM providers that provide CiviCRM-optimised hosting - some are pretty cheap  
  > **username_0**: That makes sense in many situations I'm sure. I'm a developer running Civi for my own education on an account with 40+ sites on it, which I won't move for the sake of Civi. I'm looking to make it work with my hosting, which is otherwise very good, rather than buying additional hosting.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-06-22. Score: 3
  
  I found the solution to my issue. The php.ini was causing another issue with my site. When I renamed it, I was able to import as expected.
  
  > **Comments:**
  > **username_2**: Renaming php.ini doesn't really "fix" anything, though. What it does is prevent the settings in that file from being used by the system, causing it to fall back on defaults or settings set elsewhere in the environment; on someone else's server, this might easily have no effect or make things worse. It would be more helpful to pinpoint a relevant setting like memory_limit, max_execution_time, or max_input_nesting_level to tune.  
  > **username_0**: Yes, I thought of that, too, username_2. For many situations, finding the root cause within the php.ini would be the way to do. In my case, the php.ini was left over from previous hosting and doesn't need to be added with my new hosting. So, I deleted it. Done.  
  
  ---
  
  