PacketMan

Members
  • Content count

    52
  • Joined

  • Last visited

About PacketMan

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Interests
    FreeBSD
  1. Well I guess we all have our own ideas as to what is urgent. That all aside, care to comment on what might be happening in my installation environment?
  2. So I mentioned this on the old forum but I'll mention it again, plus a couple other items I am now doing. I have a few NAS type servers (most are off site) build with FreeBSD, an awesome OS I might add, check it out! I have security cameras that send pictures to a folder on the NAS. BTsync simply syncs to each server, and those sync to our cell phones. If the alarm company calls we have pictures on our phones. Also in the event the NAS was found and stolen or destroyed, copies of the bad guys are already off site. Our library of family moments (pictures and videos) are replicated to the off site servers. Those servers use Minidlna to stream the libraries to smart TVs. So our parents who live in other parts of the world can enjoy our pictures and videos simply using the TV remote control. Side benefit of using BTsync - since my NAS is replicated to off-site servers if my home server were to suffer a catastrophic failure or be destroyed in fire for example I have multiple copies already off-site that I can use. (Note since i use read/write mode everywhere for various reasons, I also use external drives to make rotating copies off-site, just in case somehow a "rm -r *" type boo boo is done.) (Shameless promotion - I realize there are a lot of folks here that use various OSs, but if you are in the mood to try something truly refreshing, rock solid architecture, etc you should give FreeBSD a try. Its a direct descendant of the BSD type UNIX and if you have a open mind I believe you won't be disappointed.)
  3. So I noticed a bunch of topics (including this one) didn't get any love from the 'staff', yet other do. Why? What determines which one you respond to? Or are you just doing the easy ones? Regarding this issue I managed to get my shares up and running again. I had to completely delete them, and re-add them. And after a fair bit of more reviewing it seems obvious that the renaming of files (folders and or files) causes syncing to break. Which is kind of interesting because in FreeBSD there is no rename command. We use the 'mv' (move) command. I'm guessing there are some Linux OSs that have the same behaviour too. It seems as along as I use 'cp' (copy), let sync finish, and then 'rm' (remove) it works fine.
  4. Well I managed to add back one sync/share instance without issue. However my attempt at adding back in a 2nd sync/share instance is running into a thick stone wall. It will transfer about 405+ MB of content (out of a possible 3.8 GB, which is one of my smaller folders) and then simply stop. Repeat over and over = same results over and over. Arrgghhhh. Never had this with my way old version. I'll tinker with this a bit more, but I would say it looks like this coming weekend I am gonna roll back to the old version. I've pretty much lost trust in these never versions. ....unless a site admin or other Resilio can convince me otherwise. And while on the topic, I realize I have not paid for support, but the lack of response from admins is a bit concerning too. The top of this topic group says "Having problems with Sync? Found a bug? This is the place to post about it! "
  5. I got stung bad by this issue: I took for granted that sync was working fine, but in reality it had been broken for many weeks. Please bring back the sync status on the main page. How hard can a piece of logic like that be? All peers in sync = green, some nodes in sync = yellow, no nodes in sync = red.
  6. Gee its quiet in here. So I am pretty sure I have identified the cause of my troubles: renaming files including folders. I believe this issue was stated as being fixed in an earlier release but I am using version 2.3.8 (560). and I am pretty sure the sync/share instances affected by this have a messed up 'state'. So I am deleting my instances, and creating new (new key) instances. The first one seemed to load up fine. I will soon test by creating new folders (instead of renaming) and then moving files from folder to folder. I'll also try to make it a habit of organizing my file names before I put into a sync'd folder. And I also pretty sure this issue occurred only days after I upgraded to 2.3.8 (560). I never got affected by this issue with the way older version of BTsync.
  7. So it now seem a couple of the sync/share instances are okay, and others are royally busted. Not exactly sure yet but the royally busted ones seem to be not syncing or one-way syncing, maybe on a per files basis. Only thing I can gather is the sync/share instances that are really large are the ones that have broken. And it seems the 'break' is between individual sync nodes; meaning its not just one node that has gone awry, but there are issues between 1<>2, 2<>3, and 1<>3. Still troubleshooting, but it only other thing I can see is in the history section I see stuff like CheckOriginalFile:No such file or directory, or CheckSuffixFile:No such file or directory. Anyone got any ideas? And I'd like to know what possibly caused or triggered this.
  8. I decided to delete a sync/share instance on #2 machine. I added it back in. Both machines started talking (LED lights on LAN switch blinking fast). #2 machine began re-indexing the folder. Re-indexing complete. Both machines stuck saying they have to upload/download from one another. Both machines still have what I showed in first post. Really starting to wonder if I should have stayed with the really old version that I ran for ages without issue. Server 1 # ls | grep Sonny Sonny_Boy_Williamson Sonny_Boy_Williamson_2 Server 2 # ls | grep Sonny Sonny Boy Williamson
  9. Hi all, I have had a near flawless expereince with BTsync in a FreeBSD OS environment. I used a very old version for a very long time. A couple weeks ago I upgraded my three FreeBSD nodes to 2.3.8 (560) and I thought all was working well. This morning I discovered that ain't the case. All three of my nodes have stopped syncing to each other. Currently one is out on the Internet, and the other two are on the same LAN (same broadcast domain & IP subnet). I have paused/restarted individual shares, stopped BTsync process, wait like 10 minutes, start 1, wait, start another, wait, etc. No change. In an effort to make sense of this I tried renaming a folder to see what might happen. Folder name was orignally "Sonny Boy Williamson". I then renamed it to "Sonny_Boy_Williamson". I got this result: Server #1# ls | grep Sonny Sonny_Boy_Williamson Server #2# ls | grep Sonny Sonny Boy Williamson After 10 or so minutes I then on server 1 I copied the folder to yet another new name, and I got the same result no syncing: Server 1 # ls | grep Sonny Sonny_Boy_Williamson Sonny_Boy_Williamson_2 Server 1 # ls | grep Sonny Sonny Boy Williamson Both Sync instances find the folders/files and say they are uploading to the other node, but there is no actual transfer of files going on. My LAN switch LEDs confirm there is squat traffic. I am really hoping you are gonna tell me you are having an issue with your relay server or something, but the part that bothers me is these two nodes are on the same LAN and can discovered each other directly. Thoughts? What other troubleshooting could I do? Thank a bunch in advance from a long time Sync user, and general bittorrent fan.
  10. I posted to the feature request forum quite a while ago. Any comments as to when if/when this will be brought back?
  11. Yes I too think it should be brought back having status in the main UI window 100% of the time, on a per share basis. Leaving it empty, leaves me with well an empty feeling. I'm still testing 2.2.x on various platforms, most of them FreeBSD OS. Hoping to migrate every from 1.3 to 2.2 before the spring comes. But this empty status field causes me to say "yeah but" and hesitate.
  12. Any update this to this? I am trialing version 2.2.x and sp far so good, but this empty status field leaves me well with an empty feeling. Please find those 'bugs', and please implement an accurate working status field. Thanks in advance, PacketMan
  13. would be nice to have a response or two, to this.
  14. I'm curios too learn how well these latest 2.0.x versions are working, espescially across the various platforms, including Andriod, FreeBSD. I'm still running good ole 1.3.94, but am hoping to upgrade to 2.0 or 2.1 version before 2015 is over. Thanks all, P.M.