devices continuously disconnecting

Hi, I’m having an issue that I can’t figure out. I have 1.6.1 installed on a machine with mint and one with win 7. Things were working in the past. Now the two devices continue to try to connect and then get disconnected after a couple seconds. Ive attached a screenshot of the gui on the windows machine. Seems network related, however in the console on the same machine I get the message:

info: connection to … closed error: index update: arbitrary.file: file with empty block list

file changes as i pause different folders.

I’m on the same network and I’ve allowed the program in the firewall on each machine.

Please let me know what I can do, or what other info you might need. Thank you very much

My guess is that the other side is a very old version and you should upgrade it.

Interesting. I think you are right, except I did that and nothing changed.

Earlier today my linux machine had a very old version - 0.14 I think. I followed the instructions on the site, added the PGP keys, and updated - now I have 1.6.1 on both machines.

Still no sign of anything having changed.

Thanks again

Except now that both sides are on 1.6.1 I’m actually interested in log messages if they talk about “file with empty block list” and you can provide some log details. :slight_smile:

(I’ve anonymized folder ID’s below in case that matters)

Here is the log from the win machine (the file will change if I unpause other folders):

2020-06-17 11:12:03 Established secure connection to XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX at[](
2020-06-17 11:12:03 Device XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX client is "syncthing v1.6.1" named "kavon-len-lin" at[](
2020-06-17 11:12:04 Connection to XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX at[]( closed: protocol error: index update: "Books/Fundamentals of Biological Wastewater Treatment.pdf": file with empty block list

Here is the log from the linux machine that was recently updated to 1.6.1:

2020-06-17 11:08:02 Established secure connection to YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY at[](
2020-06-17 11:08:02 Replacing old connection[]( with[]( for YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY
2020-06-17 11:08:02 Connection to YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY at[]( closed: replacing connection
2020-06-17 11:08:02 Device YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY client is "syncthing v1.6.1" named "kavon-PCasus" at[](
2020-06-17 11:08:02 Failed to exchange Hello messages with YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY-YYYYYYY at [fe80::620b:42a9:3510:e01%wlp4s0]:22000-[fe80::35dd:791:62a6:2661%wlp4s0]:59725/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256: write tcp [fe80::620b:42a9:3510:e01%wlp4s0]:22000->[fe80::35dd:791:62a6:2661%wlp4s0]:59725: write: connection reset by peer

It looks like it’s still running an old version.

I guess it might be leftovers from the old version. You could try to remove the folder on the device that had the old version, restart and then readd it back.

I can confirm both machines have 1.6.1.

Removing the folder sounds like it would probably work given all the feedback in this thread. I will try that later today.

However, I’m just curious if you have any ideas on other ways? I really like this software and this project, but the major downside for me has been the need to remove folders and rebuild them whenever an issue comes up. It’s like blowing on the cartridge or rebooting windows - not the most elegant, and in my case relatively time intensive because I have about 8 folders that sync about 1.5 tb.

Any thoughts appreciated. I will update when/if redoing folders works.

If you can zip up and share the index database from the lowermost machine I can take a look and see if there’s a visible root cause. Otherwise this “file with empty block list” is just something that Can’t Happen (and doesn’t, as far as I can remember seeing, outside of a couple of the 1.4.0 release candidates that you weren’t running).

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