Unexpected flag: 222 Error

Every time I try to Acrosync a specific profile (directory tree) I get the following error:

Unexpected flag: 222 (222:1:1:1:0:64000:0:2048000:369:1047501:0:1)

Acrosync will rsync files in the directory up until a certain point, then I'm assuming that it hits a certain file, and then encounters this error. I have verbose logging turned on, but the log doesn't show the current file that it is rsync'ing, just the last successful one, so that is of little help in determining which file Acrosync has an issue with. What can I do to get past this issue?

Thanks in advance for your help.
Stach

Comments

  • Files under the same directory are sorted by name, so it should not be too hard to find out which file it is from the last successful one.  Files in subdirectories are transmitted first (depth-first fashion), so if the last successful one is the last file in its directory then you'll need to figure out which would be the next directory.


    If you can find out this file and if it doesn't contain sensitive info, could you please send it to me for analysis?
  • Unfortunately, I was hoping that new version would somehow fix the issue so the issue has been around for 1 month or more and after applying the latest version, I still have the issue. Most of the 25,000+ file have sync'd fine in the past, but I add 10-20 at a time, so i don't know exactly which file ti's failing on. The last files that I just moved over there rsync'd fine and then it dies at some point after that

    Is there any way to compare the source and destination directories to tell which files aren't in sync and would be sync'd next?

    Is there a debug version that has a more detailed log that tells what file it is working on next?

    Thanks in advance for your help.
    David
  • I uploaded a new version that shows a debug level log message before syncing each file:

  • GChen, thanks for the special debug build, as I have found the file. Unfortunately it's 224 MB in size, so what do you want me to do with it? Can you send me an email with a Dropbox share that I could put it on, or any other solution?

    Thanks in advance.
  • Just sent a Dropbox share to your yahoo email.
  • Gang, sorry for the delay (we were away for the weekend), but the file has been uploaded to your Dropbox share.

    Thanks for your help.
    David
  • I couldn't replicate the error with that file.  All download/upload were successful.

    Can you try moving this file to a different subdirectory to see if you're still getting the same error?

    And what is the version of sshd and rsync on your server?

  • Gang, I am rsyncing to a WD MyCloud NAS that is running the following versions of software:

    OpenSSH_6.0p1 Debian-3, OpenSSL 1.0.1g 7 Apr 2014

    rsync  version 3.0.9  protocol version 30

    Let me know if you see any potential issues with the versions that I am running. Also, if anyone knows the command(s) to update rsync, I'd be willing to give that a try as well.

    Thanks in advance for your help.
  • Both are recent versions so I don't think there is a need to update.

    How long did the sync run before this error popped up?  And what was the average upload speed?  I'm thinking if it makes sense to dump every bytes received from the ssh layer.

    And just to make sure, the unexpected flag was always 222 every time you ran the profile?
  • And of course with me changing nothing, other than using version 1.3 again, it ran to completion without any errors. I really like the increased logging, maybe you could make that a regular selectable feature (i.e. simple, verbose, verbose attempts, insanely everything).

    Thanks for your help, it is much appreciated!
  • Around 2 MB/s appears to be the max speed that I can transfer with Acrosync on my old Windows 7 x64 machine as no matter if I connect to a local ethernet attached NAS or to another of my NAS's acrossed the internet, that is the speed that I get.

    Would the average upload speed have the potential to cause any issues?
  • How much faster if you connect through rsync directly?  The ssh layer may incur some overhead.
  • It's the same speed.
  • The speed is really dependent on the file size.  I usually can get 5MB/s on files that are at least a few MBs, but with small files that may drop to 500KB/s.  
  • I finally figured out what caused this unexpected flag error.  The libssh2 library has a bug in the calculation of the data window size which causes some packets to be dropped, thus corrupting the rsync data stream.  The same bug also prevents the remote server from sending more data packets, resulting the error that says "The rsync channel has been blocked for more than 120 seconds".

    New version 1.3 binaries with the fix can be downloaded from the same links:


Sign In or Register to comment.