script/server -e environment_name

and NOT:

script/server RAILS_ENV=environment_name

If it’s dropping back to development, it could be that it’s not properly picking up the RAILS_ENV.

So I have this in

## config/workling.yml:
production:
listens_on: localhost:15151

development:
listens_on: localhost:22322

test:
listens_on: localhost:12345

development_remote:
listens_on: #my_remote_ip_here#:22522

cucumber:
listens_on: localhost:12345

## end of config/workling.yml

I get the starling and workling set up on my staging server at #remote_ip#, and I get this outcome:

# this succeeds:
script/console development_remote
>> r = MyWorkerClass.asynch_count_to_a_hundred_million
=> “”my_worker_classes:count_to_a_hundred_million:7edb0e25b721ea725441b79d8ebb4d58″

# and it goes to the queue, and I see the processor spike as ruby counts to 100,000,000 on my staging server

… all good so far, but then

## this fails:
script/server RAILS_ENV=development_remote
# when I browse to a controller function which somewhere has
# MyWorkerClass.asynch_count_to_a_hundred_million
# I get the following error:
“config/workling.yml configured to connect to queue server on localhost:22322 for this environment. could not connect to queue server on this host:port. for starling users: pass starling the port with -p flag when starting it. If you don’t want to use Starling, then explicitly set Workling::Remote.dispatcher (see README for an example)”

So it looks like it’s not loading the proper set of details from workling.yml. How can I fix this?

Thanks
– Luke

See this:
http://groups.google.com/group/starlingmq/browse_thread/thread/beedc7a6d7c84bd1/feda55233fa355ff?lnk=gst&q=windows#feda55233fa355ff

Seth knows his stuff.

I am working on getting starling/workling combo setup for my app when I ran into a this problem. I am using a Windows machine for development and linux machines host my deployments. When I start starling and set a queue to something on the dev machine, starling gives me an error because the path it creates automatically for my queue( /var/spool/starling/.. ) has a ‘/’ instead of a ‘\’. I tried setting the path explicitly when starting starling using:

starling -d -q C:\..\..

But still its doing the same thing. Anything I can do to get this to do the right thing??

Thanks in advance.

BTW, these files are how the memory queue is rebuilt when you restart starling.

I am trying to delete the starling queues:

./script/console

>> starling.available_queues
=> ["vimeo_background_upload_workers__upload_to_vimeo", "queue_paperclip_background_upload_workers_upload_to_amazon_s3", "queue_paperclip_background_upload_workers__upload_to_amazon_s3", "paperclip_background_upload_workers__upload_to_amazon_s3"]

>>starling.delete(‘queue_paperclip_background_upload_workers_upload_to_amazon_s3′)
MemCache::MemCacheError: bad command line format

Is there another way to delete the queue item? I have a pretty nasty back log that is starting to eat up my memory. If I kill the PID and restart the worker it seems to cache the queue and restarts everything.

Any help would be greatly appreciated!

Best,

Jackson

PhotoWorker.asynch_send_hour_warning

That should add the correct message to your queue. The downside, however, of this approach is that you will need to load your rails environment.

I usually add an:

export RAILS=production

for the bash profile of the user I run cron and/or rails processes for. This way I know the environment will be set correctly when I execute cron or rake tasks.