Databases
StackOverflow2013
Postsdbo
PORails app crashes on Heroku but runs fine locally -> "State changed from starting to crashed"
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails app crashes on Heroku but runs fine locally -> "State changed from starting to crashed"
    primarykey
    data
    text
    <p>repo at: git@github.com:assafshomer/sample_app.git</p> <ol> <li>This app is my learning app based on Michael Hartl's excellent railstutorial.</li> <li>App runs smoothly in development and test suite is all green</li> <li>When deploying to Heroku I get the following error immediatly: "Application Error. An error occurred in the application and your page could not be served"</li> <li>The problem started after upgrading to Rails4 (but I know the problem is not Rails4 itself because, e.g. git://github.com/railstutorial/sample_app_rails_4.git deploys fine to Heroku)</li> <li>I know you are going to ask "did you migrate the db on Heroku?". I did. I even ran pg:reset and then again rake db:migrate on Heroku just in case. They seemed to have run ok.</li> </ol> <p>Heroku logs don't give any info either (at least, nothing I can see as useful)</p> <pre><code>2013-05-25T22:11:26.070468+00:00 heroku[web.1]: Process exited with status 0 2013-05-25T22:11:26.083572+00:00 heroku[web.1]: State changed from starting to crashed 2013-05-25T22:13:09.372294+00:00 heroku[run.4121]: State changed from up to complete 2013-05-25T22:13:09.357146+00:00 heroku[run.4121]: Process exited with status 1 2013-05-25T22:13:50.829887+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=devsampleapp.herokuapp.com fwd="93.172.16.63" dyno= connect= service= status=503 bytes= </code></pre> <p>also the rails console doesn't come up:</p> <pre><code>2013-05-26T06:41:34.942569+00:00 heroku[api]: Starting process with command `bin/rails console` by assafshomer@gmail.com 2013-05-26T06:41:38.312107+00:00 heroku[run.5325]: Awaiting client 2013-05-26T06:41:38.339816+00:00 heroku[run.5325]: Starting process with command `bin/rails console` 2013-05-26T06:41:39.112396+00:00 heroku[run.5325]: Client connection closed. Sending SIGHUP to all processes 2013-05-26T06:41:40.329832+00:00 heroku[run.5325]: Process exited with status 0 2013-05-26T06:41:40.357047+00:00 heroku[run.5325]: State changed from starting to complete </code></pre> <p>I submitted a support ticket with Heroku, but that will only be attended to earliest Tuesday, and I'm itching to get this "upgrade to rails4" working already, so, any help in resolving this mystery will be much appreciated.</p> <p>obviously, the best way to reproduce is to clone the repo and deploy to heroku :)</p> <p>Thanks!!</p> <p>Assaf Shomer (assafshomer at gmail)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCharles
    1. USAssaf Shomer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails app crashes on Heroku but runs fine locally -> "State changed from starting to crashed"
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORails app crashes on Heroku but runs fine locally -> "State changed from starting to crashed"
      1. USsmockle
      1. VTFavorite
    3. VO
      singulars
      1. PORails app crashes on Heroku but runs fine locally -> "State changed from starting to crashed"
      1. USNick Klius
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload