ms2oo8

So I've tried to install Resilio on Centos 7 by following the instructions in the FAQ. I get stuck when I try to log into the web interface. The server is hosting in AWS with a static IP attached. I've edited the AWS Security Group to allow port 8888 and by all appearances Resilio is listening on port 8888, but no joy yet. On the server Firewall ports are open [root@control ~]# firewall-cmd --list-ports 443/tcp 49152-65535/tcp 139/tcp 138/tcp 6789/tcp 8888/tcp 80/tcp 20-21/tcp 8000/tcp 445/tcp 1088/tcp 137/tcp 901/tcp 22/tcp Resilio is listening on port 8888 [root@control ~]# nmap -sT -O localhost PORT STATE SERVICE 21/tcp open ftp 22/tcp open ssh 25/tcp open smtp 80/tcp open http 111/tcp open rpcbind 443/tcp open https 3306/tcp open mysql 8888/tcp open sun-answerbook [root@control ~]# systemctl status resilio-sync ● resilio-sync.service - Resilio Sync service Loaded: loaded (/usr/lib/systemd/system/resilio-sync.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2017-10-05 16:12:00 UTC; 17min ago Docs: https://help.getsync.com/ Process: 16124 ExecStart=/usr/bin/rslsync --config /etc/resilio-sync/config.json (code=exited, status=0/SUCCESS) Process: 16121 ExecStartPre=/bin/chown -R rslsync:rslsync /var/run/resilio-sync (code=exited, status=0/SUCCESS) Process: 16119 ExecStartPre=/bin/mkdir -p /var/run/resilio-sync (code=exited, status=0/SUCCESS) Main PID: 16127 (rslsync) CGroup: /system.slice/resilio-sync.service └─16127 /usr/bin/rslsync --config /etc/resilio-sync/config.json Oct 05 16:12:00 control.x.ca systemd[1]: Starting Resilio Sync service... Oct 05 16:12:00 control.x.ca systemd[1]: Failed to read PID from file /var/run/resilio-sync/sync.pid: Invalid argument Oct 05 16:12:00 control.x.ca systemd[1]: Started Resilio Sync service. Config file is default "webui" : { "listen" : "127.0.0.1:8888" } } Not sure where to go from here

just to reiterate the post here, we're currently syncing 3.79 TB of files (hundreds of thousands of files). Our Sync status is "Indexing" all the time, but as far as I can tell, it's keeping files up to date.

awesome, thanks for clarifying

so the latest is safe to upgrade from now? Or are we still waiting for a fix to this issue before it's considered stable to upgrade?

I have this issue as well and I'm running 2.3.1 so i don't think it's an issue due to 2.3.3 Parts of this site, including the forum and other help sections have had intermittent connectivity over the past few days. My assumption is that maybe the tracker servers are experiencing the same intermittent connection, causing this message in all clients, regardless of client version.

a few questions. did you isntall btsync on the NAS? iow is it the NAS hardware / cpu / ram that you're using to index your 3.7TB of data? To sync that many files and folders could require more RAM than your device has built in. We've run into similar issues syncing a similar amount of data. We're currently making out ok, thought it's not been entirely troublefree, by using dedicated Windows desktop clients to run the Sync software with mapped UNC drives. There has been issues previously with performance on mapped UNC drives. We do think that we're getting close to the point where we like the software, for as many issues as we've had getting it so far. I think we've been pushing it's limits a bit with the size of our sync data.

I'm having the same issue. Files are in the quene, the log says they uploaded, but they don't appear on the remote peer. The folders get created, but the files don't upload.

I am running Windows as well.

I have a .journal file that is sitting at 13GB. What do these files do and is there anything I can or should be doing to limit the size of this file?

Upgrading to Yosemite fixed this issue.

anybody? Is this simply a limitation of the Mac version?

Title says it all. I'm trying to link a device, so I copy the key from the first 2.0 device, go to my second device and click Link a Device already running Sync 2.0, click Link to a Desktop device manually, paste my key, and click link. The message saying that connecting can take as long as 60 seconds, comes up, and stays up forever. The device never links successfully. The only way I'm abe to get new devices connected eventually, is to create a new ID for each device, and then share a folder link from the original sync device, and eventually they connect. as an aside, both devices are desktop computers in thsi case, both running Windows 7

On Windows I can right click and "Sync to this device" for an entire folder or sub-folder. On Mac, this function seems missing, and I need to drill to the file level to get this fucntionality. How do I sync an entire folder with subfolders and files on Mac, without manually going into each sub folder to right click and download to the mac?

Thanks Sorry for being anxious about this bug. We bought about $2000 of hardware that we were planning to use with Sync, which is now sitting idle due to this bug. I'll sign up for 2.0, see if it works then.

Is this bug being tracked in your system? Also when is 2.0 ready for testing?

Is this fixed in the 2.0 Beta?

I think this is a great idea and the new Pro features look amazing!

Any updates on this issue yet?

Is the location your indexing a mapped network drive?

So I did some testing with RomanZ and it seems like my install is stuck completely re-Indexing almost constantly. We haven't figured out why yet, but think it might be due to the folder locations being mapped drives on SMB network shares. It keeps re-indexing previously indexed files, that I am 100% certain haven't been changed by a person. This leaves a few scenarios possible 1) software on the NAS box is reading files (for whatever reason, rsync backup of the NAS box to another NAS box etc) and is triggering Sync to re-index somehow 2) a bug in the Sync software as expained above I'd be inclined to think it's a bug, since I have another NAS with a mapped SMB share on the other end, with the same issues, but it's a different brand of NAS box, with no backup configured on it.

What does this option do in Advanced Options?

I think it is, but it seems to Index almost permanently. I'm concerned that it takes so long to Index changes because I'm afraid that it won't keep up.

I've currently got about 2TB of data synced up (almost) across a gigabit network, and 2 NAS boxes. When I move files from one location to another, does the sync clients on the other end, move like the Linux mv command, or does the data copy and paste across the network, even though all that happened is that it changed location? When I attempt this, it seems like moving files to a different location inside the same sync directory makes the entire contents copy and paste across the network, when in reality, all it had to do was move the contents on the remote side to the same location. I'm running BTSync 1.4.93 on both ends.

I'm ready to look for another solution like AeroFS. This really doesn't seem to be working.

it's 2TB of data. (628,000 files in 30,311 folders) I have the Sync app installed on a Windows boxes on either end, (i5 750 x64 Win 7 with 8GB RAM and a i7 2600 x64 Win 7 with 8GB RAM) and both are not performing any other tasks. I reconfigured the Peers to map via a drive letter vs the UNC path. Everything synced up, except 1 open office file, which was locked due to it being open. When I closed it, sync stayed stuck at the locked file status. So I closed the app on both ends again, and now we're back to Indexing . . . . having said all that, it shows Indexing status as we speak, but it seems to be syncing any changes I make immediately right now