@calmh wrote:

For discussion of https://github.com/syncthing/syncthing/pull/6214 without overwhelming that PR

Posts: 3

Participants: 2

Read full topic

@HalfNote5 wrote:

Just curious:

(And full disclosure I think I’m probably looking for a manual/readme page I’m missing. It’s early.) XD

How does the index-{n.n.].db folder work? What I mean is, are the .ldb files routinely cleaned up and restructured or do they just sort of accrue?

I know you don’t restore them on the event of a system crash, and they get rebuilt, when the systems compare files on the near end to the far, but is there any benefit/need to clearing them routinely or does (as I suspect) the program handle that? How about the log?

Also, how large do they eventually get? If I knew how they worked (format/info stored/method of function) I could probably figure that out without too much ado, but since I’m asking inane questions, I thought I’d toss that one in.

Posts: 8

Participants: 3

Read full topic

@David.P wrote:

Hi Forum,

I’ve successfully synchronized a destination folder (on a destination PC) with a source folder (on a source PC), using the “Receive Only” synchronization type.

Then I stopped the synchronization and moved the destination folder to another hard drive on the destination PC.

After that I set up a new synchronization, and the (moved) destination folder was successfully synchronized with the source folder again. So far so good.

Now I plan to change the synchronization type from “Receive Only” to “Send and Receive”.

When doing so, I want to be 100% sure that no files are accidentally deleted from the source folder.

If, for some reason, the destination folder should contain fewer files than the source folder in the meantime, and therefore the switch from “Receive Only” to “Send and Receive” could lead to files being deleted in the source folder, I want to make sure that these files are at least being backed up using File Versioning.

Now I’m only not sure whether I should set up File Versioning on the source PC or on the destination PC for this purpose?

If both should be possible, I’d rather set up File Versioning on the destination PC.

Many thanks for help :o

Posts: 2

Participants: 2

Read full topic

@Abe_Jasa_Saia wrote:

how do i use different ip lan when opening 2 synctrayzor?

Posts: 1

Participants: 1

Read full topic

@williamturner wrote:

Hi Syncthing.

1. Great job!

2. Could a small section be added on the ‘Getting Started’ web page to make clear that to be able to sync one folder across many devices the FOLDER ID should be the same, as it took a lot of determination to find, when it should be easy to find. Only hrs of searching the forums finally got the answer by stumbling across comments about folder ID needing to be the same.

I feel many potential new users are keen to use syncthing to do more complex setups than one folder between device A to device B, but the easy-to-find documentation doesn’t make it clear how to achieve more complex sync situations or if syncthing is capable.

Small tweaks to the easy-to-find typical web search results, as described below should give potential new users enough info to confirm how awesome and capable syncthing is.

.

**SUGGESTION / REQUEST ** .

Please update the ‘getting started’ webpage with a section “Example Setups” (or similar) with content similar to:

ONE FOLDER - MULTIPLE DEVICES

To synchronize a folder (e.g. folder “F”) that you wish to have the same data contents across multiple devices (e.g. devices “A”, “B” and “C”) then create a new share on each device using “Add Folder” and ensure the “Folder ID” is the same on all devices

SEND ONLY MODE

To have one device act as a “master copy” and other devices to clone from the “master”, use “send only” mode. See page: https://docs.syncthing.net/users/foldertypes.html

RECEIVE ONLY MODE

To have a device clone changes made on the cluster, but not distribute local changes use “receive only” mode. See page: https://docs.syncthing.net/users/foldertypes.html

ONE FOLDER - via SERVER (rather than peer-to-peer)

To have multiple client devices synchronize a folder via a server device (e.g. a PC device “A”, an Android device “B” and a NAS device “C” where A and B sync only to C, not directly between each other) then:

when adding a folder on device “A” you need to … (?? please complete??),

when adding a folder on device “B” you need to …(?? please complete??),

when adding a folder on device “C” you need to … (?? please complete??)

That should highlight to most new potential users that are having a quick read to see if syncthing is suitable that its quite capable.

