Iam doing a deployment in Heroku but failed as below log. Any advise would be appreciated.
*Procfile was added:web: gunicorn app:app
*requirements witouth versions
*runtime: python==3.9.13
*flight_rf.pkl is a 560+mb (model info) file in github (should I trim the model file or just the config issue,hmm)
2022-10-24T10:56:06.842035+00:00 app[web.1]: model = pickle.load(open("flight_rf.pkl","rb"))
2022-10-24T10:56:06.842035+00:00 app[web.1]: _pickle.UnpicklingError: invalid load key, 'v'.
2022-10-24T10:56:06.842315+00:00 app[web.1]: [2022-10-24 10:56:06 +0000] [10] [INFO] Worker exiting (pid: 10)
2022-10-24T10:56:07.538013+00:00 app[web.1]: [2022-10-24 10:56:07 +0000] [4] [WARNING] Worker with pid 9 was terminated due to signal 15
2022-10-24T10:56:07.621643+00:00 app[web.1]: [2022-10-24 10:56:07 +0000] [4] [INFO] Shutting down: Master
2022-10-24T10:56:07.621731+00:00 app[web.1]: [2022-10-24 10:56:07 +0000] [4] [INFO] Reason: Worker failed to boot.
2022-10-24T10:56:07.791193+00:00 heroku[web.1]: Process exited with status 3
2022-10-24T10:56:07.880199+00:00 heroku[web.1]: State changed from up to crashed
2022-10-24T10:56:31.496146+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=nzairfare.herokuapp.com request_id=09c72ff6-67d7-47de-a02a-57173824b6ed fwd="121.75.218.134" dyno= connect= service= status=503 bytes= protocol=https
2022-10-24T10:56:31.879287+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=nzairfare.herokuapp.com request_id=efd809eb-b825-4af3-9530-6a75a28f0a17 fwd="121.75.218.134" dyno= connect= service= status=503 bytes= protocol=https
Thank you!
Related
I can successfully deploy my app cfmernportfolio to heroku, but it returns a page that just says "not found"
I tried doing the heroku restart, clearing the caches, and changed the port proxy from 5000 to 8000, but nothing worked.
When I open this site on localhost, it appears just fine. I posted the website before under cfmerportfolio, and it worked. But I had to redeploy it after making some changes to the design. That's when the errors started
Below is the link to the github
https://github.com/Bl1xvan/nodeportfolio
This is what the heroku logs say
2022-09-08T20:50:50.913239+00:00 app[web.1]:
2022-09-08T20:50:50.913255+00:00 app[web.1]: > nodeportfolio#1.0.0 start
2022-09-08T20:50:50.913255+00:00 app[web.1]: > node index.js
2022-09-08T20:50:50.913256+00:00 app[web.1]:
2022-09-08T20:50:51.352016+00:00 app[web.1]: server is listening on port 20867...
2022-09-08T20:50:51.591682+00:00 heroku[web.1]: State changed from starting to up
2022-09-08T20:50:52.478564+00:00 heroku[router]: at=info method=GET path="/" host=cfmernportfolio.herokuapp.com request_id=aee12ac1-d244-45af-8978-2909cdd05e14 fwd="98.109.162.218" dyno=web.1 connect=0ms service=9ms status=400 bytes=216 protocol=https
2022-09-08T20:50:52.620136+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=cfmernportfolio.herokuapp.com request_id=31c03a90-0faa-40ea-8e74-66f614af7ab4 fwd="98.109.162.218" dyno=web.1 connect=0ms service=2ms status=400 bytes=216 protocol=https
2022-09-08T21:07:58.809104+00:00 heroku[router]: at=info method=GET path="/" host=cfmernportfolio.herokuapp.com request_id=9b493df4-b6db-4c5a-b079-f5ab29af27d3 fwd="98.109.162.218" dyno=web.1 connect=0ms service=2ms status=400 bytes=216 protocol=https
2022-09-08T21:08:00.169483+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=cfmernportfolio.herokuapp.com request_id=853a5c8e-3c92-4a8a-b810-861ea6877df3 fwd="98.109.162.218" dyno=web.1 connect=0ms service=4ms status=400 bytes=216 protocol=https
Im trying to deploy my python code on Heroku using GitHub Desktop,
i also have have .json on the files btw
[requirements]
discord.py
[Procfile]
worker : python economia.py
HEROKU ERROR:
-----> App not compatible with buildpack: https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku/python.tgz
More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure
! Push failed
updated with new files:
[githbu files] (https://github.com/richcipriano/billionaireboysclub)
UPDATED HEROKU LOG:
2020-08-30T20:51:18.764302+00:00 app[api]: Release v13 created by user mallkz#hotmail.com
2020-08-30T20:51:27.000000+00:00 app[api]: Build succeeded
2020-08-30T20:53:55.070715+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=billionaireboysclub.herokuapp.com request_id=d0cb7997-13a0-4e27-945e-6f04d471f5e7 fwd="107.184.213.12" dyno= connect= service= status=503 bytes= protocol=https
2020-08-30T20:53:55.776349+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=billionaireboysclub.herokuapp.com request_id=64a55a40-5c9e-4c9e-b351-9120b8d87e1a fwd="107.184.213.12" dyno= connect= service= status=503 bytes= protocol=https
2020-08-30T20:59:14.000000+00:00 app[api]: Build started by user mallkz#hotmail.com
2020-08-30T20:59:46.151834+00:00 app[api]: Deploy 52d5b11d by user mallkz#hotmail.com
2020-08-30T20:59:46.151834+00:00 app[api]: Release v14 created by user mallkz#hotmail.com
2020-08-30T20:59:54.000000+00:00 app[api]: Build succeeded
2020-08-30T21:05:42.259926+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=billionaireboysclub.herokuapp.com request_id=63abbf21-aa34-433c-b9e6-8a708810e334 fwd="107.184.213.12" dyno= connect= service= status=503 bytes= protocol=https
2020-08-30T21:05:43.029607+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=billionaireboysclub.herokuapp.com request_id=91edc538-2ef0-4f8e-88e3-5bb91007e6c6 fwd="107.184.213.12" dyno= connect= service= status=503 bytes= protocol=https
Trying to deploy my Akka application to Heroku
In code I have:
val httpPort = Properties.envOrElse("PORT", "8080").toInt
val serverBinding: Future[Http.ServerBinding] = Http().bindAndHandle(routes,
"localhost", httpPort)
In Procfile I have:
web: target/universal/stage/bin/hello-world -Dhttp.port=${PORT}
But I still get in logs:
Error R10 (Boot timeout) ->
Web process failed to bind to $PORT within 60 seconds of launch
2019-04-11T11:22:30.239015+00:00 heroku[web.1]: Starting process with
command `target/universal/stage/bin/hello-world -Dhttp.port=${PORT}`
2019-04-11T11:22:32.322727+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS
defaults based on dyno size. Custom settings will override them.
2019-04-11T11:22:32.447725+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -
Xmx300m -Xss512k -XX:CICompilerCount=2 -Dfile.encoding=UTF-8
2019-04-11T11:22:35.729346+00:00 app[web.1]: Server online at
http://127.0.0.1:19702/
2019-04-11T11:23:30.413620+00:00 heroku[web.1]: State changed from starting
to crashed
2019-04-11T11:23:30.306939+00:00 heroku[web.1]: **Error R10 (Boot timeout) ->
Web process failed to bind to $PORT within 60 seconds of launch**
2019-04-11T11:23:30.307058+00:00 heroku[web.1]: Stopping process with SIGKILL
2019-04-11T11:23:30.395435+00:00 heroku[web.1]: Process exited with status
137
2019-04-11T11:23:31.907600+00:00 heroku[router]: at=error code=H10 desc="App
crashed" method=GET path="/" host=word-list-app.herokuapp.com
request_id=b1d988e1-f53a-4409-9546-75404a9fcd5c fwd="94.199.129.189" dyno=
connect= service= status=503 bytes= protocol=https
You should replace localhost with 0.0.0.0.
Trying to get a beat on why my Heroku site won't load as I haven't touched in 6 months+
http://t2bthr.herokuapp.com
Below are the logs. Can anyone shed some light into this? I see this error:
/app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:130:in `issue_authentication': Failed to authenticate user 'heroku' on db 'app476164' (Mongo::AuthenticationError)
I'm just not sure why all the sudden I'd be having authentication issues.
2014-05-29T00:17:43.330292+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11
2014-05-29T00:17:43.330293+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T00:17:43.330298+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T00:17:41.551293+00:00 heroku[web.1]: Starting process with command `thin -p 23291 -e production -R /home/heroku_rack/heroku.ru start`
2014-05-29T00:17:44.952612+00:00 heroku[web.1]: Process exited with status 1
2014-05-29T00:17:44.979544+00:00 heroku[web.1]: State changed from starting to crashed
2014-05-29T00:55:00.607805+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=2bthr.com request_id=a9823832-62fb-461c-a284-49968b44850e fwd="186.210.151.58" dyno= connect= service= status=503 bytes=
2014-05-29T01:03:17.147588+00:00 heroku[web.1]: State changed from crashed to starting
2014-05-29T01:03:19.495911+00:00 heroku[web.1]: Starting process with command `thin -p 7390 -e production -R /home/heroku_rack/heroku.ru start`
2014-05-29T01:03:22.751972+00:00 app[web.1]: Could not load SystemTimer >= v1.2.0. Falling back to timeout.rb. SystemTimer is STRONGLY recommended for timeouts in Ruby 1.8.7. See http://ph7spot.com/blog/system-timer-1-2-release for details.
2014-05-29T01:03:23.329833+00:00 app[web.1]: from /app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:111:in `authenticate'
2014-05-29T01:03:23.329806+00:00 app[web.1]: /app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:130:in `issue_authentication': Failed to authenticate user 'heroku' on db 'app476164' (Mongo::AuthenticationError)
2014-05-29T01:03:23.329874+00:00 app[web.1]: from ./bthr/app.rb:15
2014-05-29T01:03:23.329970+00:00 app[web.1]: from config.ru:4
2014-05-29T01:03:23.329854+00:00 app[web.1]: from ./bthr/../lib/db.rb:10:in `init_mongo'
2014-05-29T01:03:23.329914+00:00 app[web.1]: from ./bthr/app.rb:14
2014-05-29T01:03:23.329952+00:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
2014-05-29T01:03:23.330026+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T01:03:23.330045+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:63:in `new'
2014-05-29T01:03:23.329933+00:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
2014-05-29T01:03:23.329894+00:00 app[web.1]: from /app/.gems/gems/sinatra-1.2.2/lib/sinatra/base.rb:1222:in `configure'
2014-05-29T01:03:23.329989+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:23
2014-05-29T01:03:23.330008+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T01:03:23.330081+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:18
2014-05-29T01:03:23.330118+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T01:03:23.330063+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:63:in `map'
2014-05-29T01:03:23.330136+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11:in `new'
2014-05-29T01:03:23.330100+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T01:03:23.330191+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T01:03:23.330155+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11
2014-05-29T01:03:23.330211+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T01:03:23.330248+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:1
2014-05-29T01:03:23.330230+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:1:in `new'
2014-05-29T01:03:24.749727+00:00 heroku[web.1]: State changed from starting to crashed
2014-05-29T01:03:24.741605+00:00 heroku[web.1]: Process exited with status 1
2014-05-29T01:24:47.714571+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=2bthr.com request_id=037cebb1-d9eb-450e-97f1-e3846121d2b9 fwd="204.155.149.27" dyno= connect= service= status=503 bytes=
2014-05-29T01:31:12.690405+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=2bthr.com request_id=776fe43b-c755-47e7-b741-5a2ff59b1ee8 fwd="91.200.12.70" dyno= connect= service= status=503 bytes=
2014-05-29T01:31:13.714036+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/wp-login.php host=2bthr.com request_id=66ac2b17-b220-448a-ad98-d684bbdba67c fwd="91.200.12.70" dyno= connect= service= status=503 bytes=
2014-05-29T01:54:42.347628+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=2bthr.com request_id=6d6e97c9-467d-4598-a590-b9c595cc9204 fwd="198.204.249.34" dyno= connect= service= status=503 bytes=
2014-05-29T02:25:42.894295+00:00 heroku[web.1]: State changed from crashed to starting
2014-05-29T02:25:45.238484+00:00 heroku[web.1]: Starting process with command `thin -p 27261 -e production -R /home/heroku_rack/heroku.ru start`
2014-05-29T02:25:49.223844+00:00 app[web.1]: Could not load SystemTimer >= v1.2.0. Falling back to timeout.rb. SystemTimer is STRONGLY recommended for timeouts in Ruby 1.8.7. See http://ph7spot.com/blog/system-timer-1-2-release for details.
2014-05-29T02:25:49.446648+00:00 app[web.1]: /app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:130:in `issue_authentication': Failed to authenticate user 'heroku' on db 'app476164' (Mongo::AuthenticationError)
2014-05-29T02:25:49.446654+00:00 app[web.1]: from /app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:111:in `authenticate'
2014-05-29T02:25:49.446656+00:00 app[web.1]: from ./bthr/../lib/db.rb:10:in `init_mongo'
2014-05-29T02:25:49.446663+00:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
2014-05-29T02:25:49.446670+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:23
2014-05-29T02:25:49.446667+00:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
2014-05-29T02:25:49.446658+00:00 app[web.1]: from ./bthr/app.rb:15
2014-05-29T02:25:49.446659+00:00 app[web.1]: from /app/.gems/gems/sinatra-1.2.2/lib/sinatra/base.rb:1222:in `configure'
2014-05-29T02:25:49.446669+00:00 app[web.1]: from config.ru:4
2014-05-29T02:25:49.446673+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T02:25:49.446672+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T02:25:49.446675+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:63:in `new'
2014-05-29T02:25:49.446676+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:63:in `map'
2014-05-29T02:25:49.446678+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:18
2014-05-29T02:25:49.446683+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T02:25:49.446696+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:1:in `new'
2014-05-29T02:25:49.446661+00:00 app[web.1]: from ./bthr/app.rb:14
2014-05-29T02:25:49.446681+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T02:25:49.446754+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:1
2014-05-29T02:25:49.446686+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11:in `new'
2014-05-29T02:25:49.446688+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11
2014-05-29T02:25:49.446691+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T02:25:49.446692+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T02:25:50.718902+00:00 heroku[web.1]: State changed from starting to crashed
2014-05-29T02:25:50.711009+00:00 heroku[web.1]: Process exited with status 1
2014-05-29T05:06:51.450635+00:00 heroku[web.1]: State changed from crashed to starting
2014-05-29T05:06:54.632367+00:00 app[web.1]: Could not load SystemTimer >= v1.2.0. Falling back to timeout.rb. SystemTimer is STRONGLY recommended for timeouts in Ruby 1.8.7. See http://ph7spot.com/blog/system-timer-1-2-release for details.
2014-05-29T05:06:54.918788+00:00 app[web.1]: from ./bthr/../lib/db.rb:10:in `init_mongo'
2014-05-29T05:06:54.918790+00:00 app[web.1]: from ./bthr/app.rb:15
2014-05-29T05:06:54.918751+00:00 app[web.1]: from /app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:111:in `authenticate'
2014-05-29T05:06:54.918791+00:00 app[web.1]: from /app/.gems/gems/sinatra-1.2.2/lib/sinatra/base.rb:1222:in `configure'
2014-05-29T05:06:54.918794+00:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
2014-05-29T05:06:54.918736+00:00 app[web.1]: /app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:130:in `issue_authentication': Failed to authenticate user 'heroku' on db 'app476164' (Mongo::AuthenticationError)
2014-05-29T05:06:54.918793+00:00 app[web.1]: from ./bthr/app.rb:14
2014-05-29T05:06:54.918796+00:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
2014-05-29T05:06:54.918798+00:00 app[web.1]: from config.ru:4
2014-05-29T05:06:54.918799+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:23
2014-05-29T05:06:54.918802+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T05:06:54.918800+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T05:06:54.918803+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:63:in `new'
2014-05-29T05:06:54.918807+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T05:06:54.918806+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:18
2014-05-29T05:06:54.918808+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T05:06:54.918811+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11
2014-05-29T05:06:54.918814+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T05:06:54.918810+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11:in `new'
2014-05-29T05:06:54.918804+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:63:in `map'
2014-05-29T05:06:54.918816+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:1
2014-05-29T05:06:54.918815+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:1:in `new'
2014-05-29T05:06:54.918812+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T05:06:56.095995+00:00 heroku[web.1]: State changed from starting to crashed
2014-05-29T05:06:53.328857+00:00 heroku[web.1]: Starting process with command `thin -p 58046 -e production -R /home/heroku_rack/heroku.ru start`
2014-05-29T05:06:56.090088+00:00 heroku[web.1]: Process exited with status 1
2014-05-29T05:28:10.046206+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/?author=1 host=2bthr.com request_id=5792f655-69f8-4b48-860a-8780a01db388 fwd="94.102.53.194" dyno= connect= service= status=503 bytes=
2014-05-29T09:55:11.507149+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=2bthr.com request_id=170b4b0b-f566-4c5e-be01-f19c8f50cd85 fwd="105.237.54.93" dyno= connect= service= status=503 bytes=
2014-05-29T09:55:14.043513+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=2bthr.com request_id=fb065a48-8adf-4516-8313-67d50be49e11 fwd="105.237.54.93" dyno= connect= service= status=503 bytes=
2014-05-29T09:56:43.107933+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=2bthr.com request_id=dc3f3987-2caa-4b73-80b8-062d2ace6fa5 fwd="150.70.97.119" dyno= connect= service= status=503 bytes=
2014-05-29T10:06:23.161084+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=HEAD path=/ host=2bthr.com request_id=7acf11a7-27f9-42ed-81ec-12d6a488b936 fwd="119.63.193.194" dyno= connect= service= status=503 bytes=
2014-05-29T10:21:06.786562+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/robots.txt host=www.2bthr.com request_id=0fcd52e8-98f6-426c-bf9a-8600159d5976 fwd="65.55.52.111" dyno= connect= service= status=503 bytes=
If you are using the MongoLab add-on (https://addons.heroku.com/mongolab), they recently announced that on May 22 and May 23, they would be resetting everyone's login credentials in response to the Heartbleed bug.
If you were not using the MONGOLAB_URI environment variable to connect to your database, but instead hard-coded your login URI, then your app would error out. To fix this, update your username and password. To prevent future errors like this in the future, create an additional database user and use that username and password wherever you use a hard-coded login.
Here is a post that describes some of the steps MongoLab has taken to address the issue:
http://blog.mongolab.com/2014/04/heartbleed-security-update/
I'm trying to deploy a simple Sinatra app to Heroku, I'm using postgresql, my Gemfile looks like this:
gem 'sinatra'
gem 'data_mapper'
gem 'dm-postgres-adapter'
gem 'pg'
gem 'database_cleaner'
gem 'bcrypt-ruby'
gem 'rack-flash3'
gem 'sinatra-partial'
gem 'mandrill-api'
group :development, :test do
gem 'capybara'
gem 'shotgun'
gem 'rspec'
gem 'debugger'
end
I have the pg add-on on my app, This is how my datamapper_setup.rb looks:
env = ENV['RACK_ENV'] || "development"
DataMapper.setup(:default, ENV['DATABASE_URL'] || "postgres://localhost/bookmark_manager_# {env}")
DataMapper.finalize
DataMapper.auto_upgrade!
I don't know how to interpret the logs from heroku but here they are:
2014-03-29T13:35:47.674101+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=staging-bookmarkmanager.herokuapp.com request_id=304ebd75-859f-4768-9766-f25ca2fdf3ba fwd="77.99.158.5" dyno= connect= service= status=503 bytes=
2014-03-29T13:35:48.545822+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=staging-bookmarkmanager.herokuapp.com request_id=1669c22c-60c2-4d74-9967-7e60b32d49ad fwd="77.99.158.5" dyno= connect= service= status=503 bytes=
2014-03-29T13:35:51.486444+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=staging-bookmarkmanager.herokuapp.com request_id=6c70962d-7313-4dee-82de-5c12ca091aab fwd="77.99.158.5" dyno= connect= service= status=503 bytes=
2014-03-29T13:35:52.025452+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=staging-bookmarkmanager.herokuapp.com request_id=9166bd84-2187-4d2c-bf01-13a1a5574ac1 fwd="77.99.158.5" dyno= connect= service= status=503 bytes=
Any ideas on why is this happening? I've tried several approaches already with no luck.
In the additional logs you posted, it would seem that the database is refusing your connection:
FATAL: role "xbwj…jedif" is not permitted to log in (DataObjects::ConnectionError)
Verify the that the credentials provided by ENV['DATABASE_URL'] are the same as those listed in the output of heroku config.