[Backgroundrb-devel] Client disconected error - trying to upgrade to latest version of backgroundrb

Chetan Sarva csarva at operative.com
Wed Sep 24 12:03:54 EDT 2008


For the record, I see the same behaviour on linux. "Client  
disconnected" in debug, but workers execute successfully. I tried  
grepping for that string in bdrb and packet, but it's not there or I'm  
looking in the wrong place...

On Sep 23, 2008, at 7:11 PM, Grant Blakeman wrote:

> I take it back. Downgrading the packet version does seem to have  
> helped. It was still showing "Client disconected" in the debug log,  
> but in my development log I can see it's now executing the code in  
> the worker file. Yay.
>
> Thanks for the help!
>
> -gb
>
> On Tue, Sep 23, 2008 at 4:51 PM, Grant Blakeman <grant.blakeman at gmail.com 
> > wrote:
> Hi Kieran,
>
> I'm on a Mac. I was running packet 0.1.12, so I tried downgrading to  
> MailScanner warning: numerical links are often malicious: 0.1.7. But  
> I'm still getting the same behavior: an immediate "Client  
> disconected" in the log whenever I try to call a new worker or ask  
> an existing one to do something.
>
> Could there be more info somewhere other than the debug log that I  
> might be able to check and see what's going on?
>
> -gb
>
>
> On Mon, Sep 22, 2008 at 8:30 PM, Kieran P <kieran776 at gmail.com> wrote:
> Hello Grant,
>
> Out of curiosity, are you using a Mac or Linux?
>
> If Mac, try downgrading the packet gem to MailScanner warning:  
> numerical links are often malicious: 0.1.7. Later versions include a  
> raise line that I found causes similar problems for me.
>
> And if Linux, try upgrading to the latest. I believe 0.1.13 contains  
> fixes related to packet on linux.....
>
> Regards
> Kieran
>
>
>
> On Tue, Sep 23, 2008 at 1:09 PM, Grant Blakeman <grant.blakeman at gmail.com 
> > wrote:
> Hi, I've tried it both ways (:arg & :args) and still get the same  
> 'Client disconected' in the debug log. I also tried simplifying the  
> call to see if any of the arguments were the problem:
>
> MiddleMan.worker(:danny_worker).async_do_work(:arg => "grant.blakeman at gmail.com 
> ")
>
> and I still get the error. It seems like the disconnect happens  
> before it even reads anything in the worker file. I tried calling an  
> argument that wasn't in the worker:
>
> MiddleMan.worker(:danny_worker).async_should_not_work(:arg => "grant.blakeman at gmail.com 
> ")
>
> and simply got the 'Client disconected' error.
>
> Any ideas?
>
> -gb
>
>
>
> -- 
> -Grant Blakeman
> grant.blakeman at gmail.com
> http://grantblakeman.com
>
>
>
> -- 
> -Grant Blakeman
> grant.blakeman at gmail.com
> http://grantblakeman.com
> _______________________________________________
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080924/f639a7a0/attachment.html>


More information about the Backgroundrb-devel mailing list