PS. I’m just starting testing, but it looks like the right tool for the job so once stable will definitely be donating.

Posts: 2

Participants: 2

Read full topic

@bege wrote:

Hi, I use Syncthing to sync my PC with two phones.

One folder tree is synced completely between PC and phone 1, with phone 2 I sync only a subfolder of that tree. So on my PC there is one .stfolder in the root of that tree and one in the subfolder.

On the phone 1 the full tree and on the PC the subfolder are send-only.

When I sync the full tree with phone 1 the .stfolder in the subfolder on the PC is deleted. The result is the message that .stfolder is missing in that folder on my PC.

I think Syncthing should not touch any .stfolder during syncing or do I misunderstand something?

Posts: 3

Participants: 2

Read full topic

@edrock200 wrote:

Hello, I was wondering is this feature exists in syncthing. Let’s say the remote site folder is /root/syncremote and the local is /root/synclocal

If I copy 5 files into /root/syncremote/content/ is there a way for /root/synclocal/content/ to not rename the 5 files from their temp sync names to their actual names until all 5 files are done syncing, i.e. not rename the first file once it’s complete, but wait for the entire folder to be completed? Thank you in advance. Ed

Posts: 1

Participants: 1

Read full topic

@z3rograv1tyx wrote:

I am unsure if this is a bug or not so I’m posting here. Backstory notes, we had Resilio Sync setup w these folders before this. Also worth noting, I should be downloading NO files. All my files are share only. So I set each folder as “Send only”, and on his end he set them all to “Read only”. We’re both on v1.3.2.

So, I installed Syncthing (SyncTrayzor) on Windows, and my friend installed on his Synology NAS through their package manager (On his end he gave Syncthing full permissions to the folders, unless he did something wrong?)

We both set it up, he gave me his remote device ID and I added it. After doing so, he added a folder, and linked it to a folder that had files in it already, and then sent the request to me, I paired it to the exact corresponding folder on my side. We did this for 3 different folders. (Note, these are the EXACT directory to directory pairing we had in resilio sync).

After this, we noticed a few issues. After the folders scans were done, they had a few out of sync errors. If I clicked it, it showed 4 files, they all belonged to “.sync” folder, which was resilio syncs folder, despite it being disconnected left the folder. As to why it had issue syncing idk. But anyways we deleted the .sync folders on both ends of all the folders. After rescanning, the out of sync error still showed. Also those same files. I had just selected “override changes” and now they all show “up to date”… on my end at least.

Now on HIS end, it shows errors on one of the folder, and it says theres like 1k files out of sync (there shouldn’t be, and there isn’t). On my end it shows up to date on that folder. Now on my end, under “remote devices” it shows his device, and its just stuck at “Syncing (97%, 904MiB)”, on his side, my device shows up to date. So we have basically opposite issues. On his end, he sees a folder out of sync, but my device fine. And on my end my folders are fine, his device is out of sync.

ALSO on my end, under remote devices, his device shows “Out of sync items: 15,232 items, ~904 MiB” which makes zero sense to me because all my folders show up to date. So clearly something isn’t right.

I’ve let it sit, it’s been sitting here for about 3 hours now, and on my side the “remote devices” for his device is still just stuck on the 97% syncing. Idk about his end, I assume nothing has changed though. I’m not seeing any duplicate files or anything. Not sure if we missed a setting, or if we screwed up something, or if this is actually a bug. But we’d appreciate any help. Thank you.

But yeah, those are my issues. Everything seems to be working as far as sync goes, I put a text file in each of the folders, and they appear on the other end. I just can’t get everything to show as properly synced. Sorry if any of this was confusing, I was confusing myself just typing it up. It’s though to explain it from both sides clearly. Feel free to inquire about anything.

Posts: 4

Participants: 2

Read full topic

@pegasusDum wrote:

Create an ios app that can backup my camera roll automatically to my syncthing server.

Posts: 2

Participants: 2

Read full topic

@Tenrys wrote:

Hello,

