Hi Keith, Sorry to have let this dangle for a few days and I appreciate your help with this. We wound up solving the starling/workling problem so we're no longer implementing beanstalk. However, I do have another tidbit that might be helpful for someone else with this problem. I hadn't tailed my development.log during this, but when I went in there, I saw workout output being logged. So the worker was (at least part of the time) not using the version_2 environment.
Thanks again for your time and advice. -Jason On Jan 10, 2:42 pm, "Keith Rarick" <[email protected]> wrote: > On Thu, Jan 8, 2009 at 10:09 AM, Jason F <[email protected]> wrote: > > $ RAILS_ENV=version_2 ./vendor/plugins/async_observer/bin/worker > > #!load-rails!begin!2009-01-08T17:23:38.802707Z > > RAILS_ROOT="/home/jfrankovitz/git/rails_app > > #!load-rails!end!2009-01-08T17:23:42.787549Z > > Is this all the output you see from the worker? Can you post a copy of > the rails log for one worker instance? There should be lines > containing "worker-startup" and "worker-get-job". > > > (I know they're communicating because when I ctrl-c beanstalkd the > > worker says "Errno::ECONNREFUSED: Connection refused - connect(2)") > > Can you first verfiy that beanstalkd itself is working reasonably? You > should be able to reproduce this transcript with no perceptible delays > between each command and its response: > > $ ./beanstalkd -d > $ telnet localhost 11300 > put 0 0 100 5 > hello > INSERTED 1 > reserve > RESERVED 1 5 > hello > delete 1 > DELETED > ^] > telnet> close > Connection closed. > $ killall beanstalkd > > kr --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
