S3Sync.net

Here's an an error that I saw for the first time early this morning. It occured on two of my boxes, one
of those boxes was running the latest version of s3sync (1.2.4) while my other box was running version
 1.2.3 but with the 'dodo' modification mentioned in this thread: http://s3sync.net/forum/index.php?topic=123.0

/usr/local/lib/ruby/1.8/net/http.rb:564:in `initialize': Invalid argument - connect(2) (Errno::EINVAL)
        from /usr/local/lib/ruby/1.8/net/http.rb:564:in `open'
        from /usr/local/lib/ruby/1.8/net/http.rb:564:in `connect'
        from /usr/local/lib/ruby/1.8/timeout.rb:48:in `timeout'
        from /usr/local/lib/ruby/1.8/timeout.rb:76:in `timeout'
        from /usr/local/lib/ruby/1.8/net/http.rb:564:in `connect'
        from /usr/local/lib/ruby/1.8/net/http.rb:557:in `do_start'
        from /usr/local/lib/ruby/1.8/net/http.rb:552:in `start'
        from ./S3_s3sync_mod.rb:55:in `make_http'
         ... 7 levels...
        from ./thread_generator.rb:76:in `initialize'
        from ./s3sync.rb:266:in `new'
        from ./s3sync.rb:266:in `main'
        from ./s3sync.rb:724

Wonder if it has to do with the proxy feature added... What ruby ver?  Maybe there were incompatible changes made.

I'm using ruby 1.8.6 (2007-09-24 patchlevel 111) on both boxes. Things are working
fine again at the moment, so I'm guessing it was a network glitch of sorts.

- Frank