I’ve set up Syncthing as a way to synchronize my music from my computer to my phone. It is set to receive only, and sometimes I want to delete a song off my phone. I don’t want to use the send & receive mode in case of a potential data loss, so is it possible to find out what changes have been made to the files on a synced device, so I can replicate them manually on another?

Sorry if this is a little confusing to understand. Thank you for the help!

Posts: 2

Participants: 2

Read full topic

@jbssm wrote:

Hi all, I have been using Syncthing without any issues for the past couple of years in Linux.

I now tried to setup a windows machine and I am having a problem with file permissions.

For some reason Syncthing sets all file permissions in windows with the “executable” bit. This means that inside Windows Subsystem for Linux, they show up as “755”.

Is this a bug or is there any setting I am missing here?

Posts: 7

Participants: 2

Read full topic

@dinosore wrote:

She who must be obeyed runs Windows 10 on her laptop with SyncTrayzor.

She rarely reboots and keeps multiple documents and multiple tabs in multiple browsers open for days.

I suspect that there is lots of crapware and other stuff to sort out.

The end result is that it runs s l o w l y.

Looking at the gui on the local pi, I noticed that she hadn’t connected recently.

I found that Synctrayzor wasn’t running, started it, updated it and got syncthing going again.

Still didn’t connect.

Currently

 Address	dynamic
relay://136.243.66.99:22067
quic://192.168.1.132:22000
context deadline exceeded (15:52:16)
tcp://192.168.1.132:22000
i/o timeout (15:52:06)
tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000
i/o timeout (15:52:06)
quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000
context deadline exceeded (15:52:16)
 Last seen	2019-11-12 16:37:00

Log

