Re: Fixed IP? Will my idea work...
If it were me I'd pay the extra $100 to ensure my app worked the way it needed it too. If I didn't want to pay I'd look to see if anything tools out there could proxy SOAP calls for me. If not then maybe build a proxy to the SOAP API you want to use. I'd probably put the service or homebrewed proxy app on a dinky Linode VPS, but any would do. I don't know how complicated the other API is, but you may be able to proxy it without much work.. Maybe mapping a bunch of routes to a single controller that examines the message payload, makes the right call on the real API and passes the result back. This way you code your app as if it were using the actual API. Though knowing myself, I'd just pay the $100 because my days are busy enough ;) On Mar 8, 2012, at 2:21 PM, Karl threadh...@gmail.com wrote: So, I need to connect to a SOAP API that requires the caller have a fixed IP address. We all know that heroku has two options: $100 a month for fixed ip ssl, or no-can-do. And I'm not convinced that the instance doing the calling will reveal the fixed ip anyway. So, my thought is that I could create an EC2 micro instance, give it an elastic IP address, and hobble together a quick sinatra app to receive calls from my heroku app and have it make the SOAP calls. But I would like this EC2 instance (not under heroku's app structure) to connect to the postgres db directly. I'm using the shared postgres db, but I may be willing to go with an add-on if it works. Is this possible, will it work? PS - yes, I know I could have the sinatra app just return the SOAP XML back to the heroku app, and that is my plan 'B'. But if it could talk to the postgres db directly, it would make the setup easier and simpler. -- You received this message because you are subscribed to the Google Groups Heroku group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/PdCvU66I0SkJ. 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: background jobs are becoming unresponsive regularly
well...I meant to add more to my response. Regardless of the problem Heroku resolved, the workers crash an awful lot. I have three of them running I hardly see run for more than 30 minutes. No useful information in the logs, and they crash with or without work to do...meaning the queue can be empty and they fall over. As far as I know, this is a pretty new problem and I wonder if there is an incompatibility in the mix. Maybe a gem that's causing a problem. It's a bit tricky to pin down. On Wed, May 25, 2011 at 8:21 AM, nevinera nevin...@gmail.com wrote: not much to go wrong there really. I'll just add a little teriyaki sauce, and I'm sure my words will be delicious. . -- 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. -- = Brandon Casci Loudcaster http://loudcaster.com = -- 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: background jobs are becoming unresponsive regularly
Ya, that sounds possible. On Wed, May 25, 2011 at 6:36 PM, Peter van Hardenberg p...@heroku.comwrote: Hmmm. Could it be that you're running out of memory and crashing without writing to the logs? -p On Wed, May 25, 2011 at 3:10 PM, Brandon Casci bran...@loudcaster.com wrote: well...I meant to add more to my response. Regardless of the problem Heroku resolved, the workers crash an awful lot. I have three of them running I hardly see run for more than 30 minutes. No useful information in the logs, and they crash with or without work to do...meaning the queue can be empty and they fall over. As far as I know, this is a pretty new problem and I wonder if there is an incompatibility in the mix. Maybe a gem that's causing a problem. It's a bit tricky to pin down. On Wed, May 25, 2011 at 8:21 AM, nevinera nevin...@gmail.com wrote: not much to go wrong there really. I'll just add a little teriyaki sauce, and I'm sure my words will be delicious. . -- 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. -- = Brandon Casci Loudcaster http://loudcaster.com = -- 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. -- = Brandon Casci Loudcaster http://loudcaster.com = -- 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: background jobs are becoming unresponsive regularly
From support: Sorry for the delayed response. We've had some issues with convergence that was preventing workers to get restarted properly. We've resolved them. The last crash I see is 4:33 and they've stayed running since. On Tue, May 24, 2011 at 8:05 AM, nevinera nevin...@gmail.com wrote: It is most likely not a platform problem, though you can assume what you like. Heroku workers are just calls to `rake jobs:work` from your app, and a watchdog that calls it again if the process dies - not much to go wrong there really. -- 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. -- = Brandon Casci Loudcaster http://loudcaster.com = -- 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.
background jobs are becoming unresponsive regularly
Our background jobs have started going unresponsive and they don't resume work until the app is restarted. This is the fourth day in a row. I'm assuming this is a platform problem since we haven't changed any of the job code in months. Does anyone out there advice on how we can detect if th workers have stopped and restart the app? -- = Brandon Casci Loudcaster http://loudcaster.com = -- 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: Suggestion for Heroku - different error message when issue deriving from AWS
Btw, I understand stuff happens, it just hurts. Sent from my iPhone On Apr 21, 2011, at 4:19 PM, Joe Sak j...@joesak.com wrote: Seriously, +1 for this. Wish we could put up nicer screens for our clients. People have no idea what's going on all day. -- 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 kavi@gmail.com 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.
Re: Memcached or Redis-to-Go
I move certain some data in and out out Heroku for processing with Redis-TG. I've been really impressed with the performance. On Jan 15, 2011, at 9:58 AM, John Maxwell jgwmaxw...@gmail.com wrote: Hi, I was wondering how the network response differs between using Memcached or Redis on Heroku. I'm happy using either for caching my app, but I was wondering which of the services has a better link into Heroku and thus is likely to offer better performance? (I'm not interested in a discussion about the merits of one over the other, just their performance within the Heroku platform!) Many thanks, John -- 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: Different size fonts and images between localhost and heroku
Some ideas... Check the style assets loaded on local host versus production. There is probably a difference. Force your browser to to a hard reload. Make sure your browser wasn't put into a zoom mode for your production URL. Sent from my iPhone On Nov 25, 2010, at 12:44 PM, Chris Walsh chriswa...@ireland.com wrote: Hi folks, I'm not sure if this is specific to Heroku or not, but it's still driving me nuts. My site looks different when viewed running on localhost compared to when it's deployed to heroku, even when viewed in the same browser. By different, I mean my fonts and images are a lot smaller in production (maybe 25% smaller) compared to localhost. It's throwing all my styling out and makes it a pain to layout the page properly. Anybody seen this before? Chris -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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 her...@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: MySQL server has gone away Amazon RDS
I get a few of these every couple days since upgraded to a dedicated DB as well...(PG in my case) On Fri, Nov 26, 2010 at 1:13 PM, David Whatley nsxda...@gmail.com wrote: I'm getting PGLostConnection type situations on our dedicated DB too lately. Have no idea if its related. On 11/26/10 6:31 AM, Russell Quinn wrote: I've occasionally getting MySQL server has gone away errors from my app running on Heroku (with the Amazon RDS add-on.) I'm guessing I need to adjust some packet size or timeout parameter. Does anyone have reliable information on what I should do? Thanks, Russell. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Parallel HTTP requests
I do something very similar. I just create a background job for each lookup. I think the delay for a background job could be up to 5 seconds, plus however long the job takes, and however long your queue is. It's pretty much your only option if you want to take that process out of the controller action and keep it all within Heroku. You could probably get away with having the UI periodically poll the the server and display the results as they come for some time. On Tue, Nov 2, 2010 at 3:39 PM, Alejandro Cadavid acada...@gmail.comwrote: Hi guys, I'm building an app which basically query several APIs (about 6-7) based on some words the user inputs in a form and compares the results between them. I'm not actually saving the data to the database, just calculating some stuff and displaying the results to the user. My question is, is there a good way in heroku to parallelize those HTTP requests? Right now i'm just doing one after the other. I read about delayed_but i'm not sure about it because i don't know how long would it take to start processing the requests as soon as they arrive.. i don't want to make the user to wait for a longer time.. but i'm not really sure if my guess is correct. Any other suggestion about this? -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Heroku down time today, about 30 minutes total
%252bunsubscr...@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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com heroku%2bunsubscr...@googlegroups.comheroku%252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. --+1-919-627-7546 -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
http basic auth
Anyone know if basic http auth supported on Heroku? I don't get the login box so I'm assuming no, unless there is a special convention I don't know about. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: http basic auth
I figured it out... this works authenticate_or_request_with_http_basic this does not authenticate_with_http_basic oops! On Thu, Nov 4, 2010 at 9:43 PM, Chris Hanks christopher.m.ha...@gmail.comwrote: Don't see why Heroku would have a problem with it. I've been using Rails' basic auth functionality on Heroku for months with zero issues. On Nov 4, 6:39 pm, Jimmy Thrasher ji...@jimmythrasher.com wrote: Not sure what you mean. If you implement it, it's supported.. it's just a webserver returning a 401 Unauthorized HTTP response. The browser will take care of popping up the dialog. Apache's .htaccess and other non-code ways of accomplishing it aren't supported. Here's an example for Sinatra:http://stackoverflow.com/questions/3479737 Rails has a built-in authenticate_with_http_basic and a couple other methods. Jimmy On Thu, Nov 4, 2010 at 9:09 PM, Brandon Casci bran...@loudcaster.com wrote: Anyone know if basic http auth supported on Heroku? I don't get the login box so I'm assuming no, unless there is a special convention I don't know about. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com heroku%2bunsubscr...@googlegroups.comheroku%252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- +1-919-627-7546 -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Sendgrid questions
I've been playing with Sendgrid for a while. I think they eventually start rejecting messages, but I've also heard they might hunt you down with a furious wrath that no one can comprehend. On Fri, Oct 29, 2010 at 3:09 PM, Russell Quinn m...@russellquinn.comwrote: * What happens if I exceed my quota? * How do we access the Sendgrid web interface from our Heroku account? -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Sendgrid questions
You know...I just remembered I'm not using the Sendgrid addon. I'm still using my own Sendgrid account I set up before moving to Heroku. I'm pretty sure I encountered a hard limit there, but that was before Sendgrid launched the new site and some other things. On Fri, Oct 29, 2010 at 5:05 PM, chris mcclellan...@gmail.com wrote: Pretty sure they'll just charge you... their regular plans ( http://sendgrid.com/pricing.html ) all have a Price per email thereafter To access the Sendgrid web interface, run 'heroku config' and look for the ENV variables SENDGRID_PASSWORD and SENDGRID_USERNAME. Use those to login at sendgrid.com ! On Oct 29, 3:09 pm, Russell Quinn m...@russellquinn.com wrote: * What happens if I exceed my quota? * How do we access the Sendgrid web interface from our Heroku account? -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Heroku down time today, about 30 minutes total
As much as it sucks when your site goes down, Heroku is doing a better job taming EC2 than I was. I've had my stuff on EC2 for some time and was ready to bail after a lot of frustration, but decided to take Heoku for a whirl. What EC2 offers is pretty cool, but you have to put a lot of work in to deal with recovering from EC2's own problems, like instances dropping off. I lost five in a year. Heroku abstracts all that for Rails apps. On Wed, Oct 27, 2010 at 12:01 AM, David nsxda...@gmail.com wrote: Growing pains. They'll get it resolved. On Tue, Oct 26, 2010 at 6:03 PM, Shane Becker veganstraighte...@gmail.com wrote: How can we be sure this won't happen again? No -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: inconsistent Memcache reads
It took a few days for the ticket to get answered, but yesterday did get confirmation from Heroku that this was a problem, with Amazon EC2 causing the pain. See this: http://getsatisfaction.com/heroku/topics/sporadic_errors_with_memcache_addon I have the same symptoms they mention, though for my app it's not sporadic, it's a state. The only way I can seem to shake it is by opening the rails console and doing Rails.cache.clear, and things go back to normal until problem kicks back up again. I'd rate this problem a 9.5 out of 10 for my app. What makes things particularly difficult for me is input comes in from outside sources and sits in memcache. In this case, what a radio station is currently playing, and it should stay there until the next time until new data comes in via the API. I suppose it's fair to say that data should be placed in the DB, which is fine. I can do that, and then do a Rails.cache.fetch from there. Any miss would mean another AR query instead of a nil. That's still a problem though, because a lot of supplementary data gets queried with the song title, artwork, photos, products and more. So all those cache misses will have a recognizable negative impact. On Tue, Oct 5, 2010 at 9:13 AM, John Norman j...@7fff.com wrote: Brandon: Regretably, I'm cheating and am using the Dalli gem without the guidance of Heroku. :-( I couldn't get memcached-northscale to compile on my Mac. Whatever. In any case: Rails.cache.write foo, bar = true Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar On Mon, Oct 4, 2010 at 3:53 PM, Brandon Casci bran...@loudcaster.comwrote: Yep :) On Mon, Oct 4, 2010 at 4:48 PM, Teng Siong Ong siong1...@gmail.comwrote: are you sure that you are using the supported memcache gem? http://docs.heroku.com/memcache On Mon, Oct 4, 2010 at 3:43 PM, Brandon Casci bran...@loudcaster.comwrote: It's crazy making. Rails.cache.read mykey = nil Rails.cache.read mykey = nil Rails.cache.read mykey = nil Rails.cache.read mykey = 1 Rails.cache.read mykey = nil Rails.cache.read mykey = nil Rails.cache.read mykey = 1 Rails.cache.read mykey = nil Rails.cache.read mykey = nil On Sat, Oct 2, 2010 at 7:58 PM, Brandon Casci bran...@loudcaster.comwrote: Hello I'm new to Heroku, so I'm not sure if this is a problem, or normal behavior. I'm seeing a inconsistent memcache reads. Reading a key will sometimes alternate between nil and the value placed in memcache. Other times the value just seems to vanish, though that could be a sign that memcache is full, though I can't find a way to tell if it's full. What do es everyone think might be happening? -- = Brandon Casci Loudcaster http://loudcaster.com = -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http
Re: inconsistent Memcache reads
That was the first thing I checked. The cache did not look full to me. I had this app running outside of heroku for months with out the problem. Though as a safeguard I went ahead and made sure I gave all my memcache writes an expirations and cleared the cache. That didn't seem to help. On Tue, Oct 5, 2010 at 9:19 AM, chris mcclellan...@gmail.com wrote: It does sound like your cache might be full. You can use Rails.cache.stats to see various stats, including how much memory you're using. Docs are at the vey bottom of http://docs.heroku.com/memcache On Oct 2, 7:58 pm, Brandon Casci bran...@loudcaster.com wrote: Hello I'm new to Heroku, so I'm not sure if this is a problem, or normal behavior. I'm seeing a inconsistent memcache reads. Reading a key will sometimes alternate between nil and the value placed in memcache. Other times the value just seems to vanish, though that could be a sign that memcache is full, though I can't find a way to tell if it's full. What do es everyone think might be happening? -- = Brandon Casci Loudcasterhttp://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: inconsistent Memcache reads
I forgot to mention, when this state kicks up Rails.cache.stats will error out occasionally, but not nearly as often as a cache miss. On Tue, Oct 5, 2010 at 9:19 AM, chris mcclellan...@gmail.com wrote: It does sound like your cache might be full. You can use Rails.cache.stats to see various stats, including how much memory you're using. Docs are at the vey bottom of http://docs.heroku.com/memcache On Oct 2, 7:58 pm, Brandon Casci bran...@loudcaster.com wrote: Hello I'm new to Heroku, so I'm not sure if this is a problem, or normal behavior. I'm seeing a inconsistent memcache reads. Reading a key will sometimes alternate between nil and the value placed in memcache. Other times the value just seems to vanish, though that could be a sign that memcache is full, though I can't find a way to tell if it's full. What do es everyone think might be happening? -- = Brandon Casci Loudcasterhttp://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: inconsistent Memcache reads
The problem for me isn't the exception vs miss, it's data reliability. On Tue, Oct 5, 2010 at 10:19 AM, Keenan Brock kee...@thebrocks.net wrote: Hi Brandon, Once, I had changed my memcache client library and it started raising exceptions. Turns out the previous library just returned a nil, while this one raised an exception. So I hacked the library to return nil on failures rather than throw exceptions. (The previous library just returned a nil not failing) This seems like the answer for me. Maybe alter the gem and add the option to throw an exception instead of returning a nil. But it is curious that it would fail so many times. --Keenan On Oct 5, 2010, at 9:25 AM, Brandon Casci wrote: It took a few days for the ticket to get answered, but yesterday did get confirmation from Heroku that this was a problem, with Amazon EC2 causing the pain. See this: http://getsatisfaction.com/heroku/topics/sporadic_errors_with_memcache_addon I have the same symptoms they mention, though for my app it's not sporadic, it's a state. The only way I can seem to shake it is by opening the rails console and doing Rails.cache.clear, and things go back to normal until problem kicks back up again. I'd rate this problem a 9.5 out of 10 for my app. What makes things particularly difficult for me is input comes in from outside sources and sits in memcache. In this case, what a radio station is currently playing, and it should stay there until the next time until new data comes in via the API. I suppose it's fair to say that data should be placed in the DB, which is fine. I can do that, and then do a Rails.cache.fetch from there. Any miss would mean another AR query instead of a nil. That's still a problem though, because a lot of supplementary data gets queried with the song title, artwork, photos, products and more. So all those cache misses will have a recognizable negative impact. On Tue, Oct 5, 2010 at 9:13 AM, John Norman j...@7fff.com wrote: Brandon: Regretably, I'm cheating and am using the Dalli gem without the guidance of Heroku. :-( I couldn't get memcached-northscale to compile on my Mac. Whatever. In any case: Rails.cache.write foo, bar = true Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar On Mon, Oct 4, 2010 at 3:53 PM, Brandon Casci bran...@loudcaster.comwrote: Yep :) On Mon, Oct 4, 2010 at 4:48 PM, Teng Siong Ong siong1...@gmail.comwrote: are you sure that you are using the supported memcache gem? http://docs.heroku.com/memcache On Mon, Oct 4, 2010 at 3:43 PM, Brandon Casci bran...@loudcaster.comwrote: It's crazy making. Rails.cache.read mykey = nil Rails.cache.read mykey = nil Rails.cache.read mykey = nil Rails.cache.read mykey = 1 Rails.cache.read mykey = nil Rails.cache.read mykey = nil Rails.cache.read mykey = 1 Rails.cache.read mykey = nil Rails.cache.read mykey = nil On Sat, Oct 2, 2010 at 7:58 PM, Brandon Casci bran...@loudcaster.comwrote: Hello I'm new to Heroku, so I'm not sure if this is a problem, or normal behavior. I'm seeing a inconsistent memcache reads. Reading a key will sometimes alternate between nil and the value placed in memcache. Other times the value just seems to vanish, though that could be a sign that memcache is full, though I can't find a way to tell if it's full. What do es everyone think might be happening? -- = Brandon Casci Loudcaster http://loudcaster.com = -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google
Re: inconsistent Memcache reads
Aye On Tue, Oct 5, 2010 at 10:37 AM, John Norman j...@7fff.com wrote: Maybe you should take it up in the Northscale forums ( http://www.northscale.com/support/policies.html). On Tue, Oct 5, 2010 at 9:26 AM, Brandon Casci bran...@loudcaster.comwrote: The problem for me isn't the exception vs miss, it's data reliability. On Tue, Oct 5, 2010 at 10:19 AM, Keenan Brock kee...@thebrocks.netwrote: Hi Brandon, Once, I had changed my memcache client library and it started raising exceptions. Turns out the previous library just returned a nil, while this one raised an exception. So I hacked the library to return nil on failures rather than throw exceptions. (The previous library just returned a nil not failing) This seems like the answer for me. Maybe alter the gem and add the option to throw an exception instead of returning a nil. But it is curious that it would fail so many times. --Keenan On Oct 5, 2010, at 9:25 AM, Brandon Casci wrote: It took a few days for the ticket to get answered, but yesterday did get confirmation from Heroku that this was a problem, with Amazon EC2 causing the pain. See this: http://getsatisfaction.com/heroku/topics/sporadic_errors_with_memcache_addon I have the same symptoms they mention, though for my app it's not sporadic, it's a state. The only way I can seem to shake it is by opening the rails console and doing Rails.cache.clear, and things go back to normal until problem kicks back up again. I'd rate this problem a 9.5 out of 10 for my app. What makes things particularly difficult for me is input comes in from outside sources and sits in memcache. In this case, what a radio station is currently playing, and it should stay there until the next time until new data comes in via the API. I suppose it's fair to say that data should be placed in the DB, which is fine. I can do that, and then do a Rails.cache.fetch from there. Any miss would mean another AR query instead of a nil. That's still a problem though, because a lot of supplementary data gets queried with the song title, artwork, photos, products and more. So all those cache misses will have a recognizable negative impact. On Tue, Oct 5, 2010 at 9:13 AM, John Norman j...@7fff.com wrote: Brandon: Regretably, I'm cheating and am using the Dalli gem without the guidance of Heroku. :-( I couldn't get memcached-northscale to compile on my Mac. Whatever. In any case: Rails.cache.write foo, bar = true Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar Rails.cache.read foo = bar On Mon, Oct 4, 2010 at 3:53 PM, Brandon Casci bran...@loudcaster.comwrote: Yep :) On Mon, Oct 4, 2010 at 4:48 PM, Teng Siong Ong siong1...@gmail.comwrote: are you sure that you are using the supported memcache gem? http://docs.heroku.com/memcache On Mon, Oct 4, 2010 at 3:43 PM, Brandon Casci bran...@loudcaster.com wrote: It's crazy making. Rails.cache.read mykey = nil Rails.cache.read mykey = nil Rails.cache.read mykey = nil Rails.cache.read mykey = 1 Rails.cache.read mykey = nil Rails.cache.read mykey = nil Rails.cache.read mykey = 1 Rails.cache.read mykey = nil Rails.cache.read mykey = nil On Sat, Oct 2, 2010 at 7:58 PM, Brandon Casci bran...@loudcaster.com wrote: Hello I'm new to Heroku, so I'm not sure if this is a problem, or normal behavior. I'm seeing a inconsistent memcache reads. Reading a key will sometimes alternate between nil and the value placed in memcache. Other times the value just seems to vanish, though that could be a sign that memcache is full, though I can't find a way to tell if it's full. What do es everyone think might be happening? -- = Brandon Casci Loudcaster http://loudcaster.com = -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group
Re: DJ Workers Crashing Without Specific Information
I can only offer commiseration because I'm in the same position as you ;) Please let me know what they say. What do your jobs do? On Thu, Sep 30, 2010 at 8:58 AM, WilliamF wflana...@tempusgroup.com wrote: Hi all, I'm looking for suggestions, as I'm not getting a response from Heroku. My background DJ workers are crashing. I can't seem to make them stay up for more than 15 or so seconds. If I look at the logs, the error message I'm getting is: RPM Monitoring DJ worker host:railgun64.29642 pid:29790 *** Starting job worker host:railgun64.29642 pid:29790 /usr/ruby1.8.7/lib/ruby/1.8/uri/common.rb:385: [BUG] Segmentation fault ruby 1.8.7 (2010-04-19 patchlevel 253) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2010.02 NewRelic doesn't show the DJ worker in its logs that I can troubleshoot. NewRelic states: RPM recorded no DelayedJob background task executions in the last 30 minutes. Which, needless to say, isn't the most helpful. I've taken every job that I can find that is outstanding and locked in the database, duplicated the data down to my local machine, and run my machine in production mode. The workers are able to process these just fine on my local machine. Given this, and the lack of response by Heroku, I'm stuck. I'd love some suggestions as to the best/next way to go to troubleshoot this problem. Background tasks are CORE to my application. If the background tasks don't work, my app is dead in the water. Help! William -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: DJ Workers Crashing Without Specific Information
William...this may sound trivial, but to your DJ workers crash if the work queues is empty? On Mon, Oct 4, 2010 at 1:08 PM, Dan Croak dcr...@thoughtbot.com wrote: There are some troubleshooting suggestions on this page: http://docs.heroku.com/ps On Mon, Oct 4, 2010 at 1:04 PM, Brandon Casci bran...@loudcaster.com wrote: I can only offer commiseration because I'm in the same position as you ;) Please let me know what they say. What do your jobs do? On Thu, Sep 30, 2010 at 8:58 AM, WilliamF wflana...@tempusgroup.com wrote: Hi all, I'm looking for suggestions, as I'm not getting a response from Heroku. My background DJ workers are crashing. I can't seem to make them stay up for more than 15 or so seconds. If I look at the logs, the error message I'm getting is: RPM Monitoring DJ worker host:railgun64.29642 pid:29790 *** Starting job worker host:railgun64.29642 pid:29790 /usr/ruby1.8.7/lib/ruby/1.8/uri/common.rb:385: [BUG] Segmentation fault ruby 1.8.7 (2010-04-19 patchlevel 253) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2010.02 NewRelic doesn't show the DJ worker in its logs that I can troubleshoot. NewRelic states: RPM recorded no DelayedJob background task executions in the last 30 minutes. Which, needless to say, isn't the most helpful. I've taken every job that I can find that is outstanding and locked in the database, duplicated the data down to my local machine, and run my machine in production mode. The workers are able to process these just fine on my local machine. Given this, and the lack of response by Heroku, I'm stuck. I'd love some suggestions as to the best/next way to go to troubleshoot this problem. Background tasks are CORE to my application. If the background tasks don't work, my app is dead in the water. Help! William -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: inconsistent Memcache reads
Yep :) On Mon, Oct 4, 2010 at 4:48 PM, Teng Siong Ong siong1...@gmail.com wrote: are you sure that you are using the supported memcache gem? http://docs.heroku.com/memcache On Mon, Oct 4, 2010 at 3:43 PM, Brandon Casci bran...@loudcaster.comwrote: It's crazy making. Rails.cache.read mykey = nil Rails.cache.read mykey = nil Rails.cache.read mykey = nil Rails.cache.read mykey = 1 Rails.cache.read mykey = nil Rails.cache.read mykey = nil Rails.cache.read mykey = 1 Rails.cache.read mykey = nil Rails.cache.read mykey = nil On Sat, Oct 2, 2010 at 7:58 PM, Brandon Casci bran...@loudcaster.comwrote: Hello I'm new to Heroku, so I'm not sure if this is a problem, or normal behavior. I'm seeing a inconsistent memcache reads. Reading a key will sometimes alternate between nil and the value placed in memcache. Other times the value just seems to vanish, though that could be a sign that memcache is full, though I can't find a way to tell if it's full. What do es everyone think might be happening? -- = Brandon Casci Loudcaster http://loudcaster.com = -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
inconsistent Memcache reads
Hello I'm new to Heroku, so I'm not sure if this is a problem, or normal behavior. I'm seeing a inconsistent memcache reads. Reading a key will sometimes alternate between nil and the value placed in memcache. Other times the value just seems to vanish, though that could be a sign that memcache is full, though I can't find a way to tell if it's full. What do es everyone think might be happening? -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: rake aborted! Don't know how to build task 'jobs:work'
Ahhh good old rake errors! See if you can get a worker to start up with --trace. See if you can kick of DelayedJob locally too..with --trace. you may get the same exception. You might find that something is preventing all the necessary tasks from loading. I was migrating over to Heroku. I had a bunch of junk in my Rakefile which was required by certain gems and plugins, but I had removed many of the things Rakefile wanted to load and my workers went splat. On Tue, Sep 28, 2010 at 2:44 AM, Chris Kalaboukis thinkfut...@gmail.comwrote: hi guys: just installed the delayed_jobs gem and am now getting this error. rake aborted! Don't know how to build task 'jobs:work' Has anyone had this error? Thanks...Chris -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
