kamborio

Members
  • Posts

    41
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by kamborio

  1. 7 minutes ago, RomanZ said:

    @kamborio Your issue looks very similar to one we are hunting down now :). Unfortunately, no success in reproduction in lab. I wonder if you are okay to supply me with logs? Only affected computer would be enough.

    In this particular instance I could. Although I cannot see much and the ones I have are for version 2.3.5

    This is an edited log of the most important events I can see:

    [2016-04-02 22:30:24] MC[0D34] [9E60]: sending get_nodes message
    [2016-04-02 22:36:46] Change network from WIRED_NETWORK to NO_NETWORK
    [2016-04-02 22:36:46] SF[F90E]: Stop folder synchronization
    [2016-04-02 22:36:46] SF[F90E] [7B11]: peer lost
    [2016-04-02 22:36:46] SF[3AF3]: Stop folder synchronization
    [2016-04-02 22:36:46] SSPI[0x0000003be805f8d0]: Dispose SSPI connection

    [2016-04-02 22:36:46] SF[F90E]: Not loading torrents - sync is paused or fc error
    [2016-04-02 22:36:46] ScheduledTask: "ConnectMorePeers" invoked: timer, reason:ConnectMorePeers - sync is paused or fc error
    [2016-04-02 22:36:46] SF[F90E]: UpdatePeersStat
    [2016-04-02 22:36:46] ScheduledTask: "UpdatePeersStat" invoked: timer, reason:FinishStateSync
    [2016-04-02 22:36:46] SF[0D34]: UpdatePeersStat

    Down the logs it looks as if it connected to some peers but not all of them.

    If you want to the full logs please get me on Skype.

     

  2. I'd like to report another issue, I have seen it before and I think the problem did not exist in 2.2.x

    If you pause a VM and you start it again (for example when you restart the server that hosts the VMs), Sync will not connect again.

    I am using W2012 R2 Hyper-V.

    What I do when that happens is I restart the the service and everything works again.

  3. On 01/04/2016 at 3:16 PM, RomanZ said:

    @kamborio

    Yes. Sometimes, OS splits the event of file movements into "file deleted here" + "file appears here" couple of events. If they arrive separately, Sync could already move file to archive. Starting from 2.x (don't remember precise build) Sync also keeps track of Archived files MD5s and drags file out of archive if MD5 matches.

    @RomanZ

    That explains the higher memory usage on the other server.

    It's been 72 hours since I reported the memory usage and I am glad to let you know that still at the same values (kB up or down). It seems the memory leak is gone.

     

     

  4. 5 hours ago, RomanZ said:

    @kamborio Thanks for reporting - we'll try to reproduce and fix. What about your memleak?

    Memory usage is really good in this release.

    Main server (Read/Write), for 1.56M files in 7.11K folders - 1.6GB RAM

    Backup server (Read only), for 1.82M in 9.78K folders - 1.9GB RAM

    Note: The backup server has more files and folders because I am counting the .sync/Archive which I think makes a difference. Doesn't BitTorrent Sync trakcs the contents of the Archive to quickly restore a file and not transfer it again if it is restored on the other machine?

    So I think it is using much less memory than previous 2.3.x versions and doesn't seem to be leaking.

    CPU usage is still higher than 2.2.x but not exceptionally higher.

  5. Installed on 2 computers. Installation didn't go very well:

    1st computer: Service stopped, install completed without errors. Service did not start automatically. After starting service manually all was working.

    2nd computer: Service did not stop. Services console said "stopping" but it never stopped. Killed manually. Restarted installation. and this time it worked and service started automatically.

  6. 1 hour ago, RomanZ said:

    For the future time - well, its a tricky thing. It is pretty much the same for all platforms. Sync doesn't work well with future mtime, and there is no simple solution for that issue. Ideally, we'd like to show error message in future so user will be aware of the issue and fix it in his preferred way.

    I can imagine it can be a propper headache to deal with future dates. An error message would be helpful, I think I added the folder with version 2.3.3, it synced quite well among Windows clients but it failed on android. I only realized how to fix it when I upgraded to version 2.3.5 and a message came up on the screen.

    UPDATE: I just realized that I am still using version 2.3.3 on my desktop, so the message appeared using that version. I think the message only appears when you open Sync, not when you add the folder.

  7.  

    5 minutes ago, RomanZ said:

    @kamborio For the moment (=2.3.6) we've addressed all known leaks. Will be happy to get your logs :). As this is leak, only one peer (which is leaking) would be enough.

    Hello @RomanZ

    You surely remember how much I hate showing you my logs ;)

    2.3.5 is much better than 2.3.3 in terms of memory usage so happy at the moment. The issue only happened once. Let me try 2.3.6 and if it reoccurs I'll be in touch.

    I also had a problem with a mobile sync (android, sync not happening at all) because a file had a date set in the future (2095? or something like that). Once I change the date on the file everything worked fine. I was using 2.3.5 on the desktop and the latest available on the Play Store on the mobile.

  8. On 17/03/2016 at 9:30 AM, RomanZ said:

    @kamborio Try 2.3.4. There was indeed memleak so it may help you. For the #2 - installer prompts for the name of user to run under. Type in  "LOCAL SERVICE", leave pass empty.

    Thanks for confirming. I had some screenshots to prove my point but if you agree there was one I'll save my time.

    I have upgraded 1 machine to 2.3.5 today, more to follow. I will keep you posted.

    The machine I upgraded was a dual core with high CPU usage, it seems to have improved.

    I did try the "LOCAL SERVICE" approach and it works. Once you know it easy to use but I think you should use a similar approach to SQL Server install that makes it easy to choose which account to use.

    16lmsld.jpg

  9. 5 hours ago, RomanZ said:

    @carloxp The issue with all folders disappearing in 2.3.2 and 2.3.3 was already addressed in 2.3.4 (which is on the way).
    For the amount of files - I'm asking as amount of memory consumed by Sync is proportional to amount of files and folders it manages. It takes around 1.5 Kb of memory per file. So, the 100K of files and folders will force Sync to allocate around 150Mb of memory. So this info can give a hint if memory consumption is adequate or something is going wrong.

    That particular instance has 1,640,556 files and 7,263 folders.

    According to your numbers it should use around 2,403 MB RAM but it was using 4,941 MB when I got the alert for low memory.

    I restarted the service and it is currently using 2,636 MB (it has been running 4 hours).

    So yes, I think that version 2.3.3 has a memory leak.

    I will test 2.3.4 on the offending machines and I will let you know.

    Screenshot_20160316-145328.png

  10. 10 hours ago, RomanZ said:

    @kamborio

    1. When installing, try use the "LOCAL SERVICE" account. Should work fine.
    2. I'm attaching simple sync.conf file. Don't change the filename, just drop it to your storage folder:
      for LOCAL SERVICE account: C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\BitTorrent Sync Service\
      for SYSTEM account: C:\Windows\system32\config\systemprofile\AppData\Roaming\BitTorrent Sync Service\
      Then restart the service. It'll listen to all available interfaces. Adding the ,"force_https": true to the config file in "webui" section will also enforce https, although it does not work on windows due to known issue (already fixed, will be available in 2.3.4)
    3. (And 4) Its not a debugging turned on, neither memory leak. I suspect it is bound to new flow of things in Sync core. There was an couple of issues addressed regarding mem and CPU usage in upcoming 2.3.4, although I'll be more than happy to peek into your debug logs to see if this is something we already fixed or that is something new.

     

    1. When installing I have never seen the option to select "LOCAL SERVICE". It asks for username and password.

    2. I'll give it a try

    3. (and 4) Oh yes there is a memory leak somewhere. I got some servers starting with memory usage at 3.5 GB and then slowly using more memory until I have to restart the service, Ir particularly happens with servers with high number of files and frequent updates from peers. I will post a screenshot on a different post where you mentioned something about 1.5k RAM per file.

  11. After a week using 2.3.3 (jumped from 2.2.7), this is what I think:

    1. Love the new service install. Hate that you cannot install as SYSTEM (I mean, you can, but you have to stop service, change account, move config files to SYSTEM profile and start service... much easier if the install took care of that).
    2. I have not been able to configure and access remote GUI access yet. Hopefully options will be added to the UI in the near future to make this possible and also, to allow remote access from any IP via HTTPS.
    3. Memory usage: BAD, very BAD (compared to 2.2.7) I think there is a memory leak somewhere, I have seen cases of 11GB used by the process where before was 4GB (same machine, same number of files)
    4. CPU usage: SO SO. Not as good as 2.2.7. Makes me wonder if there are some debug options active?

     

  12. 10 hours ago, Helen said:

    (1) right. No, at least with Sync means and settings, it's not designed so.

    (2) perhaps you'll need to reconfigure your network and make a kind of a VPN tunnel to the machine where service runs, or access it via a remote desktop tool, so you'l be able to access WebUI remotely. 

    (3) But better to it the right way - either change the user in service properties, or define the necessary user when installing service. 

    (1) Actually, it is design to do so. You have built in the capability of accessing the UI remotely BUT you have capped it by hard coding from where you can access it. That's fantastic in terms of security but not giving the option of overriding it, make the feature useless under certain circumstances. I can only think that you are doing so you can now sell us your upcoming "Sync IT".

    (2) I am well aware of what I need to know to circumvent your hard coding but it makes my life more difficult. You should be making my life (as an IT admin) easier, not harder.

    (3) I may be wrong here but I do not remember the option of using the SYSTEM account when I installed it (at least version 2.3.1)

  13. 3 hours ago, RomanZ said:

    @kamborio We'll put it in future plans - meanwhile, you can use the conf file workaround.

    Hi RomanZ,

    Even if I make it work... I am still constrain by the "LAN only" constrain right? Anyway to circumvent that at this stage?

    Something else, somehow related... If I want to run the service under another user account (let's say SYSTEM), how easy is to move the configuration files and databases from one account to the other one?

  14. 8 hours ago, Helen said:

    And finally, note that webui will be access from a machine in LAN only. 

    Maybe I did manage to make it work BUT I wasn't trying to access it from LAN, which defeats the whole purpose.

    Now that (at last) BitTorrent Sync can be installed as a service means that no longer it is necessary to logon to the server so it runs, hence in an ideal world why do we need to logon to the machine to change the settings if could be done remotely?

    Whilst I can understand why you would implement such measures and they indicate how serious you are about security by locking down as much as possible the default installation, why don't you let advanced users to circumvent those security measures?

  15. It doesn't seem to take the option of 0.0.0.0. So far no luck to try and connect remotely.

    Using version 2.3.1 as a service.  Downloaded sample file. Made several changes and put in C:\ProgramData\BitTorrent Sync Service. Tried with sync.conf and btsync.conf. Service was restarted every change or rename.

    Having the option on the UI would definitely make things easier.

  16. @RomanZ

     

    I am not seeing that particular entry in the logs any more but, both nodes are still out of sync with version 2.2.0

     

    One node is  constantly sending around 1 Mbps of data to the other one files are not getting sync.

     

    The logs are showing a lot of info:

    [2015-09-13 23:15:39] RC[9DE8]: file updated - can't proceed rename for file "\\?\D:\file.yyy", t1:1246686063 t2:1246686063 s1:10105 s2:10105 p1:0 p2:0

     

    Or:

    [2015-09-13 23:25:06] MC[9DE8] [1F06]: too many nodes to send 187671, stopping at /file.xyz

     

    I am guessing that I will have to remove one of the folders, add it again and wait for 1.3 million files and 250GB to resync... Lovely!

     

    You are no longer in BETA, you are selling a commercial product and, some of us, are paying for it. You need to start getting things right...

  17. This is a known issue with 2.1.2 - the developers are aware and are working to fix.

    That's 3 releases back! The release prior to 2.1.2 was 2.1.1 - does that cause you problems also?

     

    3 releases back is where I was.

     

    2.1.3 seems to fix the slow interface and problems detecting new files that I have seen in 2.0.128 but it definitely introduces new issues. I am using /webui to be able to have an UI that at least is responsive.

     

    On top of that I just don't like that 2.1.x doesn't install in Program Files and it installs in the AppData folder. At least give us the choice!

  18. Useless release.

     

    Got 3 folders in a loop downloading a bunch of files for a total of... wait for it... 127TB! One of them is saying... 30 years to sync (the folder is 10GB and was fully sync before the upgrade).

     

    Not to mention the icon on the notification area that appears (in some machines) as paused.

     

    Fingers crossed... Let's try and roll back to 2.0.128.

  19.  

    We feel that the free version of Sync is a great product that will satisfy the needs of a lot of users. With the functionality/usability enhancements and core engine improvements for 2.0, it is much improved over Sync 1.4. 

     

     

    I think you have been quite kind with the restrictions. Some people wants everything for free.

     

    My only concern is, 1.4 is still not working properly, why should we paid for a product that is still not working?