2019-12-09 04:01:40 My ID: 3YBZSGE-...
2019-12-09 04:01:41 Single thread SHA256 performance is 45 MB/s using minio/sha256-simd (44 MB/s using crypto/sha256).
2019-12-09 04:01:41 Hashing performance is 41.10 MB/s
2019-12-09 04:01:42 Ready to synchronize Pdocs (sendreceive)
2019-12-09 04:01:42 Ready to synchronize Pdocuments (sendreceive)
2019-12-09 04:01:42 Ready to synchronize Phhg (sendreceive)
2019-12-09 04:01:42 Ready to synchronize Ppics (sendreceive)
2019-12-09 04:01:42 Ready to synchronize "stStuff" (xkqsj-csnz5) (sendreceive)
2019-12-09 04:01:42 Ready to synchronize "Dvideos" (7sth4-fdehd) (sendreceive)
2019-12-09 04:01:42 Ready to synchronize Ddocuments (sendreceive)
2019-12-09 04:01:42 ...
2019-12-09 04:01:42 Ready to synchronize Dpictures (sendreceive)
2019-12-09 04:01:42 Ready to synchronize Ppictures (sendreceive)
2019-12-09 04:01:42 Ready to synchronize Dldocs (sendreceive)
2019-12-09 04:01:42 Ready to synchronize Dmusic (sendreceive)
2019-12-09 04:01:42 Overall send rate is unlimited, receive rate is unlimited
2019-12-09 04:01:42 QUIC listener ([::]:22000) starting
2019-12-09 04:01:42 TCP listener ([::]:22000) starting
2019-12-09 04:01:42 GUI and API listening on 127.0.0.1:8384
2019-12-09 04:01:42 Access the GUI via the following URL: http://127.0.0.1:8384/
2019-12-09 04:01:42 My name is "pi4b"
2019-12-09 04:01:42 Device B3IQ5IL-... is "pie" at [tcp://away.example.co.uk]
2019-12-09 04:01:42 Device CLKW22T-... is "PAULINE-PC" at [dynamic]
2019-12-09 04:01:42 Device NC5XMBX-... is "anzu" at [dynamic]
2019-12-09 04:01:42 Device T23BC6D-... is "monocerus" at [dynamic]
2019-12-09 04:01:42 Device VZN3PZC-... is "unicorn" at [dynamic]
2019-12-09 04:01:43 Completed initial scan of sendreceive folder Dldocs
2019-12-09 04:01:43 Completed initial scan of sendreceive folder "Dvideos" (7sth4-fdehd)
2019-12-09 04:01:43 Completed initial scan of sendreceive folder Ppictures
2019-12-09 04:01:43 Completed initial scan of sendreceive folder "stStuff" (xkqsj-csnz5)
2019-12-09 04:01:44 Completed initial scan of sendreceive folder Phhg
2019-12-09 04:01:44 Completed initial scan of sendreceive folder Pdocuments
2019-12-09 04:01:46 Completed initial scan of sendreceive folder Ppics
2019-12-09 04:01:47 Completed initial scan of sendreceive folder Dpictures
2019-12-09 04:01:55 Completed initial scan of sendreceive folder Ddocuments
2019-12-09 04:01:56 Completed initial scan of sendreceive folder Pdocs
2019-12-09 04:01:59 Completed initial scan of sendreceive folder Dmusic
2019-12-09 04:02:01 quic://0.0.0.0:22000 detected NAT type: Port restricted NAT
2019-12-09 04:02:01 quic://0.0.0.0:22000 resolved external address quic://1.2.3.4:22000 (via stun.syncthing.net:3478)
2019-12-09 04:02:02 Detected 1 NAT service
2019-12-09 04:11:41 Established secure connection to B3IQ5IL-... at 192.168.1.12:22000-5.6.7.8:52868/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256
2019-12-09 04:11:41 Device B3IQ5IL-... client is "syncthing v1.3.2" named "pie" at 192.168.1.12:22000-5.6.7.8:52868/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256
2019-12-09 04:31:44 Sent usage report (version 3)
2019-12-09 11:43:01 Established secure connection to NC5XMBX-... at [fe80::fdec:66ea:7309:9b92%eth0]:22000-[fe80::dd5b:263e:c0bf:2eff%eth0]:45860/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256
2019-12-09 11:43:01 Device NC5XMBX-... client is "syncthing v1.3.2" named "anzu" at [fe80::fdec:66ea:7309:9b92%eth0]:22000-[fe80::dd5b:263e:c0bf:2eff%eth0]:45860/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256
2019-12-09 13:10:47 Enabled debug data for "connections"
2019-12-09 13:10:55 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial: context deadline exceeded
2019-12-09 13:10:55 dialing CLKW22T-... quic://192.168.1.132:22000 error: dial: context deadline exceeded
2019-12-09 13:10:55 failed to connect to CLKW22T-... 99
2019-12-09 13:10:55 Reconnect loop for T23BC6D-... []
2019-12-09 13:10:55 Reconnect loop for VZN3PZC-... []
2019-12-09 13:10:55 sleep until next dial 1m0s
2019-12-09 13:11:55 Reconnect loop
2019-12-09 13:11:55 Reconnect loop for CLKW22T-... [quic://192.168.1.132:22000 quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= tcp://192.168.1.132:22000 tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000]
2019-12-09 13:11:55 Dialer for relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= is disabled
2019-12-09 13:11:55 dialing CLKW22T-... tcp://192.168.1.132:22000 prio 9
2019-12-09 13:11:55 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 9
2019-12-09 13:12:05 dialing CLKW22T-... tcp://192.168.1.132:22000 error: dial tcp 192.168.1.132:22000: i/o timeout
2019-12-09 13:12:05 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial tcp [fe80::7191:68c7:ffd4:f383%eth0]:22000: i/o timeout
2019-12-09 13:12:05 failed to connect to CLKW22T-... 9
2019-12-09 13:12:05 dialing CLKW22T-... quic://192.168.1.132:22000 prio 99
2019-12-09 13:12:05 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 99
2019-12-09 13:12:15 dialing CLKW22T-... quic://192.168.1.132:22000 error: dial: context deadline exceeded
2019-12-09 13:12:15 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial: context deadline exceeded
2019-12-09 13:12:15 failed to connect to CLKW22T-... 99
2019-12-09 13:12:15 Reconnect loop for T23BC6D-... []
2019-12-09 13:12:15 Reconnect loop for VZN3PZC-... []
2019-12-09 13:12:15 sleep until next dial 1m0s
2019-12-09 13:13:15 Reconnect loop
2019-12-09 13:13:15 Reconnect loop for CLKW22T-... [quic://192.168.1.132:22000 quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= tcp://192.168.1.132:22000 tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000]
2019-12-09 13:13:15 Dialer for relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= is disabled
2019-12-09 13:13:15 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 9
2019-12-09 13:13:15 dialing CLKW22T-... tcp://192.168.1.132:22000 prio 9
2019-12-09 13:13:25 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial tcp [fe80::7191:68c7:ffd4:f383%eth0]:22000: i/o timeout
2019-12-09 13:13:25 dialing CLKW22T-... tcp://192.168.1.132:22000 error: dial tcp 192.168.1.132:22000: i/o timeout
2019-12-09 13:13:25 failed to connect to CLKW22T-... 9
2019-12-09 13:13:25 dialing CLKW22T-... quic://192.168.1.132:22000 prio 99
2019-12-09 13:13:25 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 99
2019-12-09 13:13:35 dialing CLKW22T-... quic://192.168.1.132:22000 error: dial: context deadline exceeded
2019-12-09 13:13:35 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial: context deadline exceeded
2019-12-09 13:13:35 failed to connect to CLKW22T-... 99
2019-12-09 13:13:35 Reconnect loop for T23BC6D-... []
2019-12-09 13:13:35 Reconnect loop for VZN3PZC-... []
2019-12-09 13:13:35 sleep until next dial 1m0s
2019-12-09 13:14:35 Reconnect loop
2019-12-09 13:14:35 Reconnect loop for CLKW22T-... [quic://192.168.1.132:22000 quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= tcp://192.168.1.132:22000 tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000]
2019-12-09 13:14:35 Dialer for relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= is disabled
2019-12-09 13:14:35 dialing CLKW22T-... tcp://192.168.1.132:22000 prio 9
2019-12-09 13:14:35 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 9
2019-12-09 13:14:45 dialing CLKW22T-... tcp://192.168.1.132:22000 error: dial tcp 192.168.1.132:22000: i/o timeout
2019-12-09 13:14:45 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial tcp [fe80::7191:68c7:ffd4:f383%eth0]:22000: i/o timeout
2019-12-09 13:14:45 failed to connect to CLKW22T-... 9
2019-12-09 13:14:45 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 99
2019-12-09 13:14:45 dialing CLKW22T-... quic://192.168.1.132:22000 prio 99
2019-12-09 13:14:55 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial: context deadline exceeded
2019-12-09 13:14:55 dialing CLKW22T-... quic://192.168.1.132:22000 error: dial: context deadline exceeded
2019-12-09 13:14:55 failed to connect to CLKW22T-... 99
2019-12-09 13:14:55 Reconnect loop for T23BC6D-... []
2019-12-09 13:14:55 Reconnect loop for VZN3PZC-... []
2019-12-09 13:14:55 sleep until next dial 1m0s
2019-12-09 13:15:55 Reconnect loop
2019-12-09 13:15:55 Reconnect loop for CLKW22T-... [quic://192.168.1.132:22000 quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= tcp://192.168.1.132:22000 tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000]
2019-12-09 13:15:55 Dialer for relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= is disabled
2019-12-09 13:15:55 dialing CLKW22T-... tcp://192.168.1.132:22000 prio 9
2019-12-09 13:15:55 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 9
2019-12-09 13:16:05 dialing CLKW22T-... tcp://192.168.1.132:22000 error: dial tcp 192.168.1.132:22000: i/o timeout
2019-12-09 13:16:05 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial tcp [fe80::7191:68c7:ffd4:f383%eth0]:22000: i/o timeout
2019-12-09 13:16:05 failed to connect to CLKW22T-... 9
2019-12-09 13:16:05 dialing CLKW22T-... quic://192.168.1.132:22000 prio 99
2019-12-09 13:16:05 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 99
2019-12-09 13:16:05 Enabled debug data for "dialer"
2019-12-09 13:16:15 dialing CLKW22T-... quic://192.168.1.132:22000 error: dial: context deadline exceeded
2019-12-09 13:16:15 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial: context deadline exceeded
2019-12-09 13:16:15 failed to connect to CLKW22T-... 99
2019-12-09 13:16:15 Reconnect loop for T23BC6D-... []
2019-12-09 13:16:15 Reconnect loop for VZN3PZC-... []
2019-12-09 13:16:15 sleep until next dial 1m0s
2019-12-09 13:17:15 Reconnect loop
2019-12-09 13:17:15 Reconnect loop for CLKW22T-... [quic://192.168.1.132:22000 quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= tcp://192.168.1.132:22000 tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000]
2019-12-09 13:17:15 Dialer for relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= is disabled
2019-12-09 13:17:15 dialing CLKW22T-... tcp://192.168.1.132:22000 prio 9
2019-12-09 13:17:15 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 9
2019-12-09 13:17:25 dialing CLKW22T-... tcp://192.168.1.132:22000 error: dial tcp 192.168.1.132:22000: i/o timeout
2019-12-09 13:17:25 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial tcp [fe80::7191:68c7:ffd4:f383%eth0]:22000: i/o timeout
2019-12-09 13:17:25 failed to connect to CLKW22T-... 9
2019-12-09 13:17:25 dialing CLKW22T-... quic://192.168.1.132:22000 prio 99
2019-12-09 13:17:25 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 99
2019-12-09 13:17:35 dialing CLKW22T-... quic://192.168.1.132:22000 error: dial: context deadline exceeded
2019-12-09 13:17:35 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial: context deadline exceeded
2019-12-09 13:17:35 failed to connect to CLKW22T-... 99
2019-12-09 13:17:35 Reconnect loop for T23BC6D-... []
2019-12-09 13:17:35 Reconnect loop for VZN3PZC-... []
2019-12-09 13:17:35 sleep until next dial 1m0s
2019-12-09 13:18:35 Reconnect loop
2019-12-09 13:18:35 Reconnect loop for CLKW22T-... [quic://192.168.1.132:22000 quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= tcp://192.168.1.132:22000 tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000]
2019-12-09 13:18:35 Dialer for relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= is disabled
2019-12-09 13:18:35 dialing CLKW22T-... tcp://192.168.1.132:22000 prio 9
2019-12-09 13:18:35 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 9
2019-12-09 13:18:45 dialing CLKW22T-... tcp://192.168.1.132:22000 error: dial tcp 192.168.1.132:22000: i/o timeout
2019-12-09 13:18:45 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial tcp [fe80::7191:68c7:ffd4:f383%eth0]:22000: i/o timeout
2019-12-09 13:18:45 failed to connect to CLKW22T-... 9
2019-12-09 13:18:45 dialing CLKW22T-... quic://192.168.1.132:22000 prio 99
2019-12-09 13:18:45 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 99
2019-12-09 13:18:55 dialing CLKW22T-... quic://192.168.1.132:22000 error: dial: context deadline exceeded
2019-12-09 13:18:55 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial: context deadline exceeded
2019-12-09 13:18:55 failed to connect to CLKW22T-... 99
2019-12-09 13:18:55 Reconnect loop for T23BC6D-... []
2019-12-09 13:18:55 Reconnect loop for VZN3PZC-... []
2019-12-09 13:18:55 sleep until next dial 1m0s
2019-12-09 13:19:55 Reconnect loop
2019-12-09 13:19:55 Reconnect loop for CLKW22T-... [quic://192.168.1.132:22000 quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= tcp://192.168.1.132:22000 tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000]
2019-12-09 13:19:55 Dialer for relay://136.243.66.99:22067/?id=OEDHLSY-...&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy= is disabled
2019-12-09 13:19:55 dialing CLKW22T-... tcp://192.168.1.132:22000 prio 9
2019-12-09 13:19:55 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 9
2019-12-09 13:20:05 dialing CLKW22T-... tcp://192.168.1.132:22000 error: dial tcp 192.168.1.132:22000: i/o timeout
2019-12-09 13:20:05 dialing CLKW22T-... tcp://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial tcp [fe80::7191:68c7:ffd4:f383%eth0]:22000: i/o timeout
2019-12-09 13:20:05 failed to connect to CLKW22T-... 9
2019-12-09 13:20:05 dialing CLKW22T-... quic://192.168.1.132:22000 prio 99
2019-12-09 13:20:05 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 prio 99
2019-12-09 13:20:15 dialing CLKW22T-... quic://192.168.1.132:22000 error: dial: context deadline exceeded
2019-12-09 13:20:15 dialing CLKW22T-... quic://[fe80::7191:68c7:ffd4:f383%25eth0]:22000 error: dial: context deadline exceeded
2019-12-09 13:20:15 failed to connect to CLKW22T-... 99
2019-12-09 13:20:15 Reconnect loop for T23BC6D-... []
2019-12-09 13:20:15 Reconnect loop for VZN3PZC-... []
2019-12-09 13:20:15 sleep until next dial 1m0s
etc., etc.

Is there a way to configure a shorter timeout?

It looks like timeouts were reduced around the time quic was introduced. Am I right?

Posts: 3

Participants: 2

Read full topic

@steveharman wrote:

Hi,

I’m syncing between my desktop Mac & a Synology NAS. Sync Thing v1.3.2 both ends.

I have an item which appears to be “stuck” and constantly shows as failing to sync in the web UI of Sync Thing on the NAS. The sync status is fine on the desktop. It was a folder I deleted, I didn’t need it, it’s not on my local anymore and I have no interest in it. However it still appears as a “Failed Item” in “Out of Sync Items” on the NAS.

As it no longer exists on my local I can’t delete it again from there so I tried deleting the offending folder on the NAS as well, but it still shows as a “Failed Item” in “Out of Sync Items” - even though the item no longer exists in either location. I’ve tried pausing the relevant folder-sync, resuming and hoping a re-scan migt sort it out. It doesn’t.

Does anyone have any ideas? Is there a “Purge failed items” option or similar? I’d hoped that’s what Re-Scan might do for me.

Thanks,

Steve

DiskStation___Syncthing_-Mozilla_Firefox_and_Hackintosh___Syncthing-_Mozilla_Firefox1376×479 83.2 KB

Posts: 2

Participants: 2

Read full topic

@cedric wrote:

I don’t find any solution to this problem.

For information : syncthing v1.3.2 “Fermium Flea” (go1.13.4 linux-386) teamcity@build.syncthing.net 2019-11-24 08:33:58 UTC

“marc” is an actual user on a debian with no sudo rights. marc can launch syncthing as a user through a terminal.

Here is my service file : syncthing@marc.service :

[Unit]
Description=Syncthing - Open Source Continuous File Synchronization for %I
Documentation=man:syncthing(1)
After=network.target

[Service]
User=%I
ExecStart=/usr/local/bin/syncthing -no-browser -no-restart -logflags=0
Restart=on-failure
SuccessExitStatus=3 4
RestartForceExitStatus=3 4

# Hardening
ProtectSystem=full
PrivateTmp=true
SystemCallArchitectures=native
MemoryDenyWriteExecute=true
NoNewPrivileges=true

[Install]
WantedBy=multi-user.target

When starting it with “sudo systemctl start syncthing@marc.service”, i get the following logs from systemd :

déc. 09 21:55:41 syncdz systemd[1]: Started Syncthing - Open Source Continuous File Synchronization for marc.
déc. 09 21:55:41 syncdz systemd[1]: syncthing@marc.service: Main process exited, code=killed, status=31/SYS
déc. 09 21:55:41 syncdz systemd[1]: syncthing@marc.service: Failed with result 'signal'.
déc. 09 21:55:41 syncdz systemd[1]: syncthing@marc.service: Service RestartSec=100ms expired, scheduling restart.
déc. 09 21:55:41 syncdz systemd[1]: syncthing@marc.service: Scheduled restart job, restart counter is at 1.
déc. 09 21:55:41 syncdz systemd[1]: Stopped Syncthing - Open Source Continuous File Synchronization for marc.

and from systemctl status :

cedric@syncdz:~$ sudo systemctl status syncthing@marc.service
● syncthing@marc.service - Syncthing - Open Source Continuous File Synchronization for marc
Loaded: loaded (/etc/systemd/system/syncthing@marc.service; disabled; vendor preset: enabled)
Active: failed (Result: signal) since Mon 2019-12-09 22:26:16 CET; 13s ago
Docs: man:syncthing(1)
Process: 1259 ExecStart=/usr/local/bin/syncthing -no-browser -no-restart -logflags=0 (code=killed, signal=SYS)
Main PID: 1259 (code=killed, signal=SYS)

Posts: 4

Participants: 2

Read full topic

@Xeenych wrote:

I have a VDS, a home computer, a laptop and a computer at work with syncthing. Sometimes ST looses files. I add some new files to a working directory at home. Then I go my office and see, that the files are gone. I go at home again and see that some of my added files are gone at home too.

Posts: 3

Participants: 2

Read full topic

@Moisie wrote:

Hello:

Not a biggie - but it seems consistent on my setups here:

Running Syncthing 1.3.2 on a couple of Synology NAS units: I’ve got ~50 locally changed files on each device.

When I view the Locally Changed Files list, I get the first page of it ok - but when I attempt to go to subsequent pages (or increase the number of items per page), I get a Connection Error - Syncthing seems to be experiencing a problem… error.

It’s happening on both NAS units - so I suspect it’s not a temporary glitch.

Thanks.

Posts: 3

Participants: 2

Read full topic

@DonQuishot wrote:

Hi, my setup is as follows:

I have one always-on machine, a Raspberry Pi 3 B+, running Freedombox with Syncthing enabled. This server is accessible from the outside.

And then there are 4 mobile devices (2 laptops, 2 android smartphones) all syncing several folders with the little server, mostly pictures, where the pictures from phones are transferred to the laptops where they get processed and eventually archived.

The connection with one of the laptops keeps dropping. Only the server has Global Discovery enabled. When I restart the server, the transfer rate is high but drops after a few seconds to zero.

Sometimes in the log of that laptop it shows “External host has closed a connection”, but not always.

All machines, when at home, are behind the same firewall with the server.

What am I doing wrong here?

Posts: 10

Participants: 5

Read full topic

@cosas wrote:

When a change happens in my folder I will trigger a wake up action (WoL or other way) to the remote device so that sync starts (ST yet setup as a service)

On remote side I think I’d use a cron hourly to run a script that detects sync is done then shutdown the pc.

I read doc and found rest/db/completion but they say its expensive. There is also /rest/events?events=FolderCompletion but it may happens that no change is needed in the folder since last startup… so if IUC the event will not rise.

What’s the best way please. Thanks

Posts: 2

Participants: 2

Read full topic

@Totti wrote:

I moved Syncthing from Ubuntu to Docker on Ubuntu and somehow can#t get it to work:

Error shown in Web-UI: 2019-12-13 08:07:05: Error on folder “FOLDER1” (xxxxx-yyyyy): stat /datapool1/backup/PATH/FOLDER: permission denied

But I can stat that folder without Problems, when I exec onto the container as user syncthing: File: /datapool1/backup/PATH/FOLDER Size: 23 Blocks: 17 IO Block: 1536 directory Device: 2ch/44d Inode: 286875 Links: 22 Access: (0770/drwxrwx—) Uid: ( 1004/USERA) Gid: ( 1008/USERA)

I can also ls that directory and the .stfolder within, and cat the .stignore

Any ideas, what’s going wrong?

Thanks a lot in advance!

Posts: 1

Participants: 1

Read full topic

@alice wrote:

network bandwidth - what should it be?

Posts: 2

Participants: 2

Read full topic