Hi, all. I serve an Internet cafe with 40 computers. I decided to use Synching to update online-games. Is about 12 folders and 300 GB of information on each machine. Prompt optimal configuration of Synching for these options: -trafficClass -urAccepted -weakHashSelectionMethod -weakHashThresholdPct
My hardware: Server: 2 Xeon 5130, 2TB Sata II, 1Gb Lan Workstations: 30 Core i5 + 10 Core Quad E8400 LAN 100 MB
Defaults are optimal
Syncthing console show next rows: [MIZDS] 2017/02/27 19:00:32.183315 service.go:390: DEBUG: dial DI774TI tcp://192.168.2.129:22000 [MIZDS] 2017/02/27 19:00:32.245318 tcp_dial.go:49: DEBUG: failed to set traffic class: operation not supported [MIZDS] 2017/02/27 19:00:33.350380 service.go:341: DEBUG: Reconnect loop for FPFVON3 [MIZDS] 2017/02/27 19:00:33.351382 service.go:390: DEBUG: dial FPFVON3 tcp://192.168.2.139:22000 [MIZDS] 2017/02/27 19:00:33.447385 service.go:281: INFO: Established secure connection to DI774TI at 192.168.2.99:63957-192.168.2.129:22000 (tcp-client) (TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384) [MIZDS] 2017/02/27 19:00:33.448386 model.go:1380: INFO: Device DI774TI client is “syncthing v0.14.23” named “k29” [MIZDS] 2017/02/27 19:00:33.458386 tcp_dial.go:49: DEBUG: failed to set traffic class: operation not supported [MIZDS] 2017/02/27 19:01:25.353304 model.go:1095: INFO: Connection to VFTCXDR closed: read timeout [MIZDS] 2017/02/27 19:01:36.851950 service.go:211: INFO: Failed to exchange Hello messages with FPFVON3 (192.168.2.139:22000): write tcp 192.168.2.99:63958->192.168.2.139:22000: wsasend: An existing connection was forcibly closed by the remote host. [MIZDS] 2017/02/27 19:01:36.855950 service.go:341: DEBUG: Reconnect loop for GLGGDVS [MIZDS] 2017/02/27 19:01:36.855950 service.go:390: DEBUG: dial GLGGDVS tcp://192.168.2.127:22000 [MIZDS] 2017/02/27 19:01:37.006959 tcp_dial.go:49: DEBUG: failed to set traffic class: operation not supported [MIZDS] 2017/02/27 19:01:37.121965 service.go:341: DEBUG: Reconnect loop for HDF5SWB [MIZDS] 2017/02/27 19:01:37.122965 service.go:390: DEBUG: dial HDF5SWB tcp://192.168.2.118:22000 [MIZDS] 2017/02/27 19:01:37.158967 service.go:281: INFO: Established secure connection to GLGGDVS at 192.168.2.99:63961-192.168.2.127:22000 (tcp-client) (TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384) [MIZDS] 2017/02/27 19:01:37.158967 model.go:1380: INFO: Device GLGGDVS client is “syncthing v0.14.23” named “k27” [MIZDS] 2017/02/27 19:01:37.163967 tcp_dial.go:49: DEBUG: failed to set traffic class: operation not supported [MIZDS] 2017/02/27 19:02:33.860155 service.go:211: INFO: Failed to exchange Hello messages with HDF5SWB (192.168.2.118:22000): write tcp 192.168.2.99:63962->192.168.2.118:22000: wsasend: An existing connection was forcibly closed by the remote host. [MIZDS] 2017/02/27 19:02:33.862155 service.go:341: DEBUG: Reconnect loop for HFZIDIF [MIZDS] 2017/02/27 19:02:33.865155 service.go:390: DEBUG: dial HFZIDIF tcp://192.168.2.137:22000 [MIZDS] 2017/02/27 19:02:33.866155 tcp_dial.go:49: DEBUG: failed to set traffic class: operation not supported [MIZDS] 2017/02/27 19:02:34.965216 service.go:341: DEBUG: Reconnect loop for II5NL7X [MIZDS] 2017/02/27 19:02:34.965216 service.go:390: DEBUG: dial II5NL7X tcp://192.168.2.107:22000 [MIZDS] 2017/02/27 19:02:34.966218 service.go:281: INFO: Established secure connection to HFZIDIF at 192.168.2.99:63966-192.168.2.137:22000 (tcp-client) (TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384) [MIZDS] 2017/02/27 19:02:34.966218 model.go:1380: INFO: Device HFZIDIF client is “syncthing v0.14.23” named “k37” [MIZDS] 2017/02/27 19:02:34.985217 tcp_dial.go:49: DEBUG: failed to set traffic class: operation not supported
what is mean “failed to set traffic class” and “Failed to exchange Hello messages”?
It means that your kernel does not support setting traffic class, if you want to know what it is, google it. Exchange hello probably means you A connect to B while B connected to A and one of the connections got axed, as we don’t need two, unless you actually have issues connecting…
Sorry, but you say what defaults are optimal. In my configuration traffic class is 0. It is a default. You can please a few words about the traffic class. on Google I found no direct definition. In reality, it is necessary to introduce Syncthing in my work, but I do not have such deep knowledge in these areas. The general scheme I realized I would ask you udilyty me a few minutes of your time. Thank you in advance!
It’s an advanced setting that people should not care about, unless you know what it means. The first link on Google explains what it is perfectly. The actual usable values can be seen in the DSCP value table, but I am pretty sure there is pretty much zero reason you need to use anything else than the default (especially given your kernel does not support it, so no value has any meaning at all)
Ok. Thanks for reply. My Syncthing kernel or what kernel you mean?
another question: Syncthing synchronizes folders to 92-97% and stops. log file that’s on both sides: On a side A (readonly)
[MIZDS] 19:54:20 INFO: Connection to CSWZVHZ closed: reading length: read tcp 192.168.2.99:49816->192.168.2.134:22000: wsarecv: An existing connection was forcibly closed by the remote host. [MIZDS] 19:55:07 INFO: Established secure connection to CSWZVHZ at 192.168.2.99:50343-192.168.2.134:22000 (tcp-client) (TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384) [MIZDS] 19:55:07 INFO: Device CSWZVHZ client is “syncthing v0.14.23” named “k34” [MIZDS] 19:57:58 INFO: Connection to SLYJNKO closed: reading length: read tcp 192.168.2.99:49809->192.168.2.102:22000: wsarecv: An existing connection was forcibly closed by the remote host. [MIZDS] 19:58:07 INFO: Established secure connection to GLGGDVS at 192.168.2.99:50393-192.168.2.127:22000 (tcp-client) (TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384) [MIZDS] 19:58:07 INFO: Device GLGGDVS client is “syncthing v0.14.23” named “k27” [MIZDS] 20:22:17 INFO: Connection to FPFVON3 closed: reading length: read tcp 192.168.2.99:49801->192.168.2.139:22000: wsarecv: An existing connection was forcibly closed by the remote host. [MIZDS] 20:24:19 INFO: Established secure connection to FPFVON3 at 192.168.2.99:50475-192.168.2.139:22000 (tcp-client) (TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384) [MIZDS] 20:24:19 INFO: Device FPFVON3 client is “syncthing v0.14.23” named “k39” [MIZDS] 20:29:19 INFO: Established secure connection to SLYJNKO at 192.168.2.99:50532-192.168.2.102:22000 (tcp-client) (TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384) [MIZDS] 20:29:19 INFO: Device SLYJNKO client is “syncthing v0.14.23” named “k02” [MIZDS] 20:35:31 INFO: Connection to VRXYTSG closed: reading length: read tcp 192.168.2.99:49820->192.168.2.114:22000: wsarecv: An existing connection was forcibly closed by the remote host. [MIZDS] 20:36:19 INFO: Established secure connection to VRXYTSG at 192.168.2.99:50535-192.168.2.114:22000 (tcp-client) (TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384) [MIZDS] 20:36:19 INFO: Device VRXYTSG client is “syncthing v0.14.23” named “k14” [MIZDS] 21:32:13 INFO: Connection to VRXYTSG closed: reading length: read tcp 192.168.2.99:50535->192.168.2.114:22000: wsarecv: An existing connection was forcibly closed by the remote host. [MIZDS] 21:33:21 INFO: Established secure connection to VRXYTSG at 192.168.2.99:50870-192.168.2.114:22000 (tcp-client) (TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384) [MIZDS] 21:33:21 INFO: Device VRXYTSG client is “syncthing v0.14.23” named “k14”
On a side B (readwrite)
[SLYJN] 20:29:18 INFO: Completed initial scan (rw) of “War Thunder” (duydy-jcoyk) [SLYJN] 20:29:22 INFO: Established secure connection to MIZDSYR at 192.168.2.102:22000-192.168.2.99:50532 (tcp-server) (TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384) [SLYJN] 20:29:22 INFO: Device MIZDSYR client is “syncthing v0.14.23” named “Report” [SLYJN] 20:29:58 INFO: Completed initial scan (rw) of “World of Warplanes” (wv9vk-xpdbd) [SLYJN] 20:30:38 INFO: Completed initial scan (rw) of “World_of_Warships” (tqdxg-azkd9) [SLYJN] 20:31:09 INFO: Completed initial scan (rw) of “World of Tanks” (jzz4p-xecjr) [SLYJN] 20:32:04 INFO: Completed initial scan (rw) of “League of Legends” (mvreo-34cor) [SLYJN] 20:52:02 INFO: Enabled debug data for “connections” [SLYJN] 20:53:01 DEBUG: Reconnect loop [SLYJN] 20:53:01 DEBUG: sleep until next dial 1m0s [SLYJN] 20:54:01 DEBUG: Reconnect loop [SLYJN] 20:54:01 DEBUG: sleep until next dial 1m0s [SLYJN] 20:55:01 DEBUG: Reconnect loop [SLYJN] 20:55:01 DEBUG: sleep until next dial 1m0s [SLYJN] 20:56:09 DEBUG: Reconnect loop [SLYJN] 20:56:09 DEBUG: sleep until next dial 1m0s [SLYJN] 20:57:09 DEBUG: Reconnect loop [SLYJN] 20:57:09 DEBUG: sleep until next dial 1m0s [SLYJN] 20:58:11 DEBUG: Reconnect loop [SLYJN] 20:58:11 DEBUG: sleep until next dial 1m0s [SLYJN] 20:59:39 DEBUG: Reconnect loop [SLYJN] 20:59:39 DEBUG: sleep until next dial 1m0s [SLYJN] 21:00:49 DEBUG: Reconnect loop
[quote=“dobermannlast, post:8, topic:9329”] An existing connection was forcibly closed by the remote host. [/quote] what caused forcibly close connection?
Firewall, network error, or Syncthing itself dropping the connection for some reason that would be logged on the other side.
(“forcibly closed” is Windows-speak for connection reset, afaik)
Thanks. Let me ask a few questions: Templates ignoring must be only in master folder or on both sides?
When I try syhnronize two folders, side B (read-write) in the log file I see an attempt to remove a directory (perhaps an attempt to rewrite?) is not going well. The folderd and files are identical on both sides and not occupied by foreign processes. What is the reason?
[XZDWS] 10:16:20 INFO: Puller (folder “mvreo-34cor”, dir “RADS\solutions\lol_game_client_sln\releases\0.0.1.163\deploy”): delete: remove \?\D:\Games\League of Legends\RADS\solutions\lol_game_client_sln\releases\0.0.1.163\deploy: The directory is not empty. [XZDWS] 10:16:20 INFO: Folder “mvreo-34cor” isn’t making progress. Pausing puller for 1m0s.
Which ceckboxes from Logging+STTRACE tab i have to enable to see why syncthing process stopping on a ninety with something percent?
General question: Folder synchronization conflict occurs files to B side (readwrite). On the screenshot we see file “pkg_Russian.ver” modified 14:18:27 with original size of 9
bytes and the same file is modified in 14:20:52 with a size of 10 bytes. In the master folder on a A side, present file “pkg_Russian.ver” modified 14:18:27
with the size in 10 bytes. Where Syncthing takes file is modified 14:20:52 in 10 bytes?
The error means you have some ignored files left over in the directory preventing to remove the folder. If you are fine for the files to be deleted by syncthing, read the ignore section of the docs again about the different prefixes.
Ignores ideally should be the the same on all sides.
Thanks. What about last question (with the screenshot)?
There is no way to know where the conflict came from yet.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
