I'm trying to deploy an new rails 3.0/datamapper application on heroku cedar.
Despite I can run the console and do successful "app.get ''", every request gives the following error in the logs with no backtrace:
2011-06-12T11:31:04+00:00 heroku[router]: Error H10 (App crashed) -> GET empty-samurai-701.herokuapp.com/ dyno= queue= wait= service= bytes=
A weird thing I noticed that can be related or not to my problem is that I needed to run
heroku run script/rails console
instead of
heroku run console
It was simply because I didn't add the rails gem into my Gemfile.
Related
I am trying to deploy Vue + Flask application to Heroku
On the server side the command npm run build is run and the dist folder appears containing index.html & build.js inside.
In the index.html I have <script src="/dist/build.js"></script>
But when I try to open my app all I get is blank empty page.
In the logs I see:
2020-06-29T17:04:23.211646+00:00 heroku[router]: at=info method=GET path="/dist/build.js" host=myapp.herokuapp.com request_id=some-request-id fwd="some-ip" dyno=web.1 connect=1ms service=10ms status=404 bytes=400 protocol=https
Why can't the server find the build.js inside the dist, even though I can see that it is there?
My Ruby on Rails app works fine in development on cloud9. When I push to Heroku, the application crashes immediately. 'heroku logs' shows:
2015-03-15T17:11:11.909831+00:00 heroku[web.1]: State changed from crashed to starting
2015-03-15T17:11:16.291267+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 42991 -e production`
2015-03-15T17:11:20.262015+00:00 app[web.1]: => Booting Puma
2015-03-15T17:11:20.262090+00:00 app[web.1]: => Rails 4.2.0 application starting in production on http://0.0.0.0:42991
2015-03-15T17:11:20.264853+00:00 app[web.1]: Abort testing: Your Rails environment is running in production mode!
2015-03-15T17:11:20.264972+00:00 app[web.1]: Exiting
2015-03-15T17:11:20.262130+00:00 app[web.1]: => Run `rails server -h` for more startup options
2015-03-15T17:11:20.262170+00:00 app[web.1]: => Ctrl-C to shutdown server
2015-03-15T17:11:21.206693+00:00 heroku[web.1]: State changed from starting to crashed
2015-03-15T17:11:21.193413+00:00 heroku[web.1]: Process exited with status 1
2015-03-15T17:11:22.003251+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=agile-plateau-9101.herokuapp.com request_id=2889a78c-9ccf-4583-ac2b-978683cab62e fwd="149.151.180.124" dyno= connect= service= status=503 bytes=
2015-03-15T17:11:22.536224+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=agile-plateau-9101.herokuapp.com request_id=355eeb91-1fb6-410c-a169-3407d7c2af67 fwd="149.151.180.124" dyno= connect= service= status=503 bytes=
I've tried using unicorn and puma, both with the .rb files Heroku provides, with no luck. I can't even get a console to run on Heroku. 'heroku run rails console' in the IDE shows 'Running rails console attached to terminal... up, run.9870' then brings me back to the IDE console, rather than Heroku's. The Heroku logs for the console command are:
2015-03-15T17:16:48.811613+00:00 heroku[api]: Starting process with command `rails console` by msandford#gmail.com
2015-03-15T17:16:54.386969+00:00 heroku[run.9870]: Awaiting client
2015-03-15T17:16:54.550213+00:00 heroku[run.9870]: Starting process with command `rails console`
2015-03-15T17:16:54.772282+00:00 heroku[run.9870]: State changed from starting to up
2015-03-15T17:17:01.220393+00:00 heroku[run.9870]: State changed from up to complete
2015-03-15T17:17:01.207230+00:00 heroku[run.9870]: Process exited with status 1
Any suggestions on where to begin troubleshooting this?
Edit: I've set up an Ubuntu server on EC2, and I'm getting exactly the same thing when running in development and in production. I'm using pg for both. rails s -e development runs fine, rails s -e production crashes immediately, and nothing is logged (that I can find)
I've resolved the issue: I had to comment out "require 'rails/test_help'" in environment.rd then everything ran along nicely.
My Ruby on Rails app was running smoothly until yesterday.
When ever I try to open my Heroku App it gives me a "Application Error" message and when I check my logs I get this message below.
[36m2013-09-10T17:42:34.393159+00:00 app[web.1]: [0m Connecting to database
specified by DATABASE_URL
[36m2013-09-10T17:42:34.846457+00:00 app[web.1]: [0m Exiting
[36m2013-09-10T17:42:34.849786+00:00 app[web.1]: [0m /app/vendor/bundle/ruby/2.
0.0/gems/devise-3.1.0/lib/devise/rails/routes.rb:440:in `raise_no_secret_key':
Devise.secret_key was not set. Please add the following to your Devise
initializer: (RuntimeError)
Has anyone encountered this? What does the error mean?
A discussion about that error here:
https://github.com/plataformatec/devise/issues/2554
Follow the error log instructions in your post. Add the following to your Devise initializer:
config.secret_key = '-- secret key --'
Although read many articles about this problem, I still couldn't solve those error,
Here is a part of the heroku logs, if it's less-information, I would update others code of the red mine source code.
2012-11-05T14:02:54+00:00 app[web.1]: Plugins in vendor/plugins (/app/vendor/plugins) are no longer allowed. Please, put your Redmine plugins in the `plugins` directory at the root of your Redmine directory (/app/plugins)
2012-11-05T14:02:54+00:00 app[web.1]: => Booting WEBrick
2012-11-05T14:02:54+00:00 app[web.1]: => Rails 3.2.8 application starting in production on http://0.0.0.0:40115
2012-11-05T14:02:54+00:00 app[web.1]: => Call with -d to detach
2012-11-05T14:02:54+00:00 app[web.1]: => Ctrl-C to shutdown server
2012-11-05T14:02:54+00:00 app[web.1]: Exiting
2012-11-05T14:02:55+00:00 heroku[web.1]: Process exited with status 1
2012-11-05T14:02:55+00:00 heroku[web.1]: State changed from starting to crashed
2012-11-05T14:02:56+00:00 heroku[router]: Error H10 (App crashed) -> GET ceciits.herokuapp.com/ dyno= queue= wait= service= status=503 bytes=
2012-11-05T14:06:04+00:00 heroku[web.1]: State changed from crashed to down
2012-11-05T14:06:04+00:00 heroku[web.1]: Unidling
2012-11-05T14:06:04+00:00 heroku[web.1]: State changed from down to starting
2012-11-05T14:06:07+00:00 heroku[web.1]: Starting process with command `bundle exec rails server -p 3103`
2012-11-05T14:06:12+00:00 app[web.1]: Plugins in vendor/plugins (/app/vendor/plugins) are no longer allowed. Please, put your Redmine plugins in the `plugins` directory at the root of your Redmine directory (/app/plugins)
2012-11-05T14:06:12+00:00 app[web.1]: => Booting WEBrick
2012-11-05T14:06:12+00:00 app[web.1]: => Rails 3.2.8 application starting in production on http://0.0.0.0:3103
2012-11-05T14:06:12+00:00 app[web.1]: => Call with -d to detach
2012-11-05T14:06:12+00:00 app[web.1]: => Ctrl -C to shutdown server
2012-11-05T14:06:12+00:00 app[web.1]: Exiting
2012-11-05T14:06:13+00:00 heroku[web.1]: Process exited with status 1
2012-11-05T14:06:13+00:00 heroku[web.1]: State changed from starting to crashed
I can't figure where is the reason that leads app crashed actually,
Thanks for answering...
Just out of curiosity, did you happen to generate your secret key?
Try running:
heroku run rake generate_secret_token
Not sure if it will help, but I know I've had an issue with this before.
I have upgraded a Rails 2.3.5 app to Rails 3.0.6. In the process I have also upgraded the resque from 1.9.1 to 1.15.0 and resque_scheduler from 1.9.1 to 1.9.9. The following commands used to work fine with Rails 2.3.5
COUNT=1 QUEUE=scheduled_1_queue,another_queue,yet_another_queue,slow_queue,redis_cleanup_queue,immediate_queue RAILS_ENV=development JOBS_PER_FORK=500 rake resque:workers
rake resque:scheduler
But now after the upgrade when I run above commands I get following error:
rake aborted!
wrong number of arguments (0 for 1)
Tasks: TOP => resque:work => resque:setup => environment
The RakeFile is as following:
require File.expand_path('../config/application', __FILE__)
require 'rake'
require 'resque/tasks'
require 'resque_scheduler/tasks'
MyApp::Application.load_tasks
task "resque:setup" => :environment
If i comment the last line 'task "resque:setup" => :environment' in RakeFile the resque scheduler and worker commands run without any error, but the scheduler does not schedule any tasks at all and stays on this:
2011-06-16 09:33:45 Schedule empty! Set Resque.schedule
I have also tried with older version of resque(1.9.1) and resque_scheduler(1.9.1) with Rails 3, but to no avail. I have also tried to run above commands with --trace, but it does not provide any trace info about the "wrong number of arguments (0 for 1)" error. I suspect I might need to provide more info, but don't know exactly what, please let me know what else is needed to answer this question. Thanks a lot.