Backgroundrb devel - Jan 2007 - failed to find slave socket

I''m having a strange issue. The following error is printed to the  
backgroundrb_server.log file:

failed to find slave socket </tmp/backgroundrb.803/ 
verification_email_delivery_worker_fafbd1e29be8b802aef4a4ffc1a35754_0_0. 
126366358217085> - (RuntimeError)
20070124-17:41:29 (805) /usr/local/lib/ruby/gems/1.8/gems/slave-1.2.0/ 
lib/slave.rb:462:in `initialize''
20070124-17:41:29 (805) /Users/erik/Documents/projects/productblazer/ 
trunk/vendor/plugins/backgroundrb/server/lib/backgroundrb/ 
middleman.rb:210:in `new_worker''

What''s strange is that no exception reaches the console:
 >> MiddleMan.new_worker(:class => :verification_email_delivery_worker)
=> "fafbd1e29be8b802aef4a4ffc1a35754"

Any thoughts? it''s a fairly straight forward error message, but I  
can''t understand why this worker would have an issue with its socket  
file when several others do not have this problem.

I think the socket filename was too long. I shortened the name of the  
worker to verification_email_worker and it loads correctly on OSX  
now. I haven''t tested linux yet.

Erik
On Jan 24, 2007, at 5:46 PM, Erik Morton wrote:
> I''m having a strange issue. The following error is printed to the
> backgroundrb_server.log file:
>
> failed to find slave socket </tmp/backgroundrb.803/ 
> verification_email_delivery_worker_fafbd1e29be8b802aef4a4ffc1a35754_0_ 
> 0.126366358217085> - (RuntimeError)
> 20070124-17:41:29 (805) /usr/local/lib/ruby/gems/1.8/gems/ 
> slave-1.2.0/lib/slave.rb:462:in `initialize''
> 20070124-17:41:29 (805) /Users/erik/Documents/projects/ 
> productblazer/trunk/vendor/plugins/backgroundrb/server/lib/ 
> backgroundrb/middleman.rb:210:in `new_worker''
>
> What''s strange is that no exception reaches the console:
> >> MiddleMan.new_worker(:class =>
:verification_email_delivery_worker)
> => "fafbd1e29be8b802aef4a4ffc1a35754"
>
> Any thoughts? it''s a fairly straight forward error message, but I
> can''t understand why this worker would have an issue with its  
> socket file when several others do not have this problem.