Re: App is Crashing with a meaningless Error
That didn't work, thanks for the idea though. Here's the code: https://github.com/jeffayle/TV-Tracker (please excuse the incredibly embarrassing commit messages) On Feb 13, 11:11 am, Jesse House wrote: > I have a rails app that referenced aws-s3. last time I uploaded my > code the gems were re-imported and I ended up with builder 3.0.0 (aws- > s3 depends on builder); this caused a lot of other code to start > failing. > > I had to specify builder -v 2.1.2, I am only bringing this up since I > see errors in builder in your stacktrace, in my case it was a local > gem not part of the heroku stack > > try to specify builder -v 2.1.2 in .gem or bundler? > > On Feb 12, 11:38 am, Jeffrey Aylesworth wrote: > > > I have a Sinatra app working on my local computer, but when I send it > > to heroku, it crashes. The error log says: > > > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > > heroku.ru:18 > > 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ > > gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `instance_eval' > > 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ > > gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `initialize' > > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > > heroku.ru:11:in `new' > > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > > heroku.ru:11 > > 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ > > gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `instance_eval' > > 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ > > gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `initialize' > > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > > heroku.ru:1:in `new' > > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > > heroku.ru:1 > > 2011-02-12T11:36:50-08:00 heroku[web.1]: State changed from starting > > to crashed > > 2011-02-12T11:36:55-08:00 heroku[router]: Error H10 (App crashed) -> > > GET deep-ice-593.heroku.com/ dyno=none queue=0 wait=0ms service=0ms > > bytes=0 > > 2011-02-12T11:36:55-08:00 heroku[router]: Error H10 (App crashed) -> > > GET deep-ice-593.heroku.com/favicon.ico dyno=none queue=0 wait=0ms > > service=0ms bytes=0 > > 2011-02-12T11:36:55-08:00 heroku[nginx]: GET /favicon.ico HTTP/1.1 | > > 24.57.83.182 | 3310 | http | 500 > > 2011-02-12T11:36:55-08:00 heroku[nginx]: GET / HTTP/1.1 | 24.57.83.182 > > | 3310 | http | 500 > > 2011-02-12T11:36:55-08:00 heroku[router]: Error H10 (App crashed) -> > > GET deep-ice-593.heroku.com/favicon.ico dyno=none queue=0 wait=0ms > > service=0ms bytes=0 > > 2011-02-12T11:36:55-08:00 heroku[nginx]: GET /favicon.ico HTTP/1.1 | > > 24.57.83.182 | 3310 | http | 500 > > 2011-02-12T11:36:58-08:00 heroku[router]: Error H10 (App crashed) -> > > GET deep-ice-593.heroku.com/ dyno=none queue=0 wait=0ms service=0ms > > bytes=0 > > 2011-02-12T11:36:58-08:00 heroku[nginx]: GET / HTTP/1.1 | 24.57.83.182 > > | 3310 | http | 500 > > 2011-02-12T11:36:58-08:00 heroku[router]: Error H10 (App crashed) -> > > GET deep-ice-593.heroku.com/favicon.ico dyno=none queue=0 wait=0ms > > service=0ms bytes=0 > > 2011-02-12T11:36:58-08:00 heroku[nginx]: GET /favicon.ico HTTP/1.1 | > > 24.57.83.182 | 3310 | http | 500 > > > Which means nothing to me because it does not mention any of my own > > files, as far as I can see. > > > Has anyone had this before, and know what might be causing the > > problem? > > > Thanks. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: How to pass username and password as authorization header to Restclient?
Hi,
Is this correct one?
basic_auth = ""
if (parameter[:password])
password1 = parameter[:password].to_s
basic_auth = Base64.encode64("admin"+":"+password1)
end
resp = RestClient.put uri, str.strip!.to_s, :content_type =>
'text/xml', :Authorization => basic_auth
Will this pass user and password values to RestClient (req.basic_auth(user,
password)?
Thanks,
Kavita
On Mon, Feb 14, 2011 at 4:56 AM, Brandon Casci wrote:
>
> https://github.com/adamwiggins/rest-client
>
> One of the first examples shows the credentials in the URL. Helpful?
>
> Sent from my iPhone
>
> On Feb 13, 2011, at 5:56 PM, "kavitha.k kavi" wrote:
>
> Hi,
>
> I have heard a lot about Heroku and his work on Ruby on rails. I have
> started working on ruby newly. I need to implement basic authorization
> (https). I have used Heroku's implementation for http GET, PUT, POST and
> DELETE methods. I need to pass username and password so that RestClient
> does basic authorization and returns the result.
> Can you please help me how to pass username and password (for basic
> authentication) as optional parameters to RestClient.
> Suppose,
>
> - > If the restclient module is defined as follows,
> def self.put(url, payload, headers={})
> Request.execute(:method => :put, :url => url, :payload => payload,
> :headers => headers)
> end
>
> - > username, password, headers , methods(GET, PUT, POST, DELETE) are
> initialised as follows,
> def initialize(args)
> @method = args[:method] or raise ArgumentError, "must pass :method"
> @url = args[:url] or raise ArgumentError, "must pass :url"
> @headers = args[:headers] || {}
> @payload = process_payload(args[:payload])
> @user = args[:user]
> @password = args[:password]
> @timeout = args[:timeout]
> end
>
> - > Basic authorization is performed internally as,
> def setup_credentials(req)
> req.basic_auth(user, password) if user
> end
>
> - > Now, I need to pass username and password in the authentication header,
> so that the values are passed to RestClient and basic authorization is
> performed.
> response=RestClient.put uri, resp.to_s, :content_type => 'text/xml' (how
> top pass authentication header from here to RestClient (
> req.basic_auth(user, password) if user )? )
>
> Can you please help me on this?
>
> Regards
> Kavita
>
> --
> You received this message because you are subscribed to the Google Groups
> "Heroku" group.
> To post to this group, send email to heroku@googlegroups.com.
> To unsubscribe from this group, send email to
> heroku+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Heroku" group.
> To post to this group, send email to heroku@googlegroups.com.
> To unsubscribe from this group, send email to
> heroku+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to heroku@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
Re: How to pass username and password as authorization header to Restclient?
https://github.com/adamwiggins/rest-client
One of the first examples shows the credentials in the URL. Helpful?
Sent from my iPhone
On Feb 13, 2011, at 5:56 PM, "kavitha.k kavi" wrote:
> Hi,
>
> I have heard a lot about Heroku and his work on Ruby on rails. I have started
> working on ruby newly. I need to implement basic authorization (https). I
> have used Heroku's implementation for http GET, PUT, POST and DELETE methods.
> I need to pass username and password so that RestClient does basic
> authorization and returns the result.
> Can you please help me how to pass username and password (for basic
> authentication) as optional parameters to RestClient.
> Suppose,
>
> - > If the restclient module is defined as follows,
> def self.put(url, payload, headers={})
> Request.execute(:method => :put, :url => url, :payload => payload,
> :headers => headers)
> end
>
> - > username, password, headers , methods(GET, PUT, POST, DELETE) are
> initialised as follows,
> def initialize(args)
> @method = args[:method] or raise ArgumentError, "must pass :method"
> @url = args[:url] or raise ArgumentError, "must pass :url"
> @headers = args[:headers] || {}
> @payload = process_payload(args[:payload])
> @user = args[:user]
> @password = args[:password]
> @timeout = args[:timeout]
> end
>
> - > Basic authorization is performed internally as,
> def setup_credentials(req)
> req.basic_auth(user, password) if user
> end
>
> - > Now, I need to pass username and password in the authentication header,
> so that the values are passed to RestClient and basic authorization is
> performed.
> response=RestClient.put uri, resp.to_s, :content_type => 'text/xml' (how top
> pass authentication header from here to RestClient ( req.basic_auth(user,
> password) if user )? )
>
> Can you please help me on this?
>
> Regards
> Kavita
> --
> You received this message because you are subscribed to the Google Groups
> "Heroku" group.
> To post to this group, send email to heroku@googlegroups.com.
> To unsubscribe from this group, send email to
> heroku+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to heroku@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
How to pass username and password as authorization header to Restclient?
Hi,
I have heard a lot about Heroku and his work on Ruby on rails. I have
started working on ruby newly. I need to implement basic authorization
(https). I have used Heroku's implementation for http GET, PUT, POST and
DELETE methods. I need to pass username and password so that RestClient
does basic authorization and returns the result.
Can you please help me how to pass username and password (for basic
authentication) as optional parameters to RestClient.
Suppose,
- > If the restclient module is defined as follows,
def self.put(url, payload, headers={})
Request.execute(:method => :put, :url => url, :payload => payload,
:headers => headers)
end
- > username, password, headers , methods(GET, PUT, POST, DELETE) are
initialised as follows,
def initialize(args)
@method = args[:method] or raise ArgumentError, "must pass :method"
@url = args[:url] or raise ArgumentError, "must pass :url"
@headers = args[:headers] || {}
@payload = process_payload(args[:payload])
@user = args[:user]
@password = args[:password]
@timeout = args[:timeout]
end
- > Basic authorization is performed internally as,
def setup_credentials(req)
req.basic_auth(user, password) if user
end
- > Now, I need to pass username and password in the authentication header,
so that the values are passed to RestClient and basic authorization is
performed.
response=RestClient.put uri, resp.to_s, :content_type => 'text/xml' (how top
pass authentication header from here to RestClient ( req.basic_auth(user,
password) if user )? )
Can you please help me on this?
Regards
Kavita
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to heroku@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
Re: App is Crashing with a meaningless Error
I have a rails app that referenced aws-s3. last time I uploaded my code the gems were re-imported and I ended up with builder 3.0.0 (aws- s3 depends on builder); this caused a lot of other code to start failing. I had to specify builder -v 2.1.2, I am only bringing this up since I see errors in builder in your stacktrace, in my case it was a local gem not part of the heroku stack try to specify builder -v 2.1.2 in .gem or bundler? On Feb 12, 11:38 am, Jeffrey Aylesworth wrote: > I have a Sinatra app working on my local computer, but when I send it > to heroku, it crashes. The error log says: > > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > heroku.ru:18 > 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ > gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `instance_eval' > 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ > gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `initialize' > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > heroku.ru:11:in `new' > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > heroku.ru:11 > 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ > gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `instance_eval' > 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ > gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `initialize' > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > heroku.ru:1:in `new' > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > heroku.ru:1 > 2011-02-12T11:36:50-08:00 heroku[web.1]: State changed from starting > to crashed > 2011-02-12T11:36:55-08:00 heroku[router]: Error H10 (App crashed) -> > GET deep-ice-593.heroku.com/ dyno=none queue=0 wait=0ms service=0ms > bytes=0 > 2011-02-12T11:36:55-08:00 heroku[router]: Error H10 (App crashed) -> > GET deep-ice-593.heroku.com/favicon.ico dyno=none queue=0 wait=0ms > service=0ms bytes=0 > 2011-02-12T11:36:55-08:00 heroku[nginx]: GET /favicon.ico HTTP/1.1 | > 24.57.83.182 | 3310 | http | 500 > 2011-02-12T11:36:55-08:00 heroku[nginx]: GET / HTTP/1.1 | 24.57.83.182 > | 3310 | http | 500 > 2011-02-12T11:36:55-08:00 heroku[router]: Error H10 (App crashed) -> > GET deep-ice-593.heroku.com/favicon.ico dyno=none queue=0 wait=0ms > service=0ms bytes=0 > 2011-02-12T11:36:55-08:00 heroku[nginx]: GET /favicon.ico HTTP/1.1 | > 24.57.83.182 | 3310 | http | 500 > 2011-02-12T11:36:58-08:00 heroku[router]: Error H10 (App crashed) -> > GET deep-ice-593.heroku.com/ dyno=none queue=0 wait=0ms service=0ms > bytes=0 > 2011-02-12T11:36:58-08:00 heroku[nginx]: GET / HTTP/1.1 | 24.57.83.182 > | 3310 | http | 500 > 2011-02-12T11:36:58-08:00 heroku[router]: Error H10 (App crashed) -> > GET deep-ice-593.heroku.com/favicon.ico dyno=none queue=0 wait=0ms > service=0ms bytes=0 > 2011-02-12T11:36:58-08:00 heroku[nginx]: GET /favicon.ico HTTP/1.1 | > 24.57.83.182 | 3310 | http | 500 > > Which means nothing to me because it does not mention any of my own > files, as far as I can see. > > Has anyone had this before, and know what might be causing the > problem? > > Thanks. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: "Your application is too busy to open a console session."
It is a read only filesystem. So sqlite3 would not work On Feb 13, 2011, at 6:20 AM, Vinicius de Araujo Barboza wrote: > I'm also new to Heroku and get the same error here following the > documentation guide. > And another question about databases: > Does Heroku support SQLite3? > > On Feb 12, 10:14 am, MikeBlyth wrote: >> I'm new to Heroku, trying to get my databases set up, and when I try >> to open the console this is what I get: >> >> Your application is too busy to open a console session. >> Console sessions require an open dyno to use for execution. >> >> I tried putting the application into maintenance mode in case it was >> in fact doing something, but this doesn't help. The app crashes >> whenever it starts, so hard to see how it is too busy. > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: "Your application is too busy to open a console session."
This had me worried for a minute, as I frequently open consoles on 1 dyno apps. That message suggests that if a console is open, a dyno is busy servicing the request. However, after a quick check it seems to not be the case. Maybe someone @ Heroku could tell us what the deal is here - I don't want my inquisitiveness to take a site offline ;) Neil Middleton http://about.me/neilmiddleton On Saturday, 12 February 2011 at 12:14, MikeBlyth wrote: > Console sessions require an open dyno to use for execution. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: "Your application is too busy to open a console session."
I'm also new to Heroku and get the same error here following the documentation guide. And another question about databases: Does Heroku support SQLite3? On Feb 12, 10:14 am, MikeBlyth wrote: > I'm new to Heroku, trying to get my databases set up, and when I try > to open the console this is what I get: > > Your application is too busy to open a console session. > Console sessions require an open dyno to use for execution. > > I tried putting the application into maintenance mode in case it was > in fact doing something, but this doesn't help. The app crashes > whenever it starts, so hard to see how it is too busy. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
