Re: Sinatra 1.1
Thanks Oren, it's useful to know how it works and what the best thing to do is. cheers, DAZ On Oct 26, 7:58 pm, Oren Teich o...@heroku.com wrote: Both are correct. Just add a blank line and we'll pull the latest version if you havn't specified. Best practice is to pin all versions to prevent nasty surprises. Oren On Tue, Oct 26, 2010 at 11:53 AM, DAZ daz4...@gmail.com wrote: thanks Oren, I've tested it locally, so was happy to update. So would I have to just change the .gems file with something trivial to 'force' an update? Or are you saying that best practice is to always specify version numbers? cheers, DAZ On Oct 26, 7:40 pm, Oren Teich o...@heroku.com wrote: By not specifiying a gem version we will always pull the latest version when you change your .gems/gemfile. This is a bad idea however, as your app could randomly break if for example sinatra 2.0 comes out and changes an API you depend on. Oren On Tue, Oct 26, 2010 at 11:35 AM, DAZ daz4...@gmail.com wrote: Thanks Oren, I changed my .gems file to say sinatra --version 1.1 instead of just sinatra Is there any way of forcing Heroku to always go and look for the latest gems without having to specify a version number? cheers, DAZ On Oct 26, 4:30 pm, Oren Teich o...@heroku.com wrote: Simply put it in your .gems or Gemfile and you'll be all set. Oren On Tue, Oct 26, 2010 at 5:58 AM, DAZ daz4...@gmail.com wrote: Hi, Sinatra upgraded to version 1.1 yesterday. Is this version available on Heroku and how do I update current apps that are using Sinatra to the new version? cheers, DAZ -- 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 athttp://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 athttp://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 athttp://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: Has anyone got pony working with gmail on heroku?
On Wed, Oct 27, 2010 at 12:23 PM, Phil Pirozhkov pirjs...@gmail.com wrote: look at padrino mailer if you are using sinatra, or active mailer if rails tmail gem is outdated, and pony depends on it you can either patch tmail or use patched as provided by tools i've mentioned you can also use SendGrid or any alternative addon I got sendgrid working. It was pretty straightforward. I followed the instructions on the heroku site directly. -- http://richardconroy.blogspot.com | http://twitter.com/RichardConroy -- 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.
SOLVED: Has anyone got pony working with gmail on heroku?
I figured it out, I had used an example from http://github.com/benprew/pony
Works locally, doesn't work on heroku
Pony.mail :to = ENV['TO_EMAIL'],
:from = params[:email],
:subject = params[:subject],
:via_options = {
:address = 'smtp.gmail.com',
:port = '587',
:enable_starttls_auto = true,
:user_name = ENV['GMAIL_USER'],
:password = ENV['GMAIL_PASSWORD'],
:authentication = :plain,
# :plain, :login, :cram_md5, no auth by default
:domain = wavesummit.com # the HELO
domain provided by the client to the server
}
However after reading http://blog.jpoz.net/2009/09/02/gmail-heroku-sinatra.html
and also cheking out adams page github http://github.com/adamwiggins/pony
This code below worked.
Pony.mail :to = ENV['TO_EMAIL'],
:from = params[:email],
:subject = params[:subject],
:via = :smtp,
:smtp = {
:address = 'smtp.gmail.com',
:port = '587',
:user_name = ENV['GMAIL_USER'],
:password = ENV['GMAIL_PASSWORD'],
:authentication = :plain,
# :plain, :login, :cram_md5, no auth by default
:domain = wavesummit.com # the HELO
domain provided by the client to the server
}
Another gotcha is that in order to install pony rubygems needs to be
at least 1.3.6, debian only offers 1.3.5 through apt-get
On Oct 26, 6:04 pm, Jimmy moxley.ja...@googlemail.com wrote:
Pony works locally, but on heroku I get the following:
2010-10-25 16:07:48 1PAW8q-0006J3-Qr Failed to create spool file /var/
spool/exim4/input//1PAW8q-0006J3-Qr-D: Permission denied
2010-10-25 16:07:48 1PAW8q-0006J3-Qr Failed to create spool file /var/
spool/exim4/input//1PAW8q-0006J3-Qr-D: Permission denied
2010-10-25 16:07:48 1PAW8q-0006J3-Qr Failed to create spool file /var/
spool/exim4/input//1PAW8q-0006J3-Qr-D: Permission denied
Is there a solution or alternative to sending mail from Sinatra using
Gmail and Pony?
--
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
You can browse the incident archive here: http://status.heroku.com/past Most of the issues seems to be related to tooling, but there was at least one other case of app outage earlier in the month (Oct. 4) Does Heroku publish uptime numbers? Does anyone running an app in production (I'm still not yet...) have app uptime numbers they're willing to share? On Oct 26, 7: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.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
Al, I'm afraid Heroku's had a fair bit of downtime since I've joined earlier this year. The status link mattsly gave you paints a pretty grim picture. I figure I'll probably have to come up with something else once my site's uptime becomes important to me. I'm hoping they stop adding new features, and instead pour themselves into stability. On Oct 27, 8:11 am, mattsly matt...@gmail.com wrote: You can browse the incident archive here:http://status.heroku.com/past Most of the issues seems to be related to tooling, but there was at least one other case of app outage earlier in the month (Oct. 4) Does Heroku publish uptime numbers? Does anyone running an app in production (I'm still not yet...) have app uptime numbers they're willing to share? On Oct 26, 7: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.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Dalli memcached not hitting the cache
I found out yesterday that for Dalli versions =0.10.1, you don't need
to specify ENV['MEMCACHE_SERVERS'].
http://github.com/mperham/dalli/wiki/Heroku-Configuration
On Oct 24, 5:32 pm, Joost Schuur jsch...@jschuur.com wrote:
That did the trick for me. Thanks so much!
Heroku ought to have this listed on the docs page. I'll drop them a
note if they're not already seeing this.
/j
On Oct 24, 12:53 pm, arailsdemo arailsd...@gmail.com wrote:
I just figured this out today. I wrote it up here
(http://www.arailsdemo.com/posts/17). Basically, you have to configure Dalli
to use the Heroku memcache server. Simply change your config to:
# production.rb
config.action_controller.perform_caching = true
config.cache_store = :dalli_store, ENV['MEMCACHE_SERVERS']
(BTW: I was also having problems installing memcached-northscale. I
think this had to do with using ruby 1.9.2. If you're using RVM just
switch to ruby 1.8.7.)
Good luck.
On Oct 18, 6:40 am, Joost Schuur jsch...@jschuur.com wrote:
I've been experimenting with memcached and read good things about the
dalli gem, so I thought I'd try it out on Heroku. I can't seem to get
it to work and m not getting back any obvious errors either.
My production.rb defines:
config.action_controller.perform_caching = true
config.cache_store = :dalli_store
...and in my Gemfile:
gem 'dalli'
However, based on the logs, it's not reading from the cache. Upon
refreshing the page in question twice (to make sure the cache was
written the first time around), I still get this:
Exist fragment? views/front_sidebar (506.9ms)
Write fragment views/front_sidebar (508.3ms)
Likewise, from the heroku console for the app in question:
Rails.cache.write('hello', 'world')
= false
Rails.cache.read('hello')
= nil
I've restarted the heroku server during my tests too, and have
confirmed that I have the add-on installed (the app name is
tvgridthing-stage, if a Heroku rep would like to take a look).
I don't know what other debug tools there are for dalli. I tried
checking the stats, but the instructions
athttp://docs.heroku.com/memcache#getting-stats-on-usage
obviously don't apply to dalli, which doesn't seem to have a stats
command.
Locally on my Mac, things seem to work just fine, based on the
presence of 'Read fragment views/front_sidebar (0.0ms)' in the logs.
I'm running Rails 3.0.1 and dalli 0.10.0 FWIW.
Then I thought I'd try the standard memcached instead, so I added this
to my Gemfile
group :production do
gem memcache-client
gem 'memcached-northscale', :require = 'memcached'
end
...and in production.rb:
config.cache_store = :mem_cache_store, Memcached::Rails.new
Unfortunately, despite the :production group, when I went to do a
bundle install locally first, it tries to compile native extensions
under Mac OS X for memcached-northscale, and I get a compile error
that's been discussed here too:
http://osdir.com/ml/ruby-talk/2010-02/msg01693.html
Should I be able to tell bundle what environment to run under, so that
it'll ignore that on development and thus bypass any attempt to
install memcached-norrthscale?
--
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
I'd be curious to find out what the actual uptime percentage is, and what it would cost you to maintain that on a different platform with comparable services. :) Jimmy On Wed, Oct 27, 2010 at 9:55 AM, JDeville jeffdevi...@gmail.com wrote: Al, I'm afraid Heroku's had a fair bit of downtime since I've joined earlier this year. The status link mattsly gave you paints a pretty grim picture. I figure I'll probably have to come up with something else once my site's uptime becomes important to me. I'm hoping they stop adding new features, and instead pour themselves into stability. On Oct 27, 8:11 am, mattsly matt...@gmail.com wrote: You can browse the incident archive here:http://status.heroku.com/past Most of the issues seems to be related to tooling, but there was at least one other case of app outage earlier in the month (Oct. 4) Does Heroku publish uptime numbers? Does anyone running an app in production (I'm still not yet...) have app uptime numbers they're willing to share? On Oct 26, 7: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. -- +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.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: RubyAMF
Anyone? I'd rather not go headlong down a blind alley. Does anyone from heroku read this group? Thanks On Oct 22, 9:32 pm, paul h p...@hollyer.me.uk wrote: Hi, I am moving my apps from AptanaCloud to heroku, and so far so good. I am also switching from Windows to Linux - finally!! :) The only problem I have come across so far, is connecting to my app via RubyAMF. I need this because my front end is all Flex. My question, then, (before I potentially, waste time going round in circles), is: Are there any issues on heroku that would prevent me from connecting via RubyAMF? I am happy to look at solving my problem myself, but I'd rather not waste time trying if something on heroku prevents me from using the RubyAMF Plugin. I have searched the group, and the only post I can find is a couple of years old, so it may not be relevant. Thanks Paul -- 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
unexpected downtown is way different than planned downtown. This is really discomforting. I'm not looking forward in moving my production app to more stable place... heroku should really answer this. On Oct 27, 7:19 pm, Jimmy Thrasher ji...@jimmythrasher.com wrote: Interesting. So, back of the envelope, from a dev perspective: ruby-1.8.7-p302 elapsed = (Time.local(2010,10,26,16) - Time.local(2010,8,1)) / 60 =124800.0 ruby-1.8.7-p302 (elapsed - 45 - 28 - 45) / elapsed = 0.999054487179487 About 99.9% uptime over the elapsed time. It's still way cheaper for me to use Heroku, but the cost of 30 minutes of downtime in a month is fairly low. Folks with higher uptime requirements are likely just going to have to shell out the $$$ no matter which way you slice it. Jimmy On Wed, Oct 27, 2010 at 12:54 PM, John Norman j...@7fff.com wrote: Below is the data I have for one app (similar data from two other apps). So, for September, 28 minutes of downtime . . . better than 3 nines: http://en.wikipedia.org/wiki/High_availability#Percentage_calculation But I would much rather report to my customers official data from Heroku. The times below are central time zone, I think. AUGUST - Total unavailable minutes: 45 unavail at avail at elapsed 8/4/2010 17:06:00 8/4/2010 17:51:00 0:45:00 SEPTEMBER - Total unavailable minutes: 28 9/13/2010 8:46:00 9/13/2010 8:55:00 0:09:00 9/13/2010 14:26:00 9/13/2010 14:36:00 0:10:00 9/21/2010 1:16:00 9/21/2010 1:21:00 0:05:00 9/28/2010 22:26:00 9/28/2010 22:30:00 0:04:00 OCTOBER - Total unavailable minutes so far: 45 10/4/2010 15:41:00 10/4/2010 15:51:00 0:10:00 10/5/2010 11:56:00 10/5/2010 12:01:00 0:05:00 10/26/2010 12:16:00 10/26/2010 12:26:00 0:10:00 10/26/2010 14:41:00 10/26/2010 14:46:00 0:05:00 10/26/2010 15:21:00 10/26/2010 15:36:00 0:15:00 On Wed, Oct 27, 2010 at 9:53 AM, Jimmy Thrasher ji...@jimmythrasher.comwrote: I'd be curious to find out what the actual uptime percentage is, and what it would cost you to maintain that on a different platform with comparable services. :) Jimmy On Wed, Oct 27, 2010 at 9:55 AM, JDeville jeffdevi...@gmail.com wrote: Al, I'm afraid Heroku's had a fair bit of downtime since I've joined earlier this year. The status link mattsly gave you paints a pretty grim picture. I figure I'll probably have to come up with something else once my site's uptime becomes important to me. I'm hoping they stop adding new features, and instead pour themselves into stability. On Oct 27, 8:11 am, mattsly matt...@gmail.com wrote: You can browse the incident archive here:http://status.heroku.com/past Most of the issues seems to be related to tooling, but there was at least one other case of app outage earlier in the month (Oct. 4) Does Heroku publish uptime numbers? Does anyone running an app in production (I'm still not yet...) have app uptime numbers they're willing to share? On Oct 26, 7: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. -- +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. -- 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. --+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.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Postmortem on Tuesday's outage
We have posted a postmortem on Tuesday's outage on our blog: http://blog.heroku.com/archives/2010/10/27/tuesday_postmortem/ Oren -- 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: Has anyone got pony working with gmail on heroku?
2010/10/26 Jimmy moxley.ja...@googlemail.com: Pony works locally, but on heroku I get the following: It's working fine for me. Have you declared the gem smtp_tls in your .gems file? Here you have the code. http://gist.github.com/648619 2010-10-25 16:07:48 1PAW8q-0006J3-Qr Failed to create spool file /var/ spool/exim4/input//1PAW8q-0006J3-Qr-D: Permission denied 2010-10-25 16:07:48 1PAW8q-0006J3-Qr Failed to create spool file /var/ spool/exim4/input//1PAW8q-0006J3-Qr-D: Permission denied 2010-10-25 16:07:48 1PAW8q-0006J3-Qr Failed to create spool file /var/ spool/exim4/input//1PAW8q-0006J3-Qr-D: Permission denied Is there a solution or alternative to sending mail from Sinatra using Gmail and Pony? -- 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. -- - Pedro Del Gallego Email : pedro.delgall...@gmail.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.
Delayed_job worker + paperclip + s3 error
Hi all, I'm implementing a simple photo upload test app that uses paperclip 2.3.5 for the upload, S3 for storage, and delayed_job + ImageMagick for photo resizing. It works fine on my local development machine, but on heroku (I've got a worker running), the worker dies with this error: last_error = 'The specified key does not exist. /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/aws-s3-0.6.2/lib/aws/s3/error.rb:38:in `raise'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/aws-s3-0.6.2/lib/aws/s3/base.rb:72:in `request'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/aws-s3-0.6.2/lib/aws/s3/base.rb:88:in `get'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/aws-s3-0.6.2/lib/aws/s3/object.rb: 134:in `value'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/paperclip-2.3.5/lib/paperclip/storage/ s3.rb:134:in `to_file'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/paperclip-2.3.5/lib/paperclip/ attachment.rb:219:in `reprocess!'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/app/models/photo.rb:29:in `regenerate_styles!'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/lib/photo_job.rb:3:in `perform'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:217:in `invoke_job'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:92:in `run_with_lock'' /usr/ruby1.8.7/lib/ruby/1.8/benchmark.rb:308:in `realtime'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:91:in `run_with_lock'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:155:in `reserve_and_run_one_job'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:154:in `each'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:154:in `reserve_and_run_one_job'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:201:in `work_off'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:200:in `times'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:200:in `work_off'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/worker.rb: 28:in `start'' /usr/ruby1.8.7/lib/ruby/1.8/benchmark.rb:308:in `realtime'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/worker.rb: 27:in `start'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/worker.rb: 24:in `loop'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/worker.rb: 24:in `start'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/tasks/tasks.rb:13 /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain'' /usr/ruby1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/
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: Delayed_job worker + paperclip + s3 error
Actually solved it. It turns out it was a red herring: the S3 error is actually just a transient issue caused by the DJ worker being on a different host. The real issue is that I had the last_error column of my delayed_jobs table as string rather than text, causing this to die with a PostgresSQL exception because of last_error being too long, and the S3 write is never re-attempted. Changing the column type to text made things work fine because the S3 error goes away after a few seconds. On Oct 27, 3:40 am, Mark Wang mark.w...@gmail.com wrote: Hi all, I'm implementing a simple photo upload test app that uses paperclip 2.3.5 for the upload, S3 for storage, and delayed_job + ImageMagick for photo resizing. It works fine on my local development machine, but on heroku (I've got a worker running), the worker dies with this error: last_error = 'The specified key does not exist. /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/aws-s3-0.6.2/lib/aws/s3/error.rb:38:in `raise'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/aws-s3-0.6.2/lib/aws/s3/base.rb:72:in `request'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/aws-s3-0.6.2/lib/aws/s3/base.rb:88:in `get'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/aws-s3-0.6.2/lib/aws/s3/object.rb: 134:in `value'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/paperclip-2.3.5/lib/paperclip/storage/ s3.rb:134:in `to_file'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/paperclip-2.3.5/lib/paperclip/ attachment.rb:219:in `reprocess!'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/app/models/photo.rb:29:in `regenerate_styles!'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/lib/photo_job.rb:3:in `perform'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:217:in `invoke_job'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:92:in `run_with_lock'' /usr/ruby1.8.7/lib/ruby/1.8/benchmark.rb:308:in `realtime'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:91:in `run_with_lock'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:155:in `reserve_and_run_one_job'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:154:in `each'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:154:in `reserve_and_run_one_job'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:201:in `work_off'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:200:in `times'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/job.rb:200:in `work_off'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/worker.rb: 28:in `start'' /usr/ruby1.8.7/lib/ruby/1.8/benchmark.rb:308:in `realtime'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/worker.rb: 27:in `start'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/worker.rb: 24:in `loop'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/lib/delayed/worker.rb: 24:in `start'' /disk1/home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5- b4c7f19aace0/mnt/vendor/plugins/delayed_job/tasks/tasks.rb:13 /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute'' /home/slugs/321931_787afbf_9e88-aba30188-0172-47bf-bcf5-b4c7f19aace0/ mnt/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:597:in
