Upgrade v0.14.16 breaks connection between Linux installations

Support
1

Hi all, I just updated my Linux servers to v0.14.16 the web console on all installations show all remote devices as Disconnected and there is no syncing taking place.

The sync folder was empty (if that makes a difference) while I connected various servers to each other for a project we are trialing.

I see no other reports of problems so I imagine it is Linux only. The upgrade was by apt update && apt upgrade I will look at downgrading to a previous version if there is no response in the next weeks. Let me know if this advisable.

Cheers and merry Xmas and happy holidays if you have them. ausinch

syslog: Dec 23 09:17:57 ZUR-Monitor systemd[1]: Started OpenBSD Secure Shell server. Dec 23 09:48:21 ZUR-Monitor syncthing[21726]: [AEGIH] INFO: Connection to KUALR7U-HEBWAUV-6RGYZJE-JJKIJS6-TFD7VJR-3RCHHM4-ZHAL6KE-NTB4SA5 closed: reading length: EOF Dec 23 09:48:37 ZUR-Monitor syncthing[21726]: [AEGIH] INFO: Connection to UJ5JTPU-TALSSIK-AWQ27LU-HUKDNNF-VQZO7PZ-2EL2HM4-F6Z5IYE-HYLUBQL closed: reading length: EOF Dec 23 09:48:39 ZUR-Monitor syncthing[21726]: [AEGIH] INFO: Connection to A6LND3V-KO7CHGY-CAURY3L-2P5TQSI-3DZUIRK-3MKUAFY-LVS6HWQ-K2DK7QK closed: reading length: EOF Dec 23 10:17:01 ZUR-Monitor CRON[806]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Dec 23 10:53:51 ZUR-Monitor syncthing[21726]: [AEGIH] INFO: Restarting Dec 23 10:53:51 ZUR-Monitor syncthing[21726]: [AEGIH] INFO: Exiting Dec 23 10:53:52 ZUR-Monitor systemd[1]: syncthing@syncthing.service holdoff time over, scheduling restart. Dec 23 10:53:52 ZUR-Monitor systemd[1]: Cannot add dependency job for unit syncthing-inotify@syncthing.service, ignoring: Unit syncthing-inotify@syncthing.service failed to load: No such file or directory. Dec 23 10:53:52 ZUR-Monitor systemd[1]: Stopping Syncthing - Open Source Continuous File Synchronization for syncthing… Dec 23 10:53:52 ZUR-Monitor systemd[1]: Starting Syncthing - Open Source Continuous File Synchronization for syncthing… Dec 23 10:53:52 ZUR-Monitor systemd[1]: Started Syncthing - Open Source Continuous File Synchronization for syncthing. Dec 23 10:53:52 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: syncthing v0.14.16 “Dysprosium Dragonfly” (go1.8beta2 linux-amd64) jenkins@build.syncthing.net 2016-12-21 18:46:28 UTC Dec 23 10:53:52 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: My ID: AEGIHUD-TNXBI56-QZR46IP-3J2A5M2-4YVZ3LJ-5UCK3A5-GC247V2-3UKFOQP Dec 23 10:53:52 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Single thread hash performance is 187 MB/s using minio/sha256-simd (138 MB/s using crypto/sha256). Dec 23 10:53:56 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Ready to synchronize eaa3t-nctc9 (readwrite) Dec 23 10:53:56 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Ready to synchronize zcmgw-xdny7 (readwrite) Dec 23 10:53:56 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Ready to synchronize xafpi-rdit6 (readwrite) Dec 23 10:53:56 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: TCP listener ([::]:22000) starting Dec 23 10:53:56 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Device X5UHEAA-OZEU2TP-ROPG4MD-2F32PNL-7QGUY3Z-5ZMTJ53-CM5YJMW-7MUUFQ7 is “MUN-Monitor” at [tcp://mun-monitor] Dec 23 10:53:56 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Device AEGIHUD-TNXBI56-QZR46IP-3J2A5M2-4YVZ3LJ-5UCK3A5-GC247V2-3UKFOQP is “ZUR-Monitor” at [dynamic] Dec 23 10:53:56 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Device A6LND3V-KO7CHGY-CAURY3L-2P5TQSI-3DZUIRK-3MKUAFY-LVS6HWQ-K2DK7QK is “PAR-Monitor” at [tcp://par-monitor] Dec 23 10:53:56 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Device KUALR7U-HEBWAUV-6RGYZJE-JJKIJS6-TFD7VJR-3RCHHM4-ZHAL6KE-NTB4SA5 is “NJ-Monitor” at [tcp://nj-monitor] Dec 23 10:53:56 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Device UJ5JTPU-TALSSIK-AWQ27LU-HUKDNNF-VQZO7PZ-2EL2HM4-F6Z5IYE-HYLUBQL is “LON-Monitor” at [tcp://lon-monitor] Dec 23 10:53:57 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: GUI and API listening on [::]:8384 Dec 23 10:53:57 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Access the GUI via the following URL: http://127.0.0.1:8384/ Dec 23 10:53:57 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Completed initial scan (rw) of folder xafpi-rdit6 Dec 23 10:53:57 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Completed initial scan (rw) of folder zcmgw-xdny7 Dec 23 10:54:16 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Completed initial scan (rw) of folder eaa3t-nctc9 Dec 23 11:17:01 ZUR-Monitor CRON[1347]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) /var

0.14.16_error_1.png565×615 26.9 KB

2

Which version did you upgrade from?

There was a regression introduced in 0.14.14 (I think) which made it mandatory to specify a port for manually entered remote device addresses.

There was a patch 5 days ago but it seams that didn’t make it into the newest release:

According to your log, you have entered the addresses manually without port.

Dec 23 10:53:56 ZUR-Monitor syncthing[1114]: [AEGIH] INFO: Device X5UHEAA-OZEU2TP-ROPG4MD-2F32PNL-7QGUY3Z-5ZMTJ53-CM5YJMW-7MUUFQ7 is "MUN-Monitor" at [tcp://mun-monitor]

Try adding the default port :22000 to the addresses of you remote devices.

1 Like
3

In my case I have noticed a similar problem probably related with the same issue. after upgrading from 0.14.15 to 0.14.16 on 4 or 5 machines, the two that are a linux raspberry has got some red text on some of the folders as red ‘out of sync’.

When I click on the out of sync items, the unsynced files appeared as with the status ‘parent not a directory’.

About the :22000 solution, I’m not sure where should I enter that, because if I go to:

win81_machine_A->RemoteDevicesList->Edit_linux_machine_A on Adresses I have ‘dynamic’, not a tcp or port forced.

Same on: Linux_machine_A->RemoteDevicesList->Edit_win81_machine_A on address I also have ‘dynamic’ there.

4

I’m not sure why any of you are looking at the port number issue. :slight_smile:

@ausinch Connection to ... closed: reading length: EOF means the other side hung up. The real error is probably logged there.

@user512 parent not a directory means there is some part of the directory structure leading up to the mentioned file that is missing or a symlink, which is no longer acceptable even though it may have passed muster before. Please take a look at what exactly is at the mentioned path. There is also no real similarity to the original poster’s error, other than them both happening in late December, from what I can tell. :slight_smile:

5

First thing I did was look at the mentioned path. The out of sync items are inside a subfolder which is inside a subfolder of the main synced folder like:

Main_folder/1st_subfolder/failing_2nd_subfolder/26 files

Everything is synced, even files inside 1st subfolder except the files inside the 2nd subfolder which are ‘out of sync’

I knew about the problems with symlinks in previous updates, but non of this files or directories are symlinks. Just real files.

I though the problem could be related because it happens to me right after upgrading to 0.14.16 and only on linux installations as the thread opener mention. That’s why I answer on this thread.

I create a new folder inside ‘1st subfolder’ entering with ftp on the linux machine and moved all 26 files to the new destination, an deleted the folder with problems. New folder is red and out of sync too.

Don’t worry I will wait and see if it’s a particular problem of my config or if there is any other people affected by the issue, don¡t want to fill this thread with a not related problem. Thanks.

6

Hi,

I have similar problem since v0.14.16 upgrade.

I have two computers. The first under Ubuntu 12.04 and syncthing 0.14.15 The second with Xubuntu 16.04 and syncthing 0.14.16

On each machine, the shared folder is seen as synchronized On each machine, the other machine is seen as disconnected

On Ubuntu 12.04 (0.14.15) no error reported On Xubuntu 16.04 (0-14.16) these errors are reported:

2016-12-24 14:47:21: Connecting to L4ZFF3A-XWIJEZ6-WJUFMEY-GTBVCQE-2NV6ZAD-SSAP5YF-WQ3PKMF-2TDBJAI (192.168.1.15:8384): the remote device speaks an unknown (newer?) version of the protocol

2016-12-24 15:02:53: Connecting to L4ZFF3A-XWIJEZ6-WJUFMEY-GTBVCQE-2NV6ZAD-SSAP5YF-WQ3PKMF-2TDBJAI (192.168.1.15:8384): the remote device speaks an unknown (newer?) version of the protocol

2016-12-24 15:17:53: Connecting to L4ZFF3A-XWIJEZ6-WJUFMEY-GTBVCQE-2NV6ZAD-SSAP5YF-WQ3PKMF-2TDBJAI (192.168.1.15:8384): the remote device speaks an unknown (newer?) version of the protocol

I have tried to uninstall 0.1.14.16 and reinstalled 0.14.15 thinking it will solve my problem, but probably the config files has been modified, and the errors are the same. :disappointed:

I can I solve my problem ?

Thanks A+

7

You entered the wrong port.

You entered the port for the web ui, not the sync port (which is normally 22000).

8

Are you talking about my problem between my machines under Ubuntu 12.04 and Xubuntu 16.04 ?

This was working before the upgrade, and I don’t modify nothing …

A+

9

You must have as otherwise it would have never worked.

10

I did modify nothing, and it worked well.

It’s 0.14.16 which break something.

Where can I solve the problem ? Which file to edit ?

A+

11

I have made harcopies of the syncthing web interface for the two computers, and I found a difference:

I notice that on Ubuntu hardcopy, Dell-DM061 address has no port tcp://192.168.1.13 instead of tcp://192.168.1.13:8384

Could it be the reason ?

A+

12

as mentioned before tcp://192.168.1.13:8384 is wrong as 8384 is the default gui port, tcp://192.168.1.13 without port worked before but is broken in v0.14.16 as @wweich mentioned 2 days ago, add :22000 (or replace :8384 depending on what you have now)

Both also seem to know the correct one, probably from local discovery, so I wonder why they do not connect even with wrong settings…

13

Well, I know that 8384 is the web port, but I don’t know where to correct the port. On Ubuntu 12.04 or Xubuntu 16.04 ? And in which config file ?

A+

14

ok, I found where to change:

Other device => edit => replace the port 8384 by 22000

But I notice that on Ubuntu 12.04 machine the port 22000 was not in the address, and the port which has been used is : 53486

Is-it important, and have I to modify it to 22000 ?

But the more important is that it is now syncing :yum: Thanks A+

15

I just got back to the office and noted that v0.14.17 is out. So without trying to fix v0.14.16 i just ran the upgrade on all servers. The issue is no longer present. All servers and folders have the status of “Up to Date”

Many thanks for the fix Syncthing team. :+1: This project rox

1 Like
16

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.