heroku / legacy-cli

Heroku CLI
https://cli.heroku.com
MIT License
1.37k stars 380 forks source link

Resetting the database from behind proxy #679

Open mintuhouse opened 11 years ago

mintuhouse commented 11 years ago

mintuhouse@mintuhouse:/opt/lampp/htdocs/lithasa$ heroku pg:reset DATABASE_URL --confirm sleepy-plains-5835
Resetting HEROKU_POSTGRESQL_BLACK_URL (DATABASE_URL)... failed
!    Heroku client internal error.
!    Search for help at: https://help.heroku.com
!    Or report a bug at: https://github.com/heroku/heroku/issues/new

Error:       SSL_connect returned=1 errno=0 state=unknown state: unknown protocol (OpenSSL::SSL::SSLError)
Backtrace:   /home/mintuhouse/.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/net/http.rb:799:in `connect'
             /home/mintuhouse/.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/net/http.rb:799:in `block in connect'
             /home/mintuhouse/.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/timeout.rb:54:in `timeout'
             /home/mintuhouse/.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/timeout.rb:99:in `timeout'
             /home/mintuhouse/.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/net/http.rb:799:in `connect'
             /home/mintuhouse/.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/net/http.rb:755:in `do_start'
             /home/mintuhouse/.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/net/http.rb:744:in `start'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/rest-client-1.6.7/lib/restclient/request.rb:172:in `transmit'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/rest-client-1.6.7/lib/restclient/request.rb:64:in `execute'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in `execute'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/rest-client-1.6.7/lib/restclient/resource.rb:76:in `put'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/heroku-2.34.0/lib/heroku/client/heroku_postgresql.rb:127:in `block in http_put'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/heroku-2.34.0/lib/heroku/client/heroku_postgresql.rb:91:in `checking_client_version'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/heroku-2.34.0/lib/heroku/client/heroku_postgresql.rb:126:in `http_put'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/heroku-2.34.0/lib/heroku/client/heroku_postgresql.rb:57:in `reset'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/heroku-2.34.0/lib/heroku/command/pg.rb:103:in `block in reset'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/heroku-2.34.0/lib/heroku/helpers.rb:236:in `action'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/heroku-2.34.0/lib/heroku/command/pg.rb:102:in `reset'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/heroku-2.34.0/lib/heroku/command.rb:207:in `run'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/heroku-2.34.0/lib/heroku/cli.rb:28:in `start'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/gems/heroku-2.34.0/bin/heroku:17:in `<top (required)>'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/bin/heroku:19:in `load'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/bin/heroku:19:in `<main>'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/bin/ruby_noexec_wrapper:14:in `eval'
             /home/mintuhouse/.rvm/gems/ruby-1.9.3-p327@global/bin/ruby_noexec_wrapper:14:in `<main>'

Command:     heroku pg:reset DATABASE_URL --confirm sleepy-plains-5835
HTTP Proxy:  http://hasankumar_reddy:hasan&@netmon.iitb.ac.in:80/
HTTPS Proxy: http://hasankumar_reddy:hasan&@netmon.iitb.ac.in:80/
Version:     heroku-gem/2.34.0 (i686-linux) ruby/1.9.3

Issues related to similar errors during account login were found, but the solution suggested was to upgrade tp latest pack of gems But I already have

Any help regarding it would be appreciated.

wuputah commented 11 years ago

Same issue as #677.

wuputah commented 11 years ago

I lied, it's not. Though the fix is the same, I think.