Re: Delayed jobs failing with suspicious backtrace
Awesome Awesome Awesome, all is well. Thanks for the quick fix!
On Feb 19, 7:32 pm, Oren Teich wrote:
> OK, I was totally wrong. There was a bug with New Relic that JUST popped
> up. We hot patched the new relic plugin, and things look good now. You can
> simply repush your code or change a config var, and all should be working
> again.
>
> ORen
>
> On Fri, Feb 19, 2010 at 4:51 PM, Higgaion wrote:
>
>
>
> > Well I can't uninstall new relic from the cli because I am not the app
> > owner, so I tried to log in as him and remove it via the web site and
> > noticed a bug there:
>
> > Click "Use or configure this addon"
> > Scroll to the bottom of the screen and click "Remove Add-on"
> > Confirm the js dialog
> > a 404 error page loads ("sorry, champ...") and new relic is still
> > installed to my app.
>
> > I'll figure out how to become app owner and remove it from the CLI.
>
> > On Feb 19, 5:42 pm, Doug Petkanics wrote:
> > > I had this issue this week and Heroku support suggested I disable New
> > Relic
> > > add-on since their updated gem didn't play nice with Delayed Job. I did,
> > and
> > > it immediately started working again.
>
> > > Heroku guys, any idea when we'll be able to re-enable New Relic?
>
> > > On Fri, Feb 19, 2010 at 6:38 PM, Higgaion > >wrote:
>
> > > > My jobs don't seem to be running automatically, so I tried to start a
> > > > worker with heroku rake:
>
> > > > heroku rake --trace jobs:work
> > > > (in /disk1/home/slugs/125600_b30055f_55f0/mnt)
> > > > ** Invoke jobs:work (first_time)
> > > > ** Invoke merb_env (first_time)
> > > > ** Execute merb_env
> > > > ** Invoke environment (first_time)
> > > > ** Execute environment
> > > > ** Execute jobs:work
> > > > rake aborted!
> > > > undefined method `info' for nil:NilClass
> > > > /disk1/home/slugs/125600_b30055f_55f0/mnt/vendor/plugins/rpm/lib/
> > > > new_relic/delayed_job_injection.rb:18:in `initialize'
> > > > :
> > > > :
>
> > > > Two general categories of questions come to mind:
>
> > > > 1) What is that new_relic thing trying to do? where is the source code
> > > > for that? what info? where am I?
>
> > > > 2) How to I fix it?
>
> > > > --
> > > > 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
> > > 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.
--
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 jobs failing with suspicious backtrace
OK, I was totally wrong. There was a bug with New Relic that JUST popped
up. We hot patched the new relic plugin, and things look good now. You can
simply repush your code or change a config var, and all should be working
again.
ORen
On Fri, Feb 19, 2010 at 4:51 PM, Higgaion wrote:
> Well I can't uninstall new relic from the cli because I am not the app
> owner, so I tried to log in as him and remove it via the web site and
> noticed a bug there:
>
> Click "Use or configure this addon"
> Scroll to the bottom of the screen and click "Remove Add-on"
> Confirm the js dialog
> a 404 error page loads ("sorry, champ...") and new relic is still
> installed to my app.
>
> I'll figure out how to become app owner and remove it from the CLI.
>
>
> On Feb 19, 5:42 pm, Doug Petkanics wrote:
> > I had this issue this week and Heroku support suggested I disable New
> Relic
> > add-on since their updated gem didn't play nice with Delayed Job. I did,
> and
> > it immediately started working again.
> >
> > Heroku guys, any idea when we'll be able to re-enable New Relic?
> >
> > On Fri, Feb 19, 2010 at 6:38 PM, Higgaion >wrote:
> >
> >
> >
> > > My jobs don't seem to be running automatically, so I tried to start a
> > > worker with heroku rake:
> >
> > > heroku rake --trace jobs:work
> > > (in /disk1/home/slugs/125600_b30055f_55f0/mnt)
> > > ** Invoke jobs:work (first_time)
> > > ** Invoke merb_env (first_time)
> > > ** Execute merb_env
> > > ** Invoke environment (first_time)
> > > ** Execute environment
> > > ** Execute jobs:work
> > > rake aborted!
> > > undefined method `info' for nil:NilClass
> > > /disk1/home/slugs/125600_b30055f_55f0/mnt/vendor/plugins/rpm/lib/
> > > new_relic/delayed_job_injection.rb:18:in `initialize'
> > > :
> > > :
> >
> > > Two general categories of questions come to mind:
> >
> > > 1) What is that new_relic thing trying to do? where is the source code
> > > for that? what info? where am I?
> >
> > > 2) How to I fix it?
> >
> > > --
> > > 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.
>
>
--
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 jobs failing with suspicious backtrace
Sounds like a weird bug - we'll look into it.
FYI, the new relic plugin shouldn't cause any issues - that may be a
misleading error. There are thousands of people using the add-on & workers
already.
Oren
On Fri, Feb 19, 2010 at 4:51 PM, Higgaion wrote:
> Well I can't uninstall new relic from the cli because I am not the app
> owner, so I tried to log in as him and remove it via the web site and
> noticed a bug there:
>
> Click "Use or configure this addon"
> Scroll to the bottom of the screen and click "Remove Add-on"
> Confirm the js dialog
> a 404 error page loads ("sorry, champ...") and new relic is still
> installed to my app.
>
> I'll figure out how to become app owner and remove it from the CLI.
>
>
> On Feb 19, 5:42 pm, Doug Petkanics wrote:
> > I had this issue this week and Heroku support suggested I disable New
> Relic
> > add-on since their updated gem didn't play nice with Delayed Job. I did,
> and
> > it immediately started working again.
> >
> > Heroku guys, any idea when we'll be able to re-enable New Relic?
> >
> > On Fri, Feb 19, 2010 at 6:38 PM, Higgaion >wrote:
> >
> >
> >
> > > My jobs don't seem to be running automatically, so I tried to start a
> > > worker with heroku rake:
> >
> > > heroku rake --trace jobs:work
> > > (in /disk1/home/slugs/125600_b30055f_55f0/mnt)
> > > ** Invoke jobs:work (first_time)
> > > ** Invoke merb_env (first_time)
> > > ** Execute merb_env
> > > ** Invoke environment (first_time)
> > > ** Execute environment
> > > ** Execute jobs:work
> > > rake aborted!
> > > undefined method `info' for nil:NilClass
> > > /disk1/home/slugs/125600_b30055f_55f0/mnt/vendor/plugins/rpm/lib/
> > > new_relic/delayed_job_injection.rb:18:in `initialize'
> > > :
> > > :
> >
> > > Two general categories of questions come to mind:
> >
> > > 1) What is that new_relic thing trying to do? where is the source code
> > > for that? what info? where am I?
> >
> > > 2) How to I fix it?
> >
> > > --
> > > 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.
>
>
--
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 jobs failing with suspicious backtrace
Well I can't uninstall new relic from the cli because I am not the app
owner, so I tried to log in as him and remove it via the web site and
noticed a bug there:
Click "Use or configure this addon"
Scroll to the bottom of the screen and click "Remove Add-on"
Confirm the js dialog
a 404 error page loads ("sorry, champ...") and new relic is still
installed to my app.
I'll figure out how to become app owner and remove it from the CLI.
On Feb 19, 5:42 pm, Doug Petkanics wrote:
> I had this issue this week and Heroku support suggested I disable New Relic
> add-on since their updated gem didn't play nice with Delayed Job. I did, and
> it immediately started working again.
>
> Heroku guys, any idea when we'll be able to re-enable New Relic?
>
> On Fri, Feb 19, 2010 at 6:38 PM, Higgaion wrote:
>
>
>
> > My jobs don't seem to be running automatically, so I tried to start a
> > worker with heroku rake:
>
> > heroku rake --trace jobs:work
> > (in /disk1/home/slugs/125600_b30055f_55f0/mnt)
> > ** Invoke jobs:work (first_time)
> > ** Invoke merb_env (first_time)
> > ** Execute merb_env
> > ** Invoke environment (first_time)
> > ** Execute environment
> > ** Execute jobs:work
> > rake aborted!
> > undefined method `info' for nil:NilClass
> > /disk1/home/slugs/125600_b30055f_55f0/mnt/vendor/plugins/rpm/lib/
> > new_relic/delayed_job_injection.rb:18:in `initialize'
> > :
> > :
>
> > Two general categories of questions come to mind:
>
> > 1) What is that new_relic thing trying to do? where is the source code
> > for that? what info? where am I?
>
> > 2) How to I fix it?
>
> > --
> > 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: Delayed jobs failing with suspicious backtrace
new relic is an addon - http://addons.heroku.com/newrelic What's your workers set to? Run heroku workers to see, heroku workers 1 to start up a aworker consuming your DJ jobs. You can also run heroku ps to see what is running. Oren On Fri, Feb 19, 2010 at 3:38 PM, Higgaion wrote: > My jobs don't seem to be running automatically, so I tried to start a > worker with heroku rake: > > heroku rake --trace jobs:work > (in /disk1/home/slugs/125600_b30055f_55f0/mnt) > ** Invoke jobs:work (first_time) > ** Invoke merb_env (first_time) > ** Execute merb_env > ** Invoke environment (first_time) > ** Execute environment > ** Execute jobs:work > rake aborted! > undefined method `info' for nil:NilClass > /disk1/home/slugs/125600_b30055f_55f0/mnt/vendor/plugins/rpm/lib/ > new_relic/delayed_job_injection.rb:18:in `initialize' > : > : > > Two general categories of questions come to mind: > > 1) What is that new_relic thing trying to do? where is the source code > for that? what info? where am I? > > 2) How to I fix it? > > -- > 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: Delayed jobs failing with suspicious backtrace
New Relic is aware of the issue and has a fix so it just has to make it out to the gem. I'd imagine a few days at most. On Fri, Feb 19, 2010 at 6:42 PM, Doug Petkanics wrote: > I had this issue this week and Heroku support suggested I disable New Relic > add-on since their updated gem didn't play nice with Delayed Job. I did, and > it immediately started working again. > Heroku guys, any idea when we'll be able to re-enable New Relic? > > On Fri, Feb 19, 2010 at 6:38 PM, Higgaion > wrote: >> >> My jobs don't seem to be running automatically, so I tried to start a >> worker with heroku rake: >> >> heroku rake --trace jobs:work >> (in /disk1/home/slugs/125600_b30055f_55f0/mnt) >> ** Invoke jobs:work (first_time) >> ** Invoke merb_env (first_time) >> ** Execute merb_env >> ** Invoke environment (first_time) >> ** Execute environment >> ** Execute jobs:work >> rake aborted! >> undefined method `info' for nil:NilClass >> /disk1/home/slugs/125600_b30055f_55f0/mnt/vendor/plugins/rpm/lib/ >> new_relic/delayed_job_injection.rb:18:in `initialize' >> : >> : >> >> Two general categories of questions come to mind: >> >> 1) What is that new_relic thing trying to do? where is the source code >> for that? what info? where am I? >> >> 2) How to I fix it? >> >> -- >> 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. > -- 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 jobs failing with suspicious backtrace
I had this issue this week and Heroku support suggested I disable New Relic add-on since their updated gem didn't play nice with Delayed Job. I did, and it immediately started working again. Heroku guys, any idea when we'll be able to re-enable New Relic? On Fri, Feb 19, 2010 at 6:38 PM, Higgaion wrote: > My jobs don't seem to be running automatically, so I tried to start a > worker with heroku rake: > > heroku rake --trace jobs:work > (in /disk1/home/slugs/125600_b30055f_55f0/mnt) > ** Invoke jobs:work (first_time) > ** Invoke merb_env (first_time) > ** Execute merb_env > ** Invoke environment (first_time) > ** Execute environment > ** Execute jobs:work > rake aborted! > undefined method `info' for nil:NilClass > /disk1/home/slugs/125600_b30055f_55f0/mnt/vendor/plugins/rpm/lib/ > new_relic/delayed_job_injection.rb:18:in `initialize' > : > : > > Two general categories of questions come to mind: > > 1) What is that new_relic thing trying to do? where is the source code > for that? what info? where am I? > > 2) How to I fix it? > > -- > 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.
Delayed jobs failing with suspicious backtrace
My jobs don't seem to be running automatically, so I tried to start a worker with heroku rake: heroku rake --trace jobs:work (in /disk1/home/slugs/125600_b30055f_55f0/mnt) ** Invoke jobs:work (first_time) ** Invoke merb_env (first_time) ** Execute merb_env ** Invoke environment (first_time) ** Execute environment ** Execute jobs:work rake aborted! undefined method `info' for nil:NilClass /disk1/home/slugs/125600_b30055f_55f0/mnt/vendor/plugins/rpm/lib/ new_relic/delayed_job_injection.rb:18:in `initialize' : : Two general categories of questions come to mind: 1) What is that new_relic thing trying to do? where is the source code for that? what info? where am I? 2) How to I fix it? -- 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: Caching advice for mostly private pages
memcache is the correct approach. It's currently in closed beta, though we are just a few weeks away from public beta with it, and aiming for mid march GA release. There's one outstanding issue preventing us from moving to public beta. As soon as that is resolved, we'll push it out. Oren On Fri, Feb 19, 2010 at 2:48 AM, Jamie Lawrence wrote: > From what I can tell about the Heroku setup, Varnish is perfect for > caching static public pages (i.e., my homepage, features page etc) but > what about the rest? > > My login page is public and mostly static but the error messages > aren't, so Varnish isn't going to work there. > > Then the rest of my app consists of private pages of data, which is > updated by backend processes. I'd have used fragment caching to file > but this isn't supported so I guess the only option is memcache? Can > anyone use this addon or is it a closed-beta? > > Thanks, > > Jamie > > -- > 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: require 'bundled-gem' -- no such file to load
We fixed an issue with bundler earlier this week. Push a change o your Gemfile and it should work. On Fri, Feb 19, 2010 at 2:22 AM, orlin wrote: > Something I noticed is when I run $ "bundle show" and when no gems > other than bundler are installed (clean rvm) - nokogiri is the first > to be found missing "Could not find gem 'nokogiri (= 1.4.1, runtime)' > in any of the sources.". It's not the first (very far down in the > Gemfile), and otherwise, both "bundle install" and "bundle show" > install / list the gems in alphabetical order. So it could be that > the dyno can't find its installed gems (or that the gems aren't > actually installed)... > > On Feb 17, 7:08 pm, "Matthew A. Brown" wrote: >> I'm having the same problem with Nokogiri. >> >> On Wed, Feb 17, 2010 at 12:07, orlin wrote: >> > Toadhopper doesn't find Nokogiri, after upgrading to the latest >> > Bundler. The gem is bundled, and locked, and Heroku says: "Installing >> > nokogiri (1.4.1) from rubygems repository athttp://gemcutter.orgwith >> > native extensions" upon push. >> >> > I deployed herehttp://freezing-sunset-88.heroku.com/- a temp app to >> > illustrate the issue. >> >> > Orlin >> >> > -- >> > 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. > > -- 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: app keep winding down
I applied the configuration outlined at http://wiki.github.com/railsdog/spree/spree-on-heroku. Worked. Thanks for everyone's help. L On Feb 17, 11:46 am, Glenn Rempe wrote: > I am using Compass with several apps on Heroku. Compass compiles the > stylesheets (.css) to public/stylesheets/compiled for me and what I > have done is to check those compiled CSS output files into my Git repo > that gets pushed to Heroku. > > I did not have to specifically modify the config at all to work on > Heroku. I initially setup and configured compass using the scripts > provided here: > > http://wiki.github.com/chriseppstein/compass/ruby-on-rails-integration > > HTH > > G > > On Feb 17, 9:34 am, sslguy wrote: > > > Thanks for the response. So I'm thinking I should disable compass. Has > > anyone gotten compass to work on Heroku? > > > On Feb 16, 9:13 pm, bdeank wrote: > > > > Looks like compass is trying to recompile your stylesheets, and can't > > > because Heroku FS is read-only. > > > > On Feb 16, 8:54 pm, sslguy wrote: > > > > > Here is what I was able to pull from the logs immediately following a > > > > 500 error: > > > > > ==> dyno-878231.log <== > > > > config.gem: Unpacked gem environment.rb in vendor/gems has no > > > > specification file. Run 'rake gems:refresh_specs' to fix this. > > > > config.gem: Unpacked gem environment.rb in vendor/gems not in a > > > > versioned directory. Giving up. > > > > config.gem: Unpacked gem ruby in vendor/gems has no specification > > > > file. Run 'rake gems:refresh_specs' to fix this. > > > > config.gem: Unpacked gem ruby in vendor/gems not in a versioned > > > > directory. Giving up. > > > > > ==> production.log <== > > > > # Logfile created on Tue Feb 16 17:50:59 -0800 2010 > > > > > Processing ApplicationController#new (for 98.201.58.81 at 2010-02-16 > > > > 17:51:00) [GET] > > > > > Errno::EROFS (Read-only file system - /disk1/home/slugs/ > > > > 129005_3d87b71_003c/mnt/public/stylesheets/compiled/ie.css - Heroku > > > > has a read-only filesystem. > > > > Seehttp://docs.heroku.com/constraints#read-only-filesystem): > > > > haml (2.2.3) rails/./lib/sass/plugin.rb:79:in `delete' > > > > haml (2.2.3) rails/./lib/sass/plugin.rb:79:in `update_stylesheet' > > > > haml (2.2.3) rails/./lib/sass/plugin.rb:69:in `update_stylesheets' > > > > haml (2.2.3) rails/./lib/sass/plugin.rb:64:in `each' > > > > haml (2.2.3) rails/./lib/sass/plugin.rb:64:in `update_stylesheets' > > > > haml (2.2.3) rails/./lib/sass/plugin.rb:62:in `each' > > > > haml (2.2.3) rails/./lib/sass/plugin.rb:62:in `update_stylesheets' > > > > haml (2.2.3) rails/./lib/sass/plugin/rails.rb:16:in > > > > `process_without_compass' > > > > /home/slugs/129005_3d87b71_003c/mnt/.gems/gems/chriseppstein- > > > > compass-0.8.17/lib/compass/app_integration/rails/action_controller.rb: > > > > 7:in `process' > > > > /home/heroku_rack/lib/static_assets.rb:9:in `call' > > > > /home/heroku_rack/lib/last_access.rb:25:in `call' > > > > /home/heroku_rack/lib/date_header.rb:14:in `call' > > > > thin (1.0.1) lib/thin/connection.rb:80:in `pre_process' > > > > thin (1.0.1) lib/thin/connection.rb:78:in `catch' > > > > thin (1.0.1) lib/thin/connection.rb:78:in `pre_process' > > > > thin (1.0.1) lib/thin/connection.rb:57:in `process' > > > > thin (1.0.1) lib/thin/connection.rb:42:in `receive_data' > > > > eventmachine (0.12.6) lib/eventmachine.rb:240:in `run_machine' > > > > eventmachine (0.12.6) lib/eventmachine.rb:240:in `run' > > > > thin (1.0.1) lib/thin/backends/base.rb:57:in `start' > > > > thin (1.0.1) lib/thin/server.rb:150:in `start' > > > > thin (1.0.1) lib/thin/controllers/controller.rb:80:in `start' > > > > thin (1.0.1) lib/thin/runner.rb:173:in `send' > > > > thin (1.0.1) lib/thin/runner.rb:173:in `run_command' > > > > thin (1.0.1) lib/thin/runner.rb:139:in `run!' > > > > thin (1.0.1) bin/thin:6 > > > > /usr/local/bin/thin:20:in `load' > > > > /usr/local/bin/thin:20 > > > > > Rendering /disk1/home/slugs/129005_3d87b71_003c/mnt/public/500.html > > > > (500 Internal Server Error) > > > > > Any ideas? > > > > > On Feb 16, 12:42 am, Pedro Belo wrote: > > > > > > Do you see anything by running heroku logs? > > > > > 500s are caused by the application, so you should find the source of > > > > > it in the logs. > > > > > > On Mon, Feb 15, 2010 at 9:32 PM, sslguy > > > > > wrote: > > > > > > Looks like the problem still exists :( > > > > > > > On Feb 15, 4:42 pm, sslguy wrote: > > > > > >> Thanks for your prompt response. I'll check back in a while to see > > > > > >> if > > > > > >> the 500 error resurfaces. > > > > > > >> On Feb 15, 11:14 am, Oren Teich wrote: > > > > > > >> > While free apps do cycle down after a few hours of inactivity, > > > > > >> > you should > > > > > >> > never get a 500 error. That's something we'll have to look into. > > > > > > >> > Oren > > > > > > >> > 2010/2/15 Nicolás Sanguinetti > > > > > > >> > > On Mon, Feb 15, 2010 at 2:15 PM, s
Caching advice for mostly private pages
>From what I can tell about the Heroku setup, Varnish is perfect for caching static public pages (i.e., my homepage, features page etc) but what about the rest? My login page is public and mostly static but the error messages aren't, so Varnish isn't going to work there. Then the rest of my app consists of private pages of data, which is updated by backend processes. I'd have used fragment caching to file but this isn't supported so I guess the only option is memcache? Can anyone use this addon or is it a closed-beta? Thanks, Jamie -- 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: require 'bundled-gem' -- no such file to load
Something I noticed is when I run $ "bundle show" and when no gems other than bundler are installed (clean rvm) - nokogiri is the first to be found missing "Could not find gem 'nokogiri (= 1.4.1, runtime)' in any of the sources.". It's not the first (very far down in the Gemfile), and otherwise, both "bundle install" and "bundle show" install / list the gems in alphabetical order. So it could be that the dyno can't find its installed gems (or that the gems aren't actually installed)... On Feb 17, 7:08 pm, "Matthew A. Brown" wrote: > I'm having the same problem with Nokogiri. > > On Wed, Feb 17, 2010 at 12:07, orlin wrote: > > Toadhopper doesn't find Nokogiri, after upgrading to the latest > > Bundler. The gem is bundled, and locked, and Heroku says: "Installing > > nokogiri (1.4.1) from rubygems repository athttp://gemcutter.orgwith > > native extensions" upon push. > > > I deployed herehttp://freezing-sunset-88.heroku.com/- a temp app to > > illustrate the issue. > > > Orlin > > > -- > > 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.
