This is my first time working with beanstalk (I ditched a frustrating
experience with Starling/Workling to get here) so there may be an
obvious answer to this. The only thing slighty unusual about my config
is that I'm running this all in a custom rails environment called
"version_2", not one of the usual dev/test/prod environments.
I've got beanstalkd 1.1 running:
[jfrankov...@irvsrddev6 beanstalkd-1.1]$ ./beanstalkd
./beanstalkd: net.c:90 in unbrake: releasing the brakes
Then I run one worker:
[jfrankov...@irvsrddev6 rails_app]$ ./vendor/plugins/async_observer/
bin/worker
#!load-rails!begin!2009-01-08T01:51:56.127115Z
RAILS_ROOT="/home/jfrankovitz/git/rails_app"
#!load-rails!end!2009-01-08T01:52:00.683801Z
I use a rake task to feed a simple rails/ActiveRecord call into
beanstalk:
task :feed => :environment do
beanstalk = Beanstalk::Pool.new(['localhost:11300'])
beanstalk.put("Model.create( :name => 'foo' )")
end
When I run 'RAILS_ENV=version_2 rake beanstalk:feed', I check
Model.count and it hasn't increased. But I know the job is getting
into beanstalk OK because I have another rake task that finds it/runs
it:
task :do_job => :environment do
beanstalk = Beanstalk::Pool.new(['localhost:11300'])
loop do
job = beanstalk.reserve
x = eval job.body
job.delete
end
end
After I run "RAILS_ENV=version_2 rake beanstalk:do_job", about 45
seconds later, Model.count has increased by one.
Why isn't the worker working? Most of my setup is pretty vanilla and
the config seems fairly straightforward... I hope I can get this
working because I do *not* want to mess with Workling again :)
Thanks for any/all advice,
-Jason
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"beanstalk-talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
