Answers.Body: <p>The cause of this is most likely an overloaded (very common if this is a shared hosting account) or misconfigured MySQL server.</p>
  
  <p>The installer itself should only take 10-20 seconds on 99% of hosts.  However on this one, it sits for about 120 seconds, before Apache redirects the AJAX request to:</p>
  
  <pre><code>'p' =&gt; 'internal_error.html',
  </code></pre>
  
  <p>As seen from your log files.  The underlying error is probably being logged in your Apache error logs, but it is most likely something related to a timeout from the long request.</p>
  
  <p>If I try to manually execute the SQL from a database dump that is working, removing Craft from the equation entirely, it does finish in time, but still takes about 45 seconds when it should be done in less than 10.</p>
  
  <p>I'd contact your host and ask them to check on the performance/configuration of your MySQL box.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-01T19:50:33.177Z
Answers.Text: Thanks for reporting back Brad! Is it possible to provide information like this on the "Oops" screen? As it stands now, "Oops" isn't very helpful. :)
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-01T20:00:41.247Z
Answers.Text: The problem with PHP and fatal errors like this is there isn't a graceful way to recover, much less get any information about the underlying error from PHP. They aren't normal exceptions that can be caught and dealt with in a try/catch block.
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-01T22:34:43.897Z
Answers.Text: Fair enough, that makes sense. Thanks for the explanation!
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-02T03:36:27.793Z
Answers.Text: I am troubleshooting this with the host, as they are claiming that there aren't any issues with the server that is hosting my database. So, I am not considering this answered as of the moment.
Answers.UserDisplayName: Jim Krenz
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-02T04:07:32.330Z
Answers.Text: Of course they are. :)  Which host is it?
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-02T22:49:47.553Z
Answers.Text: Dreamhost. To their credit, their servers run WordPress very well, and even Drupal adequately (and Drupal throws its weight at the database servers a lot).
Answers.UserDisplayName: Jim Krenz
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-24T17:55:52.080Z
Answers.Text: To reach closure on this: I decided to move on in my research—at this point, I need software that works gracefully on shared hosting. 
  
  The MySQL servers in question aren't overloaded or misconfigured in my experience. They have handled other software installations well—Craft is the only one to date that failed during the installation. My brief experience Craft on my local server didn't inspire me to pursue it further. I'll check in on Craft again in the future, to see its progress. Best of luck with it!
Answers.UserDisplayName: Jim Krenz
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-01T18:50:55.770Z
Answers.LastActivityDate: 2014-08-01T18:50:55.770Z
Answers.UserDisplayName: Brad Bell
Body: <p>I've uploaded the files, verified permissions and set up the database. When I run the install, I see the monkey, and I enter in my details. It appears to go well, until a screen showing only: &quot;<strong>Oops</strong>&quot;</p>
  <p>Using <a href="https://github.com/putyourlightson/craft-requirements" rel="nofollow noreferrer">Ben Croker's Craft Requirements Checker</a>, I get:</p>
  <blockquote>
  <p><strong>Success</strong></p>
  <p>Minimum requirements met. Craft can run on this server!!</p>
  </blockquote>
  <p>The server is running <strong>MySQL 5.1.56</strong> with <strong>InnoDB</strong>, so I believe it's capable of running Craft.</p>
  <p>Any advice?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-08-01T17:37:25.023Z
