Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dyno does not live long #70

Closed
rlimberger opened this issue Apr 2, 2016 · 15 comments
Closed

dyno does not live long #70

rlimberger opened this issue Apr 2, 2016 · 15 comments

Comments

@rlimberger
Copy link

Hi, I'm using boarding on 2 free dynos. when i first deploy them they are fine for a few days. after that, they seem dead and i get this (attached image). I'm sure there is something I'm missing, as I'm not that familiar with heroku. Any suggestions what might cause this? Thanks.

screen shot 2016-04-02 at 10 52 19 am

@rlimberger rlimberger changed the title dyne does not live long dyno does not live long Apr 2, 2016
@KrauseFx
Copy link
Member

KrauseFx commented Apr 3, 2016

Can you look at the look on your server? You'll find more information about the error there

@adcooley
Copy link

adcooley commented Apr 8, 2016

I'm seeing an application error as well, and considering my lack of familiarity with heroku dynos, I imagine it's related.

My logs are:

2016-04-08T09:02:16.014169+00:00 heroku[worker.1]: Starting process with command bundle exec rake jobs:work
2016-04-08T09:02:16.591837+00:00 heroku[worker.1]: State changed from starting to up
2016-04-08T09:02:17.112456+00:00 app[web.1]: Successfully created tester XX@XX.com
2016-04-08T09:02:17.113168+00:00 app[web.1]: Addding tester to application
2016-04-08T09:02:17.986206+00:00 app[web.1]: Done
2016-04-08T09:02:19.609645+00:00 app[worker.1]: rake aborted!
2016-04-08T09:02:19.609672+00:00 app[worker.1]: Don't know how to build task 'jobs:work' (see --tasks)
2016-04-08T09:02:19.609911+00:00 app[worker.1]:
2016-04-08T09:02:19.609953+00:00 app[worker.1]: (See full trace by running task with --trace)
2016-04-08T09:02:20.383394+00:00 heroku[worker.1]: Process exited with status 1
2016-04-08T09:02:20.409419+00:00 heroku[worker.1]: State changed from up to crashed
2016-04-08T09:02:44.162415+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=POST path="/submit" host=XXXX request_id=d29c8fd4-1cfb-4a34-8674-af8e1522974c fwd="73.170.198.14" dyno=web.1 connect=1ms service=30001ms status=503 bytes=0

It does indeed submit the invite, but not exactly a great experience getting an application error :D

@timothygorer
Copy link

I just got this error as well. Apple locked my Apple ID saying someone from Virginia just signed in – I'm thinking that's the script signing in and Apple thinks it's a hacker. How do we resolve this? I know I resolved it on my end by typing in a 6 digit pin they gave me, but how do I resolve it on the script's end? I really hope I can get this working again.

@KrauseFx
Copy link
Member

@lghstim You didn't share any information about your setup, output or stack trace. Please do so, so we can help you. This is probably related to 2 step verification

@timothygorer
Copy link

@KrauseFx pretty much what I did was press the "Deploy to Heroku" button and typed in my iTunes Connect username and password and my App's bundle ID. Boarding worked for 2 days but then I got the same error as @rlimberger did. A few minutes later Apple locked me out of iTunes connect and told me someone from Virginia tried to login. I don't have 2-step verification enabled. Sorry, but I don't really know where to find my stack trace since this is my first time using Heroku.

@machinefixer
Copy link

Same issue. @lghstim Did you find the solution? After my Apple ID locked, Apple ask me reset account password, then I shutdown the Boarding app on Heroku

@avazquezpr
Copy link

For now, the only way to bypass this is to turn off Apple's Two-Factor Authentication...

@owencarp
Copy link

owencarp commented Dec 5, 2016

Is there a workaround for this @KrauseFx ? I do not have two factor authentication enabled on my Apple ID however I noticed this behavior after a few days (set up on Friday worked fine, see the error on Monday)

