Answers.Body: <p>It's likely environmental/configuration related and unfortunately some hosts do some things to make it really hard to debug stuff like this.</p>
  
  <p>Off the top of my head, some common ones are if you've got something like <a href="https://suhosin.org/stories/index.html" rel="nofollow">Suhosin</a> or <a href="https://www.modsecurity.org/" rel="nofollow">mod_security</a> installed, then they have their own configuration limits on top of the usual PHP/Apache limits that might be coming into play.</p>
  
  <p>Or if you're running nginx/php-fpm as a proxy in front of Apache, you might be bumping into its configuration limits.</p>
  
  <p>Or we've seen some hosts <code>&lt;cough&gt;</code>RACKSPACE<code>&lt;/cough&gt;</code> that have hard-coded execution times of 30 seconds <em>at the router/firewall level</em> and there is absolutely nothing you can do to get around it, other than the obvious thing, which is to never use Rackspace.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-28T05:23:01.743Z
Answers.LastActivityDate: 2016-07-28T05:23:01.743Z
Answers.UserDisplayName: Brad Bell
Body: <p>I am trying to export query data to a CSV file, everything works fine when I limit the number of rows to 500 (<code>$criteria-&gt;limit</code>), but when I increase it to around 530 it gives a 500 Internal Server error. I changed PHP timeout time to 300 from 30 seconds and the issue is still there. I feel like it might be a memory issue or a PHP issue. Does anyone has this happened to them, if so how could you fix it?</p>
  
Tags: <plugin-development><database>
Title: Throwing 500 error, but nothing logged in error logs or apache logs?
ThreadText: # Throwing 500 error, but nothing logged in error logs or apache logs?
  
  (Asked by: username_0 on 2016-07-28)
  
  I am trying to export query data to a CSV file, everything works fine when I limit the number of rows to 500 (`$criteria->limit`), but when I increase it to around 530 it gives a 500 Internal Server error. I changed PHP timeout time to 300 from 30 seconds and the issue is still there. I feel like it might be a memory issue or a PHP issue. Does anyone has this happened to them, if so how could you fix it?
  
  **Tags:** plugin-development, database
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-07-28. Score: 1
  
  It's likely environmental/configuration related and unfortunately some hosts do some things to make it really hard to debug stuff like this.
  
  Off the top of my head, some common ones are if you've got something like [Suhosin](https://suhosin.org/stories/index.html) or [mod\_security](https://www.modsecurity.org/) installed, then they have their own configuration limits on top of the usual PHP/Apache limits that might be coming into play.
  
  Or if you're running nginx/php-fpm as a proxy in front of Apache, you might be bumping into its configuration limits.
  
  Or we've seen some hosts `<cough>`RACKSPACE`</cough>` that have hard-coded execution times of 30 seconds *at the router/firewall level* and there is absolutely nothing you can do to get around it, other than the obvious thing, which is to never use Rackspace.
  
  
  ---
  
  