›

'Socket was closed unexpectedly' error

Delte7
edited March 2015 in Acrosync for Windows
I'm getting a 'Socket was closed unexpectedly' error when running a sync. The other sync's (profiles) are running just fine. Any ideas what might be causing the issue?

I have tried with/without volume shadow and with/without excluded files. I have also rebooted server a couple times.

I'm running the latest version for windows -1.3.

Comments

  • gchen
    Can you enable verbose logging and see if there is any extra info?

    And did this happen with version 1.2 too?  Older versions are still available for download -- just change the version number in the download link to '1.2'.
  • Delte7
    Verbose logging did not identify anything other than the normal logging when a sync is run and then 'Socket was closed unexpectedly'

    I uninstalled 1.3 and installed 1.2. 1.2 ran with NO errors.


  • gchen
    Are you connecting via rsync directly (with the 'via ssh' option unchecked)?
  • Delte7
    yes, not using SSH.
  • gchen
    which version of rsync are you running on the server?  You can find out by running this command on the server: rsync --version
  • Delte7
    rsync version 3.0.9 protocol version 30
  • PnYMaT
    Same error here :

    rsync  version 3.0.9  protocol version 30
    Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux
    Debian GNU/Linux 7.8

    I use Acrosync v1.3.462


  • gchen
    Did that happen in download or upload mode?
  • PnYMaT
    Both for me.
  • gchen
    Finally replicated the error with my test.  Due to a bug in the ssh layer fix, Acrosync may attempt to read 0 bytes from underlying network layer.  While the ssh layer has no problem handling this case, the socket layer is tricked into falsely believing that the socket has been closed when this happens.

    I've uploaded new version 1.3 binaries.  If you're on version 1.3 you'll need to re-install Acrosync using the new installer from the download page.

  • PnYMaT
    Hi,

    Yeah ! Works fine now :)

    Many thanks.
Sign In or Register to comment.