I am not a Heroku expert and simply deployed from the button on the GitHub readme.

I'd really like to use this service but this is a major issue.

This is the error I see repeatedly in my logs

2016-12-05T18:28:30.568631+00:00 app[web.1]: Started GET "/" for 136.1.1.109 at 2016-12-05 18:28:30 +0000
2016-12-05T18:28:30.569430+00:00 app[web.1]: Processing by InviteController#index as HTML
2016-12-05T18:28:32.033248+00:00 app[web.1]: Completed 500 Internal Server Error in 1464ms
2016-12-05T18:28:32.033794+00:00 app[web.1]:
2016-12-05T18:28:32.033796+00:00 app[web.1]: Spaceship::TunesClient::ITunesConnectError (there is no web session to update):
2016-12-05T18:28:32.033797+00:00 app[web.1]: app/controllers/invite_controller.rb:164:in login' 2016-12-05T18:28:32.033798+00:00 app[web.1]: app/controllers/invite_controller.rb:143:in app'
2016-12-05T18:28:32.033799+00:00 app[web.1]: app/controllers/invite_controller.rb:155:in block in app_metadata' 2016-12-05T18:28:32.033799+00:00 app[web.1]: app/controllers/invite_controller.rb:153:in app_metadata'
2016-12-05T18:28:32.033800+00:00 app[web.1]: app/controllers/invite_controller.rb:168:in `set_app_details'

This is different from the invalid request body errors I saw others having. Not sure what to make of "There is no web session to update", looks like on Nov 2 a bunch of users had this issue but seems to be related to ITC being down.

I can still access ITC dashboard with my Apple ID credentials...

@alex-dorokhov
Copy link

I have the same issue as @owencarp from today with the same log.
I have tried to reset heroku db (with heroku pg:reset DATABASE) and restart all dynos, but it didn't help.

@f1yingbanana
Copy link

I just ran into this issue as well. I had luck for 2 weeks before I got this.

@mafellows
Copy link

I'm seeing this issue as well.

 Spaceship::TunesClient::ITunesConnectError (there is no web session to update):
2016-12-08T17:34:09.649186+00:00 app[web.1]:   app/controllers/invite_controller.rb:164:in `login'
2016-12-08T17:34:09.649187+00:00 app[web.1]:   app/controllers/invite_controller.rb:143:in `app'
2016-12-08T17:34:09.649187+00:00 app[web.1]:   app/controllers/invite_controller.rb:155:in `block in app_metadata'
2016-12-08T17:34:09.649188+00:00 app[web.1]:   app/controllers/invite_controller.rb:153:in `app_metadata'
2016-12-08T17:34:09.649189+00:00 app[web.1]:   app/controllers/invite_controller.rb:168:in `set_app_details'

@KrauseFx
Copy link
Member

KrauseFx commented Dec 8, 2016

Please update to the latest version, this is not related to the original issue, but with a new version of spaceship

@owencarp
Copy link

owencarp commented Dec 8, 2016

@KrauseFx killed and re-deployed my application through the link the Readme and it is working! Thanks for the quick fix guys.

@s2imon
Copy link

s2imon commented May 23, 2017

Hey Felix, I think I've run into a similar problem that I'm not able to currently understand. Since I'm running the latest version, are you able to shed some light on this for me? Edit: @KrauseFx confirm updating to the latest vs fixes this issue.

