RomanZ

Administrators
  • Posts

    3,588
  • Joined

  • Last visited

Everything posted by RomanZ

  1. In majority of cases we simply get the dumps automatically submitted by OS. It is not clear what the exact user path / environment to reproduce the crash - though it still caused by code imperfection / bugs and can be fixed.
  2. @dd6905 When discovering peers in LAN (if LAN discovery option is ON) Sync will try to find peers multicasting over port 3838. And starting from version 1.4 it subscribes and multicasts to all available interfaces. When issue reproduces I suggest checking who is subscribed to multicast and if your router distributes them correctly.
  3. Nicola, Folder preferences responsible for Syncing only over LAN (i.e. disabling tracker, relay and DHT) did not change in 1.4. Could you please elaborate ?
  4. @fooble It's not sort of feature - it is request to change the design. Sync intentionally does not delete pics on your PC when you remove them on iPhone. It is a backup and it wants to save you from accidental removal.
  5. @alleoma I suggest posting it to Feature Request forum as well.
  6. @onesolo This issue is not solved yet, sorry. @GusBricker Yes, there were a lot of "real fixes". For example, crashes are related to Sync core directly. @wutizurkwest Please note that Sync is in beta stage of development. Various bugs are still possible, though team does it best to address the most critical in prompt manner. @gl00mer Issue confirmed, we'll fix it. Thanks for reporting. @roza It simply does not listen the external interface anymore, only loopback. You need explicitly order sync to listen external interface, please see this article for details.
  7. Colin, I understand that "NAS-PC" is actually not a NAS. This is just a name for better understanding. As for the issue itself - I suspect that OS might not inform Sync about changes done to the folder over CIFS. Though, they should be picked up after some time (usually around 10 minutes) by folder scanner. The only trouble I can see here is if file was changed on other peer (PC 3 or PC 4) before change is detected - and in this case it will simply overwrite the change done on PC3 or PC4.
  8. Colin, Please take a look at the simple diagram. Is that something you mean in your setup? In this case PC4 and PC5 are probably your laptops which sync okay between themselves until PC1-3 does not change something in the sync folder over SMB/CIFS?
  9. @timdj Thanks for reporting. We'll check out what happened and how it can be fixed.
  10. @mogarick, @Arty2 I apologize for wrong information. The Glibc 2.3 version won't help here. The only way to run Sync would to indeed to stick with older WD firmware.
  11. @hurik There is no downgrade path. 1.3 and 1.4 are incompatible on a single PC due to differences in DB. So, if @djsuperstore wants to downgrade - he has to uninstall 1.4 with cleaning up all the Sync data and install it again. Obviously, he has to add all folders again (though he can use old secrets if they are stored somewhere). We'll do our best to align our releases with publishing them to NAS vendors in future. Though, they are currently behind our releases as they are delayed by NAS vendors. @adam1v The issue should be resolved with 1.4.82 @tenjaa We are working hard to publish official packages, but they are now get delayed by NAS vendors. We are doing our best to promote it and publish. As I got no any ETAs, I don't want to put any false expectations here. But why don't you want to use unofficial packages meanwhile? They contain the same binary and community does a great job to wrap it into a package and make easily available!
  12. @adonnan It looks to be working fine in our lab. What exactly is not working for you?
  13. @merlinuwe That's right.The WebUI for Linux and HTML UI is different. I'll check out these inconsistences and find out if they are intentional or not.
  14. @markymark77 I understand that you already stopped it. But just in case if this one repeats - we'll need debug logs from your android phone (just tap feedback, type text and agree to send the debugging information). The sooner you do it - the more chances for the failing event to get into the log. Also, I wonder if you have noticed - when it happened, the "Auto" setting in sync still stays disabled or it gets enabled?
  15. @chungyan5 Both your laptop and server has HW powerful enough.The only one thin place I can see is your server RAM. It is 2Gigs, while you attempt to sync around 2.3MLN files. When monitoring such amount of files, Sync will demand around 2Gb of RAM. OS will provide such amount of memory if it is x64 based - though, system will swap a lot. Though, you say that issue happens on laptop, which has around 8Gb of RAM - which should be enough to hold the files tree. To find a root cause of your issue we'll need your debug logs. As you get a bunch of files - please set your "log_size" advanced pref to 500 (which will give us around 1 gig space for sync.log and sync.log.old), then follow this instruction for log collection and sending to us. We'll do our best to solve it. Thanks!
  16. @merlinuwe Sorry, issue with the ports randomly changed is not solved in 1.4.83 yet. It affects both Linux WebUI and Windows-old-IE WebUI. We'll fix it soon. Could you please elaborate about links to KB? Where do you expect to see them and they are missing? @onesolo Please see the topicstarter - direct links are available now. @mariano As @GreatMarko said - as soon as 1.4 will be considered stable enough - we'll push it to auto-update. We expect i to happen within couple of weeks.
  17. Hi all, For now BT is not going to support this particular NAS model. Please use Sync with GlibC 2.3 as solution. It lacks only one function comparing to other builds - it does not subscribe for immediate directory change events, so files changed are detected only during full folder rescan.
  18. @sciurius Is it local network or peers are connected over internet? Wifi or wired? If it is local peer - there might be some issue in the router (for example, inability to serve multicast packets) If it is connected over internet - I suggest checking ability to connect to tracker server over TCP port 3000.
  19. Hi all, We are working on it. I'll post official answer a bit later here.
  20. @hurik Do not worry, all released builds will appear on syncapp.bittorrent.com, just in some cases they will be slightly delayed.
  21. Dear Stephen, Thanks for reporting. We'll fix the issue in one of future releases.
  22. @capi Confirmed issue with non-resizing columns on Firefox under Linux. @merlinuwe As GreatMarko said - port issue also confirmed and will be filed as bug. @ErgoPandemonium Could you please elaborate - what exactly is not working?
  23. @blackcloud BTSync encrypts photos before sending. In general, it always encrypts data prior to sending it (unless it is disabled explicitly in preferences - which is available only for Desktop clients).
  24. @ChrisH It is an issue of a renovated web-site, will be fixed soon.