Attention!
It has come to my attention that this plugin is no longer available from it’s original source. I have made it available on Github.
In place of steps 2 and 3 below you can download the tarball and unpack it to your vendor/plugins directory.
Let me know in the comments how this goes, thanks.
Back to the action
Sometimes you need some precess to run at set time intervals, independent of the request-response cycle a standard web server. Things like (as I did) polling Flickr to see if you’ve added any new images to your account, or looking at a to-do list to see if any email reminders are due to be sent out.
Cron jobs under Unix are a great answer to this , but you have the problem of these being:
- Particular to Unix and Linux systems.
- How do you access your active-record models that make up your Rails app?
Enter Kyle Maxwell’s Daemon_generator plugin, a simple way to create and control daemons that run your own code within the Rails Environment.
It took me a while to figure out how to get it all set up, so I decided to write a guide to help people get to grips with it.
OK, here we go…
- Install the Daemons Gem on your system using the command:
sudo gem install daemons
- Navigate to the root of your rails app, install the daemons_generator plugin in your app using the command:
ruby script/plugin install http://svn.kylemaxwell.com/rails_plugins/daemon_generator/trunk
- Unfortunately this will be installed in your
vendor/plugins folder as trunk, so change the name of this to daemon_generator so it’s easy to see at a glance what it is:mv vendor/plugins/trunk vendor/plugins/daemon_generator
- Now you can create your first daemon. I’m going to call mine
test:ruby script/generate daemon test
That should create a bunch of files, including lib/daemons/test.rb, which will hold your actual code. If you have a look at this, it should be fairly self-explanatory where you put your own code and how you set the time interval. Leave this unchanged for the moment, just to see it in action.
- Start the daemons with the command:
ruby script/daemons start
- Look at the production log, you should see output similar to the following:
dougal@tempy:~/test123$ tail -f log/production.log
This daemon is still running at Thu Nov 09 00:33:54 GMT 2006.
This daemon is still running at Thu Nov 09 00:34:04 GMT 2006.
This daemon is still running at Thu Nov 09 00:34:14 GMT 2006.
It might seem strange to be looking at the production log, daemons run in production environment by default as they can be run separately from your web server (The we server doesn’t even have to be running to get this to work). You can of course change the environment at the top of lib/daemons/test.rb should you wish so for testing purposes.
- Stop your daemon with the command:
ruby script/daemons stop
Having Trouble?
This plugin is no longer maintained by the original author. However, commenters have been kind enough to suggest fixes to problems. See Rob Lucas’s comment in particular. I will of course accept patches and fixes, and apply these to the repository.
Wrapup
That’s it, you created, run and halted your first daemon! More commands for controlling daemons can be found in the readme, and the complete source in Kyle’s SVN repository.
Hope that helped some people out. If you have any questions or problems leave a comment and I’ll hopefully see you good.
Tags
Ruby on rails, Daemon, Daemon_generator.
Related Posts
November 8th 2006 23:42 |
comments (18)
December 13th 2006 21:01
Is there an explanation of the options in daemons.yml anywhere?
December 21st 2006 22:02
There is no documentation for the code in the generator itself at all, but I'll take a look as to what it does and get back to you on that one.
January 4th 2007 16:25
Cheers Brent, that'll tech me to look in the Rdoc first!
April 2nd 2007 23:37
Please Help.
I did just what you instructed.. but when I run the script I get this...
ruby script/daemons start
script/daemons:2:in ``': No such file or directory - script/../lib/daemons/test_ctl start (Errno::ENOENT)
from script/daemons:2
from script/daemons:2:in `each'
from script/daemons:2
Any Idea why I get this error?
April 2nd 2007 23:48
Hi John. If you drop me an email at dougal DOT s AT gmail DOT com I'll email you back there.
Any other details you can provide (even a full paste of your terminal from when you started) will help me track the problem down. Should be able to get you sorted out.
April 5th 2007 18:46
Hi,
I get the same error as John above did ... how can i fix it .. i run mongrell on my machine.
Any help is appreciated.
Thank you
April 6th 2007 01:06
OK, I looked into it. In the daemons script, it looks for every *_ctl file, and passes on the command line argument for it.
For some reason, when you are running 'ruby script/generate daemon test' the test_ctl file is not being created, either that or you are not using this generator.
I just tested by downloading the latest version of the gem, and the latest plugin into a new rails app. I followed the instructions above, and everything ran fine.
Let me know if this helps in some way.
May 31st 2007 16:41
I am still getting the same error as John and Lucian above. I have the latest versions as of today. It looks like the test_ctl file is being created. Any help would be appreciated.
June 5th 2007 05:45
About the error above, try editing the config/daemons file and change:
"/../lib/daemons/*_ctl"
to: "../lib/daemons/*_ctl"
That worked for me... unfortunately dameon_generator does not work on Windows environments apparently.
June 5th 2007 12:49
Sorry I've not replied to queries in a while.
Krunkster - It looks like you may have hit the nail on the head! The preceding slash (/) would definitely cause things to be created in the wrong place on certain platforms.
As for running this on Windows, I would think it is a *nix only situation.
I'll blog about this later in the week, but recently I've been running cron jobs as a standard unix cron task, called script/runner. Much easier to administer, though only really useful if you have root access to the machine in question.
August 29th 2007 18:27
I am trying to run this under InstantRails on Windows and it looks like I am out of luck!
Anyone have another suggestion? I am still prototyping and will move a "real" environment but was hoping to make some headway on my persistent process to look for users that have not checked in lately.
Ideas and thoughts appreciated!
Andrew
October 9th 2007 21:05
How do I tap into the "scheduling" aspect that CRON is known for?
In other words, if I want a action to fire at 5:00am daily--- and another action to fire every other friday, how would I do that?
I want to stay away from OS specific things (like CRON) -- otherwise I would use that & script/runner.
Any ideas?
Thanks!
Shannon
December 12th 2007 20:38
Hi!
Anybody tried sending email from the deamon?
I try to send an html mail using the Actionmailer with the following code:
email = SiteNewsNotifier.create_new_messages( new_messages, email_addresses )
email.set_content_type("text/html")
SiteNewsNotifier.deliver(email)
In my production log it says the mail was sent and also the full html and mail details are shown, but the mail is not delivered and any following code in the deamon is not executed. The above code works fine when called from within a controller action.
Any idea what could be the problem?
Nico
April 30th 2008 14:27
Hi, thanks for all your help so far. I'm having a problem with part 6. My production log remains unchanged while the test daemon is running, and in the log for test.rb.log it's giving me a bunch of errors. What gives?
I'm getting...
<MissingSourceFile: no such file to load -- fast_xs>
<NoMemoryError: failed to allocate memory>
<SystemStackError: stack level too deep>
<fatal: exception reentered>
<LoadError: no such file to load -- active_support>
<Gem::Exception: can't activate activesupport (= 1.4.4), already activated activesupport-2.0.2]>
<NameError: uninitialized constant Rails>
<MissingSourceFile: no such file to load -- utf8proc_native>
<MissingSourceFile: no such file to load -- fast_xs>
...any idea where I could start trouble shooting?
I found fast_xs on Ruby-forge. Installed that (I think) and still no luck.
Help!
May 1st 2008 17:14
Hi,
I'm having problems with the same line discussed above:
Dir[File.dirname(__FILE__) + "/../lib/daemons/*_ctl"].each {|f| `#{f} #{ARGV.first}`}
However, this line appears to be correct on my system. E.g this will actually return the path "script/../lib/daemons/test_ctl":
Dir[File.dirname(__FILE__) + "/../lib/daemons/*_ctl"].each do |ctl|
puts ctl
end
If I change it as suggested above (to "../lib/"), it returns nothing at all.
The problem is that, even though it is clearly returning the correct file, I get ": No such file or directory" when running "ruby script/daemons start", which is evidently totally bizarre.
This, however, works:
ruby lib/daemons/test_ctl start
Is there some peculiarity with the Dir class perhaps? Anyone else seen similar behaviour?
Cheers,
Rob.
July 24th 2008 15:12
@rob and @david, I had the same problem and it was solved by:
gem update
...
Updating daemons
Successfully installed daemons-1.0.10
...
(I previously had daemons-1.0.9)
August 7th 2008 08:12
Production log is not updating :(
Having same problem as david said earlier. i've tried to update gem, but its already the latest version. Please help.
Add Your Comments