Comments.Text: @JimKrenz If you want to shoot some FTP/database credentials over to support@buildwithcraft.com, we can look at it and update the thread here with the results.
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-08-01T18:29:35.427Z
Comments.Text: @BradBell — Sent. Thanks for taking a look at it!
Comments.UserDisplayName: Jim Krenz
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-05-11T12:26:21.977Z
Comments.Text: Did you sort this, I'm getting the same error over and over again..
Comments.UserDisplayName: Etheya
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-06-15T04:01:58.070Z
Comments.Text: I'm also getting this on a local Windows install of **Craft 3** running WAMP. Don't have time to troubleshoot it right now, but will try post back if I figure it out.
Comments.UserDisplayName: Simon East
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-06-15T04:04:04.560Z
Comments.Text: This question is very closely related to [Does Craft have an installer error log I can check?](https://craftcms.stackexchange.com/questions/1279/does-craft-have-an-installer-error-log-i-can-check)
Comments.UserDisplayName: Simon East
Tags: <database><install>
Title: Craft install stuck on "Oops" screen
ThreadText: # Craft install stuck on "Oops" screen
  
  (Asked by: username_0 on 2014-08-01)
  
  I've uploaded the files, verified permissions and set up the database. When I run the install, I see the monkey, and I enter in my details. It appears to go well, until a screen showing only: "**Oops**"
  
  Using [Ben Croker's Craft Requirements Checker](https://github.com/putyourlightson/craft-requirements), I get:
  
  > **Success**
  >
  > Minimum requirements met. Craft can run on this server!!
  
  The server is running **MySQL 5.1.56** with **InnoDB**, so I believe it's capable of running Craft.
  
  Any advice?
  
  **Tags:** database, install
  
  > **Comments:**
  > **username_1**: @username_0 If you want to shoot some FTP/database credentials over to support@buildwithcraft.com, we can look at it and update the thread here with the results.  
  > **username_0**: @username_1 — Sent. Thanks for taking a look at it!  
  > **username_2**: Did you sort this, I'm getting the same error over and over again..  
  > **username_3**: I'm also getting this on a local Windows install of **Craft 3** running WAMP. Don't have time to troubleshoot it right now, but will try post back if I figure it out.  
  > **username_3**: This question is very closely related to [Does Craft have an installer error log I can check?](https://craftcms.stackexchange.com/questions/1279/does-craft-have-an-installer-error-log-i-can-check)  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-08-01. Score: 5
  
  The cause of this is most likely an overloaded (very common if this is a shared hosting account) or misconfigured MySQL server.
  
  The installer itself should only take 10-20 seconds on 99% of hosts. However on this one, it sits for about 120 seconds, before Apache redirects the AJAX request to:
  
  ```
  'p' => 'internal_error.html',
  
  ```
  
  As seen from your log files. The underlying error is probably being logged in your Apache error logs, but it is most likely something related to a timeout from the long request.
  
  If I try to manually execute the SQL from a database dump that is working, removing Craft from the equation entirely, it does finish in time, but still takes about 45 seconds when it should be done in less than 10.
  
  I'd contact your host and ask them to check on the performance/configuration of your MySQL box.
  
  > **Comments:**
  > **username_4**: Thanks for reporting back username_1! Is it possible to provide information like this on the "Oops" screen? As it stands now, "Oops" isn't very helpful. :)  
  > **username_1**: The problem with PHP and fatal errors like this is there isn't a graceful way to recover, much less get any information about the underlying error from PHP. They aren't normal exceptions that can be caught and dealt with in a try/catch block.  
  > **username_4**: Fair enough, that makes sense. Thanks for the explanation!  
  > **username_0**: I am troubleshooting this with the host, as they are claiming that there aren't any issues with the server that is hosting my database. So, I am not considering this answered as of the moment.  
  > **username_1**: Of course they are. :)  Which host is it?  
  > **username_0**: Dreamhost. To their credit, their servers run WordPress very well, and even Drupal adequately (and Drupal throws its weight at the database servers a lot).  
  > **username_0**: To reach closure on this: I decided to move on in my research—at this point, I need software that works gracefully on shared hosting.   The MySQL servers in question aren't overloaded or misconfigured in my experience. They have handled other software installations well—Craft is the only one to date that failed during the installation. My brief experience Craft on my local server didn't inspire me to pursue it further. I'll check in on Craft again in the future, to see its progress. Best of luck with it!  
  
  ---
  
  