Re: Repeated::Job cannot find Delayed::Job
I solved this. Apparently there is an issue with delayed_job loading. See here: http://groups.google.com/group/delayed_job/browse_thread/thread/19dc6207a455029d/e776959275325763?lnk=gstq=uninitialized+constant#e776959275325763 Note that putting the recommended 'Delayed::Worker.backend = :active_record'in initializers/ doesn't work in this case as they are run *after* the plug-ins are loaded. I just added it to the repeated_job plugin's init.rb before it creates the job and everything works now. Russell. On Aug 5, 6:09 pm, David Dollar da...@heroku.com wrote: Make sure the delayed_job plugin has been pushed to your app (that there is no .git subdirectory inside it masking the files) You can try to clone your app from heroku into /tmp to see a pristine state of what is in Heroku's repo. cd /tmp git clone g...@heroku.com:myapp.git On Aug 5, 2010, at 11:56 AM, Russell Quinn wrote: I'm trying to get these two things working together. Delayed::Job is installed, has the migrations and there's a background worker running, etc. However, Repeated::Job can't find it on start-up. I've tried explicitly setting the plugin load order in Rails (although they're alphabetically correct anyway,) but this doesn't help. Does anyone have any ideas? Here are my logs from straight after a slug launch. Both canary-1684341.log and dj-1891287.log complain about Repeated::Job (erroneously called Repeated::Cron in the error message from the plugin's init.rb) not finding Background::Job. Thanks, Russell. - == exceptional.log == # Logfile created on Thu Aug 05 08:50:01 -0700 2010 by logger.rb [INFO] (init.rb:18) Thu Aug 05 15:50:01 UTC 2010 - Loading Exceptional for 2.3.8 == newrelic_agent.log == # Logfile created on Thu Aug 05 08:50:02 -0700 2010 by logger.rb [08/05/10 08:50:02 -0700 railgun64.30863 (8200)] INFO : Dispatcher: thin [08/05/10 08:50:02 -0700 railgun64.30863 (8200)] INFO : Application: X-XX [08/05/10 08:50:02 -0700 railgun64.30863 (8200)] INFO : New Relic RPM Agent 2.12.3 Initialized: pid = 8200 [08/05/10 08:50:02 -0700 railgun64.30863 (8200)] INFO : Agent Log found in /disk1/home/slugs/232258_d8f7c76_6525/mnt/log/ newrelic_agent.log == production.log == # Logfile created on Thu Aug 05 08:50:01 -0700 2010 == canary-1684341.log == Exception encountered, Repeated::Cron not loaded uninitialized constant Delayed::Job ** [NewRelic] New Relic RPM Agent 2.12.3 Initialized: pid = 8200 ** [NewRelic] Agent Log found in /disk1/home/slugs/232258_d8f7c76_6525/ mnt/log/newrelic_agent.log Thin web server (v1.2.6 codename Crazy Delicious) Maximum connections set to 1024 Listening on 0.0.0.0:3693, CTRL+C to stop == production.log == # Logfile created on Thu Aug 05 08:50:11 -0700 2010 == dj-1891287.log == (in /disk1/home/slugs/232258_d8f7c76_6525/mnt) Exception encountered, Repeated::Cron not loaded uninitialized constant Delayed::Job -- 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: db:pull from one heroku app to another without downloading
On Aug 4, 2010, at 3:19 AM, gduq wrote: Is it possible to use heroku db:pull to clone the data from one (heroku) app directly to another without downloading it to the local machine and using db:push to send it back? e.g. if we have 'production' and 'staging' apps and want to copy the data over from production. Hi, gduq -- It's a mess at the moment, but I've just written a [rake task][1] to do this very thing. The basic approach is to run (the equivalent of) `heroku db:pull` on Heroku itself; from the command-line it looks like: heroku rake db:pull --remote staging (Do consider it a starting point for a conversation, though: like I say, it's a mess!) Cheers, -- Matthew [1]: http://gist.github.com/511224 -- 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: Custom Error Pages
I'd also like to see ways of customising the backlog too deep, and timeout pages too - it's not great for a user to see pages from a seemingly random place when things aren't behaving as they should. N 2010/8/6 Tomaž Žlender tomaz.zlen...@gmail.com +1 for this feature. On Jul 27, 6:20 am, daniel hoey danielho...@gmail.com wrote: Is there anyway to use our own error pages instead of the Heroku ones? -- 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. -- Neil Middleton -- 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: workers dying overnight
Update: I upgraded my stack to Ruby 1.9.1 and the crashes seem to have stopped. (Knock wood!) heroku stack:migrate bamboo-mri-1.9.1 On Jul 30, 10:28 am, Alex Chaffee ale...@gmail.com wrote: What a useful command! Thanks. Still, I don't know what I could be doing to cause DJ to crash. Doesn't it catch all exceptions raised by jobs? My jobs are just doing plain vanilla Ruby stuff... - A On Jul 29, 8:22 am, Dan Croak dcr...@thoughtbot.com wrote: Only time I've had issues with workers is when I messed up something on my side so that I was causing DJ to crash. I debugged it by doing: heroku ps On Thu, Jul 29, 2010 at 11:10 AM, Alex Chaffee a...@cohuman.com wrote: I wrote a simple Heroku app to do service monitoring. It uses DelayedJob to queue up repeating tasks like doing an HTTP ping of a server once a minute or once an hour. Twice now the worker has died overnight. heroku workers still says I'm running 1 worker, but there's no message in heroku logs -- not even the stub of logs from the DJ worker that was there before. It looks like the worker instance has been retired by the scheduler. If I run heroku workers 0; heroku workers 1 then it comes back and my jobs all start running. Aha! It just started up a worker on its own after I hit the web page for the first time today. I think the scheduler needs to be smarter about worker proceses... maybe it needs to check the database for any Delayed Jobs whose run_at is soon, and either not retire it or make sure a worker comes online in time to run it. The code is athttp://github.com/alexch/sentryifyou want to try it yourself. Has anyone else had this problem? -- Alex Chaffee - a...@cohuman.com -http://alexch.github.com Stalk me:http://friendfeed.com/alexch|http://twitter.com/alexch| http://alexch.tumblr.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 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.
Bundler 1.0.0 RC2 and Rails Beta 3
Hi, Deploying our app (Rails beta 3), we got the following error : /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc.2/lib/bundler/ definition.rb:167:in `initialize': Read-only file system - /disk1/home/ slugs/139138_9f5947d_0aeb/mnt/Gemfile.lock - Heroku has a read-only filesystem. See http://docs.heroku.com/constraints#read-only-filesystem (Errno::EROFS) This was working fine with previous bundler version. Any idea how to fix it ? (We won't upgrade Rails for now). Thanks -- 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: Rails3 RC from master failed to start
On 5 Ago, 22:47, morgoth w.wnetr...@gmail.com wrote: After pushing application to heroku I get error:http://gist.github.com/510350 Anybody having similar problem? Me too. But my last push yesterday was fine. -- 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.
Issue with new bundler and git dependencies
First of all, thanks for updating Bundler to 1.0.0.rc.2! I ran into an issue deploying my project using the new Bundler. I'd been using a git dependency in the Gemfile, and the post-receive hook seemed to check this out from github just fine, but when I tried to actually start the app, it claimed that the dependency wasn't checked out, specifically: /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0.rc.2/lib/bundler/ source.rb:552:in `load_spec_files': http://github.com/nbudin/castronaut.git (at master) is not checked out. Please run `bundle install` (Bundler::PathError) Anything to do about this? For now I'm attempting to work around it by packaging it up as a gem. Thanks, Nat -- 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: Custom Error Pages
+1 for this feature. If we could just upload static HTML pages for the different possible heroku errors, that would be great. It's unacceptable for a Heroku branded error to come up no matter what the error is. On Aug 6, 6:41 am, Tomaž Žlender tomaz.zlen...@gmail.com wrote: +1 for this feature. On Jul 27, 6:20 am, daniel hoey danielho...@gmail.com wrote: Is there anyway to use our own error pages instead of the Heroku ones? -- 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: Rails3 RC from master failed to start
Specifying gems with :path seems to work, so rather than pushing gems to a public place like rubygems.org you can pull them into your own app git repo temporarily and point to them with a relative path. for example: gem 'acts-as-taggable-on', :path = vendor/gemtmp/acts-as-taggable-on This is working for me, anyway. On Aug 5, 2010, at 5:06 PM, Chris Conley wrote: Yeah I agree. I should've mentioned that it was a temporary solution. Thanks! On Thu, Aug 5, 2010 at 5:59 PM, Nick Quaranto n...@quaran.to wrote: How about git://github.com/rails/rails.git ? Also, I've been trying to discourage gem forking unless if it's really, really necessary...you can point bundler to a git repo, why is pushing the gem necessary then? On Thu, Aug 5, 2010 at 5:56 PM, Chris Conley chris.m.con...@gmail.com wrote: I just got around this by forking the git gem and pushing to rubygems.org. Here's drnic's guide to doing just that: http://drnicwilliams.com/2009/11/04/hacking-someones-gem-with-github-and-gemcutter/ On Thu, Aug 5, 2010 at 5:33 PM, Chris Conley chris.m.con...@gmail.com wrote: Yeah, I'm getting the same error as well. On Thu, Aug 5, 2010 at 5:11 PM, lstoll l...@lds.li wrote: I'm having a similar problem - seems that any gem that is installed from a git source will fail like this. On Aug 5, 10:47 pm, morgoth w.wnetr...@gmail.com wrote: After pushing application to heroku I get error:http://gist.github.com/510350 Anybody having similar problem? -- 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. -- 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: Rails3 RC from master failed to start
Yes I'm also having this problem, with our own gem on github. Anyone have a solution to this? On Aug 5, 5:11 pm, lstoll l...@lds.li wrote: I'm having a similar problem - seems that any gem that is installed from a git source will fail like this. On Aug 5, 10:47 pm, morgoth w.wnetr...@gmail.com wrote: After pushing application to heroku I get error:http://gist.github.com/510350 Anybody having similar problem? -- 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.
private git repos in bundler
If I have a private library on Github that I want to include in my Heroku app via Bundler, I know I can pass the Git-SSH URL to Bundler. However, the deploy machine would have to have the correct SSH keys to clone from github. Is it possible to get my app's SSH pub key, and add it to my project on Github to allow private cloning from Heroku? Thanks! David -- 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: NOTICE: Updating Bundler this week
If I am using a .gems file, am I unaffected by this change? -- 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: Issue with new bundler and git dependencies
I have the same issue, if it makes you feel better. Packaging as a gem will fix the problem, but I've submitted a support ticket to get a better answer. Will keep you updated... On Aug 5, 4:22 pm, Nat Budin natbu...@gmail.com wrote: First of all, thanks for updating Bundler to 1.0.0.rc.2! I ran into an issue deploying my project using the new Bundler. I'd been using a git dependency in the Gemfile, and the post-receive hook seemed to check this out from github just fine, but when I tried to actually start the app, it claimed that the dependency wasn't checked out, specifically: /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0.rc.2/lib/bundler/ source.rb:552:in `load_spec_files':http://github.com/nbudin/castronaut.git (at master) is not checked out. Please run `bundle install` (Bundler::PathError) Anything to do about this? For now I'm attempting to work around it by packaging it up as a gem. Thanks, Nat -- 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: Issue with new bundler and git dependencies
Guess it's an official issue nowadays: http://docs.heroku.com/bundler100rc2-git On Aug 6, 2:34 pm, chris mcclellan...@gmail.com wrote: I have the same issue, if it makes you feel better. Packaging as a gem will fix the problem, but I've submitted a support ticket to get a better answer. Will keep you updated... On Aug 5, 4:22 pm, Nat Budin natbu...@gmail.com wrote: First of all, thanks for updating Bundler to 1.0.0.rc.2! I ran into an issue deploying my project using the new Bundler. I'd been using a git dependency in the Gemfile, and the post-receive hook seemed to check this out from github just fine, but when I tried to actually start the app, it claimed that the dependency wasn't checked out, specifically: /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.0.rc.2/lib/bundler/ source.rb:552:in `load_spec_files':http://github.com/nbudin/castronaut.git (at master) is not checked out. Please run `bundle install` (Bundler::PathError) Anything to do about this? For now I'm attempting to work around it by packaging it up as a gem. Thanks, Nat -- 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.
