Thank you. That did the trick!!! On May 22, 10:26 am, David <datab...@gmail.com> wrote: > Interesting. Well, it looks like the jump to RC1 with an updated > Sprockets has fixed it: > > - sprockets (~> 2.0.0.beta.2) > + sprockets (~> 2.0.0.beta.5) > > Living on the edge! > > On May 20, 11:56 am, Chris Hanks <christopher.m.ha...@gmail.com> > wrote: > > > > > > > > > I get this same error frequently on my development machine (Ruby > > 1.9.2p180 on Ubuntu Natty), so it's not Heroku-specific. > > > On May 20, 8:01 am, David <datab...@gmail.com> wrote: > > > > Klaus Harti posted this message originally on May 11th and I have it > > > in my digest list - I just can't seem to find it on Google Groups. > > > > Anyhow, I'm seeing a similar problem but with this on serving the > > > resulting CSS: > > > !! Unexpected error while processing request: deadlock; recursive > > > locking > > > > Log: > > > > 2011-05-20T08:31:13+00:00 heroku[web.1]: Starting process with > > > command: `thin -p 49201 -e production -R /home/heroku_rack/heroku.ru > > > start` > > > 2011-05-20T08:31:17+00:00 app[web.1]: Starting the New Relic Agent. > > > 2011-05-20T08:31:17+00:00 app[web.1]: Installed New Relic Browser > > > Monitoring middleware > > > 2011-05-20T08:31:19+00:00 app[web.1]: >> Thin web server (v1.2.6 > > > codename Crazy Delicious) > > > 2011-05-20T08:31:19+00:00 app[web.1]: >> Maximum connections set to > > > 1024 > > > 2011-05-20T08:31:19+00:00 app[web.1]: >> Listening on 0.0.0.0:49201, > > > CTRL+C to stop > > > 2011-05-20T01:31:20-07:00 heroku[web.1]: State changed from starting > > > to up > > > 2011-05-20T08:31:27+00:00 app[web.1]: > > > 2011-05-20T08:31:27+00:00 app[web.1]: > > > 2011-05-20T08:31:27+00:00 app[web.1]: Started GET "/" for > > > 72.229.127.215 at 2011-05-20 01:31:27 -0700 > > > 2011-05-20T08:31:27+00:00 app[web.1]: Processing by > > > HomeController#index as HTML > > > 2011-05-20T08:31:27+00:00 app[web.1]: Rendered home/index.html.erb > > > within layouts/application (15.7ms) > > > 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] application.css > > > building > > > 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] style.css building > > > 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] application.js > > > building > > > 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] jquery.js building > > > 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] jquery_ujs.js > > > building > > > 2011-05-20T08:31:28+00:00 app[web.1]: Rendered shared/ > > > _tracking_footer.html.erb (0.4ms) > > > 2011-05-20T08:31:28+00:00 app[web.1]: Completed 200 OK in 1417ms > > > (Views: 1417.0ms | ActiveRecord: 0.0ms) > > > 2011-05-20T08:31:28+00:00 heroku[router]: GET mysite.heroku.com/ > > > dyno=web.1 queue=0 wait=0ms service=1469ms bytes=1834 > > > 2011-05-20T08:31:28+00:00 app[web.1]: cache: [GET /] miss > > > 2011-05-20T08:31:28+00:00 app[web.1]: Connected to NewRelic Service at > > > collector-1.newrelic.com:80 > > > 2011-05-20T08:31:29+00:00 app[web.1]: !! Unexpected error while > > > processing request: deadlock; recursive locking > > > 2011-05-20T08:31:29+00:00 heroku[router]: Error H13 (Connection closed > > > without response) -> GET mysite.heroku.com/assets/application- > > > b1637fec79c8bbd5d3a18e84f3da878f.css dyno=web.1 queue=0 wait=0ms > > > service=0ms bytes=0 > > > 2011-05-20T01:31:29-07:00 heroku[nginx]: GET / HTTP/1.1 | > > > 72.229.127.215 | 1480 | http | 200 > > > > both edge and beta1 have the same results: > > > > Gemfile: > > > > source 'http://rubygems.org' > > > > #gem 'rails', '3.1.0.beta1' > > > gem 'rails', git: 'git://github.com/rails/rails.git' > > > > gem 'pg' > > > gem 'therubyracer-heroku', '0.8.1.pre3' > > > > # Asset template engines > > > gem 'sass' > > > gem 'coffee-script' > > > gem 'uglifier' > > > > gem 'jquery-rails' > > > > Previous post: > > > > Rails 3.1 asset pipeline causing 503? > > > > Klaus Hartl <klaus.ha...@googlemail.com> May 11 06:06AM -0700 ^ > > > > Hello there, > > > > I was curious and tried if I can use the new assets pipeline that > > > comes with Rails 3.1 beta (sprockets). From time to time I am > > > getting > > > a 503 for requests of those merged application.js/.css files, an > > > example from my log: > > > > 2011-05-11T12:26:10+00:00 app[web.1]: cache: [GET /assets/ > > > application-140d82c5f1fa592792bc01518bd2906e.js] fresh > > > 2011-05-11T12:26:10+00:00 heroku[router]: GET tweektv.heroku.com/ > > > assets/application-140d82c5f1fa592792bc01518bd2906e.js dyno=web.1 > > > queue=0 wait=0ms service=2ms bytes=8700 > > > 2011-05-11T05:26:10-07:00 heroku[nginx]: GET /assets/ > > > application-140d82c5f1fa592792bc01518bd2906e.js HTTP/1.1 | > > > 84.191.168.124 | 1325 | http | 503 > > > > I am fully aware that this is beta and I did not necessarily > > > expect it > > > to work just so. I'm wondering if this is something related to the > > > app > > > or if this is on Heroku's side anyway (in other words, should I > > > just > > > wait for Rails 3.1 out of beta or not)... The log message isn't > > > very > > > helpful to me, as is what I get in the response of such 503 > > > request > > > (stripped html): > > > > "Application Error > > > An error occurred in the application and your page could not be > > > served. Please try again in a few moments. > > > If you are the application owner, check your logs for details." > > > > Last not least I have installed the Exceptional Premium add-on and > > > I'm > > > not getting any error notifications in there. > > > > Any insight is very much appreciated... > > > > --Klaus
-- 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.
