Databases
StackOverflow2013
Postsdbo
POHeroku starts Thin but returns error from weBrick - Devise User Create Failure
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHeroku starts Thin but returns error from weBrick - Devise User Create Failure
    primarykey
    data
    text
    <p>When a new user registration is attempted I receive a server status code of 500 and no error is logged in Heroku. Here is the received response header:</p> <pre><code>Connection keep-alive Content-Length 728 Content-Type text/html; charset=utf-8 Date Mon, 15 Apr 2013 16:43:30 GMT Server WEBrick/1.3.1 (Ruby/1.9.2/2011-07-09) X-Runtime 0.390617 </code></pre> <p>There is a Procfile that specifies thin and Heroku starts up fine:</p> <p>Procfile</p> <pre><code>web: bundle exec thin start -p $PORT worker: bundle exec rake jobs:work </code></pre> <p>Also in my gemfile I specify ruby '1.9.3'</p> <p>Start up Log</p> <pre><code>2013-04-15T16:37:49.739237+00:00 heroku[web.1]: Starting process with command `bundle exec thin start -p 39185` (... Removed 3 warning - DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins!) 2013-04-15T16:37:55.104773+00:00 app[web.1]: &gt;&gt; Using rack adapter 2013-04-15T16:37:55.104773+00:00 app[web.1]: Connecting to database specified by DATABASE_URL 2013-04-15T16:37:57.202991+00:00 app[web.1]: &gt;&gt; Thin web server (v1.5.1 codename Straight Razor) 2013-04-15T16:37:57.202991+00:00 app[web.1]: &gt;&gt; Maximum connections set to 1024 2013-04-15T16:37:57.202991+00:00 app[web.1]: &gt;&gt; Listening on 0.0.0.0:39185, CTRL+C to stop 2013-04-15T16:37:57.931278+00:00 heroku[web.1]: State changed from starting to up </code></pre> <p>It's not just devise that is failing. Any call to any page that is not static fails. Also the response header for any static page has Server:WEBrick/1.3.1 (Ruby/1.9.2/2011-07-09). </p> <p>What additional configuration items am I missing or should I validate.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJohn Forbes
    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. POHeroku starts Thin but returns error from weBrick - Devise User Create Failure
      1. This table or related slice is empty.
      1. VTUndeletion
    2. VO
      singulars
      1. POHeroku starts Thin but returns error from weBrick - Devise User Create Failure
      1. This table or related slice is empty.
      1. VTClose
    1. COCan you please post the contents of your Gemfile? Also, did you create the app recently or is it an older application? The output of `heroku stack` would be useful.
      singulars
      1. POHeroku starts Thin but returns error from weBrick - Devise User Create Failure
      1. USEzekiel Templin
    2. COThanks for responding. I figured it out. The browser bookmark url was pointing at the wrong application in a different account. Now that my code and browser are pointing at the same thing all makes sense now.
      singulars
      1. POHeroku starts Thin but returns error from weBrick - Devise User Create Failure
      1. USJohn Forbes
 

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