2017-05-23T05:50:36.313361+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/bin/puma:22:in `load'
2017-05-23T05:50:36.313361+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/bin/puma:22:in `<top (required)>'
2017-05-23T05:52:15.449818+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mydictionaryapp.herokuapp.com request_id=b43d371f-2e31-4edd-991e-fcd0232a41a7 fwd="184.75.208.210" dyno= connect= service= status=503 bytes= protocol=https
2017-05-23T06:22:15.599683+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mydictionaryapp.herokuapp.com request_id=5e6c87ab-a4da-4e22-8804-165da19ffa10 fwd="209.126.120.29" dyno= connect= service= status=503 bytes= protocol=https
2017-05-23T06:52:15.312907+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mydictionaryapp.herokuapp.com request_id=bf9402a5-0bee-4935-b8fe-e8f7706b244d fwd="85.93.93.124" dyno= connect= service= status=503 bytes= protocol=https
2017-05-23T07:15:28.975287+00:00 heroku[web.1]: State changed from crashed to starting
2017-05-23T07:15:32.722231+00:00 heroku[web.1]: Starting process with command `bundle exec puma -C config/puma.rb`
2017-05-23T07:15:34.713656+00:00 app[web.1]: [4] Puma starting in cluster mode...
2017-05-23T07:15:34.713677+00:00 app[web.1]: [4] * Version 3.8.2 (ruby 2.3.4-p301), codename: Sassy Salamander
2017-05-23T07:15:34.713678+00:00 app[web.1]: [4] * Min threads: 5, max threads: 5
2017-05-23T07:15:34.713679+00:00 app[web.1]: [4] * Environment: production
2017-05-23T07:15:34.713679+00:00 app[web.1]: [4] * Process workers: 2
2017-05-23T07:15:34.713680+00:00 app[web.1]: [4] * Preloading application
2017-05-23T07:15:38.506040+00:00 heroku[web.1]: Process exited with status 1
2017-05-23T07:15:38.515076+00:00 heroku[web.1]: State changed from starting to crashed
2017-05-23T07:15:38.400265+00:00 app[web.1]: Spaceship::TunesClient::ITunesConnectError: there is no web session to update
2017-05-23T07:15:38.400267+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/tunes/tunes_client.rb:222:in `handle_itc_response'
2017-05-23T07:15:38.400197+00:00 app[web.1]: bundler: failed to load command: puma (/app/vendor/bundle/ruby/2.3.0/bin/puma)
2017-05-23T07:15:38.400267+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/tunes/tunes_client.rb:94:in `team_id='
2017-05-23T07:15:38.400065+00:00 app[web.1]: [4] ! Unable to load application: Spaceship::TunesClient::ITunesConnectError: there is no web session to update
2017-05-23T07:15:38.400268+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/tunes/tunes_client.rb:121:in `select_team'
2017-05-23T07:15:38.400269+00:00 app[web.1]:   /app/app/services/boarding_service.rb:76:in `ensure_values'
2017-05-23T07:15:38.400270+00:00 app[web.1]:   /app/app/services/boarding_service.rb:32:in `initialize'
2017-05-23T07:15:38.400270+00:00 app[web.1]:   /app/config/initializers/services.rb:1:in `new'
2017-05-23T07:15:38.400271+00:00 app[web.1]:   /app/config/initializers/services.rb:1:in `<top (required)>'
2017-05-23T07:15:38.400272+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in `load'
2017-05-23T07:15:38.400273+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in `block in load'
2017-05-23T07:15:38.400273+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:240:in `load_dependency'
2017-05-23T07:15:38.400275+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:652:in `block in load_config_initializer'
2017-05-23T07:15:38.400274+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in `load'
2017-05-23T07:15:38.400276+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:166:in `instrument'
2017-05-23T07:15:38.400276+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:651:in `load_config_initializer'
2017-05-23T07:15:38.400277+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:616:in `block (2 levels) in <class:Engine>'
2017-05-23T07:15:38.400278+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:615:in `each'
2017-05-23T07:15:38.400279+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:615:in `block in <class:Engine>'
2017-05-23T07:15:38.400279+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:30:in `instance_exec'
2017-05-23T07:15:38.400280+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:30:in `run'
2017-05-23T07:15:38.400281+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:55:in `block in run_initializers'
2017-05-23T07:15:38.400281+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:228:in `block in tsort_each'
2017-05-23T07:15:38.400282+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
2017-05-23T07:15:38.400283+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:422:in `block (2 levels) in each_strongly_connected_component_from'
2017-05-23T07:15:38.400283+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:431:in `each_strongly_connected_component_from'
2017-05-23T07:15:38.400284+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:421:in `block in each_strongly_connected_component_from'
2017-05-23T07:15:38.400285+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:44:in `each'
2017-05-23T07:15:38.400285+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:44:in `tsort_each_child'
2017-05-23T07:15:38.400286+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:415:in `call'
2017-05-23T07:15:38.400287+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:415:in `each_strongly_connected_component_from'
2017-05-23T07:15:38.400287+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:349:in `block in each_strongly_connected_component'
2017-05-23T07:15:38.400288+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:347:in `each'
2017-05-23T07:15:38.400288+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:347:in `call'
2017-05-23T07:15:38.400289+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:347:in `each_strongly_connected_component'
2017-05-23T07:15:38.400290+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:226:in `tsort_each'
2017-05-23T07:15:38.400290+00:00 app[web.1]:   /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/tsort.rb:205:in `tsort_each'
2017-05-23T07:15:38.400291+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:54:in `run_initializers'
2017-05-23T07:15:38.400292+00:00 app[web.1]:   /app/config/environment.rb:5:in `<top (required)>'
2017-05-23T07:15:38.400292+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:352:in `initialize!'
2017-05-23T07:15:38.400293+00:00 app[web.1]:   config.ru:3:in `require'
2017-05-23T07:15:38.400294+00:00 app[web.1]:   config.ru:3:in `block in <main>'
2017-05-23T07:15:38.400295+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/builder.rb:55:in `instance_eval'
2017-05-23T07:15:38.400296+00:00 app[web.1]:   config.ru:in `new'
2017-05-23T07:15:38.400295+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/builder.rb:55:in `initialize'
2017-05-23T07:15:38.400297+00:00 app[web.1]:   config.ru:in `<main>'
2017-05-23T07:15:38.400297+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/builder.rb:49:in `eval'
2017-05-23T07:15:38.400307+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/builder.rb:49:in `new_from_string'
2017-05-23T07:15:38.400308+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/rack-1.6.5/lib/rack/builder.rb:40:in `parse_file'
2017-05-23T07:15:38.400308+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/lib/puma/configuration.rb:313:in `load_rackup'
2017-05-23T07:15:38.400309+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/lib/puma/configuration.rb:242:in `app'
2017-05-23T07:15:38.400310+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/lib/puma/runner.rb:138:in `load_and_bind'
2017-05-23T07:15:38.400310+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/lib/puma/cluster.rb:391:in `run'
2017-05-23T07:15:38.400311+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/lib/puma/launcher.rb:172:in `run'
2017-05-23T07:15:38.400312+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/lib/puma/cli.rb:77:in `run'
2017-05-23T07:15:38.400312+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.8.2/bin/puma:10:in `<top (required)>'
2017-05-23T07:15:38.400313+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/bin/puma:22:in `load'
2017-05-23T07:15:38.400330+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/bin/puma:22:in `<top (required)>'
2017-05-23T07:22:15.596412+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mydictionaryapp.herokuapp.com request_id=33de56e4-523f-4a47-b3fc-82495470d16d fwd="173.254.206.242" dyno= connect= service= status=503 bytes= protocol=https
2017-05-23T07:40:19.742198+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mydictionaryapp.herokuapp.com request_id=67c56961-04a0-4b6f-b24f-b7aaf32972af fwd="31.10.155.229" dyno= connect= service= status=503 bytes= protocol=http
2017-05-23T07:40:22.701507+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mydictionaryapp.herokuapp.com request_id=d7f23ece-06bb-4c53-bfc7-cbc9e27cef40 fwd="31.10.155.229" dyno= connect= service= status=503 bytes= protocol=http

thanks a bunch!

@KrauseFx
Copy link
Member

@s2imon thanks for letting me know, I just pushed a new commit, please update to the most recent version 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests