In the starling_status script that Workling installs when added to a
Rails application, it fails with a MemCacheError about a "command line
format"
here's the trace :
/Library/Ruby/Gems/1.8/gems/memcache-client-1.7.2/lib/memcache.rb:
882:in `raise_on_error_response!': bad command line format
(MemCache::MemCacheError)
from /Library/Ruby/Gems/1.8/gems/memcache-client-1.7.2/lib/
memcache.rb:527:in `flush_all'
from /Library/Ruby/Gems/1.8/gems/memcache-client-1.7.2/lib/
memcache.rb:821:in `call'
from /Library/Ruby/Gems/1.8/gems/memcache-client-1.7.2/lib/
memcache.rb:821:in `with_socket_management'
from /Library/Ruby/Gems/1.8/gems/memcache-client-1.7.2/lib/
memcache.rb:522:in `flush_all'
from /Library/Ruby/Gems/1.8/gems/memcache-client-1.7.2/lib/
memcache.rb:521:in `each'
from /Library/Ruby/Gems/1.8/gems/memcache-client-1.7.2/lib/
memcache.rb:521:in `flush_all'
from /Library/Rails/sokoban/releases/20090527191025/vendor/plugins/
workling/lib/workling/clients/memcache_queue_client.rb:44:in `close'
from script/starling_status.rb:48
and the offending line is the "client.close" bit in this ensure
block :
ensure
puts '** Exiting'
client.close
end
referencing :
client = Workling::Clients::MemcacheQueueClient.new
By simply commenting out the close line, the error goes away, but as
part of troubleshooting other problems with workling, I'm trying to
track down everything that looks the least bit squirrely
It gives the same error with the fiveruns-memcache-client as well, on
my local machine, as well as on the server
Any ideas?
