Failed to acquire lock

mexsudo · August 20, 2025, 9:02pm

any ideas? I did reinstall syncthing, no joy using Debian Linux

===============

peter@z840-1:~$ syncthing [start] 2025/08/20 13:59:05 INFO: syncthing v1.29.5 “Gold Grasshopper” (go1.24.2 linux-amd64) debian@debian 2025-04-20 21:21:27 UTC [start] 2025/08/20 13:59:05 WARNING: Failed to acquire lock: open /home/peter/.local/state/syncthing/syncthing.lock: no such file or directory [monitor] 2025/08/20 13:59:05 INFO: Syncthing exited: exit status 1 [start] 2025/08/20 13:59:06 INFO: syncthing v1.29.5 “Gold Grasshopper” (go1.24.2 linux-amd64) debian@debian 2025-04-20 21:21:27 UTC [start] 2025/08/20 13:59:06 WARNING: Failed to acquire lock: open /home/peter/.local/state/syncthing/syncthing.lock: no such file or directory [monitor] 2025/08/20 13:59:06 INFO: Syncthing exited: exit status 1 [start] 2025/08/20 13:59:07 INFO: syncthing v1.29.5 “Gold Grasshopper” (go1.24.2 linux-amd64) debian@debian 2025-04-20 21:21:27 UTC [start] 2025/08/20 13:59:07 WARNING: Failed to acquire lock: open /home/peter/.local/state/syncthing/syncthing.lock: no such file or directory [monitor] 2025/08/20 13:59:07 INFO: Syncthing exited: exit status 1 [start] 2025/08/20 13:59:08 INFO: syncthing v1.29.5 “Gold Grasshopper” (go1.24.2 linux-amd64) debian@debian 2025-04-20 21:21:27 UTC [start] 2025/08/20 13:59:08 WARNING: Failed to acquire lock: open /home/peter/.local/state/syncthing/syncthing.lock: no such file or directory [monitor] 2025/08/20 13:59:08 INFO: Syncthing exited: exit status 1 [monitor] 2025/08/20 13:59:09 WARNING: 4 restarts in 4.12418844s; not retrying further peter@z840-1:~$

mexsudo · August 20, 2025, 9:13pm

Login failed, see Syncthing logs for details.

mexsudo · August 20, 2025, 9:16pm

/home/peter/.config/syncthing/syncthing.log

starting at line 10584:

[MBF5Y] 2025/08/20 11:27:17 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down [MBF5Y] 2025/08/20 11:27:17 INFO: Lost primary connection to 7EP4AEC at 192.168.1.70:22000-192.168.1.80:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-62TFGJHI7E7G4Q99DJIHTUCJ2A: Syncthing is being stopped (0 remain) [MBF5Y] 2025/08/20 11:27:17 INFO: Connection to 7EP4AEC at 192.168.1.70:22000-192.168.1.80:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-62TFGJHI7E7G4Q99DJIHTUCJ2A closed: Syncthing is being stopped [MBF5Y] 2025/08/20 11:27:17 INFO: Lost primary connection to PDJKYGZ at [fe80::ed2c:d0ca:4a9:689f%eno1]:22000-[fe80::1260:4bff:fe5c:5be6%eno1]:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-62TFGJHHV7K6KU5H9ECC8ROP7Q: Syncthing is being stopped (0 remain) [MBF5Y] 2025/08/20 11:27:17 INFO: Connection to PDJKYGZ at [fe80::ed2c:d0ca:4a9:689f%eno1]:22000-[fe80::1260:4bff:fe5c:5be6%eno1]:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-62TFGJHHV7K6KU5H9ECC8ROP7Q closed: Syncthing is being stopped [MBF5Y] 2025/08/20 11:27:17 INFO: Lost primary connection to 5GIHYCJ at [2806:290:c80a:c7b4:e368:c3f4:6840:4991]:22000-[2806:290:c80a:c7b4:d88d:a699:2471:3684]:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-62TFGJHI5T41AI3JKG6O0OT48A: Syncthing is being stopped (0 remain) [MBF5Y] 2025/08/20 11:27:17 INFO: Connection to 5GIHYCJ at [2806:290:c80a:c7b4:e368:c3f4:6840:4991]:22000-[2806:290:c80a:c7b4:d88d:a699:2471:3684]:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-62TFGJHI5T41AI3JKG6O0OT48A closed: Syncthing is being stopped [MBF5Y] 2025/08/20 11:27:17 INFO: Lost primary connection to ERQIOVL at [fe80::ed2c:d0ca:4a9:689f%eno1]:22000-[fe80::42b0:34ff:fe1e:d462%eno1]:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-62TFGJHHJACPGI0AGGNMQ1OLPK: Syncthing is being stopped (0 remain) [MBF5Y] 2025/08/20 11:27:17 INFO: Connection to ERQIOVL at [fe80::ed2c:d0ca:4a9:689f%eno1]:22000-[fe80::42b0:34ff:fe1e:d462%eno1]:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-62TFGJHHJACPGI0AGGNMQ1OLPK closed: Syncthing is being stopped [MBF5Y] 2025/08/20 11:27:17 INFO: Lost primary connection to NCKRCV3 at [fe80::ed2c:d0ca:4a9:689f%eno1]:22000-[fe80::ca94:2ff:fe81:1a9f%eno1]:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-62TFGJIEBMCF826ANUJVO4L2RG: Syncthing is being stopped (0 remain) [MBF5Y] 2025/08/20 11:27:17 INFO: Connection to NCKRCV3 at [fe80::ed2c:d0ca:4a9:689f%eno1]:22000-[fe80::ca94:2ff:fe81:1a9f%eno1]:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-62TFGJIEBMCF826ANUJVO4L2RG closed: Syncthing is being stopped [MBF5Y] 2025/08/20 11:27:17 INFO: Lost primary connection to 2RZZ2AZ at 192.168.1.70:22000-192.168.1.66:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-62TFGJHLM9RM6DFQD9CK4QT32M: Syncthing is being stopped (0 remain) [MBF5Y] 2025/08/20 11:27:17 INFO: Connection to 2RZZ2AZ at 192.168.1.70:22000-192.168.1.66:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-62TFGJHLM9RM6DFQD9CK4QT32M closed: Syncthing is being stopped [MBF5Y] 2025/08/20 11:27:17 INFO: TCP listener ([::]:22000) shutting down [MBF5Y] 2025/08/20 11:27:18 INFO: Exiting

calmh · August 20, 2025, 9:26pm

There’s a lot to unpack here, so a few points/pointers;

The version packaged in Debian is buggy. You appear to have found a working one, good.
By default there is no authentication for a new install. Perhaps you have an old install with credentials from before?
By default Syncthing doesn’t log to the file you mentioned, so if you’re doing something special to launch Syncthing it might be relevant to explain that.
The log snipped doesn’t show whatever was the login problem, which presumably happened earlier.

mexsudo · August 20, 2025, 10:39pm

I use the packaged “start syncthing” launcher: /usr/bin/syncthing serve --no-browser --logfile=default

perhaps that log got replaced with the reinstall. I will look at the others…

mexsudo · August 20, 2025, 10:48pm

where are logs normally kept?

calmh · August 21, 2025, 8:53am

Oh nice, I didn’t know the launcher did that. All good, then.

mexsudo · August 21, 2025, 1:12pm

Thursday, August 21 2025 05:57 AM well, error message said it failed looking for specific folders and files… so

create folders /home/peter/.local/state /home/peter/.local/state/syncthing

create empty files: /home/peter/.local/state/syncthing/syncthing.lock /home/peter/.local/state/syncthing/syncthing.log

run $ syncthing serve --no-browser --logfile=default

syncthing.log:

[start] 2025/08/21 05:52:57 INFO: syncthing v1.29.5 “Gold Grasshopper” (go1.24.2 linux-amd64) debian@debian 2025-04-20 21:21:27 UTC [MBF5Y] 2025/08/21 05:52:57 INFO: My ID: MBF5YOV-ACVTPGF-UBUQ5LG-VSSZIV4-6O42K36-BENOB3L-FPSSTKC-2U677AZ [MBF5Y] 2025/08/21 05:52:58 INFO: Hashing performance is 116.90 MB/s [MBF5Y] 2025/08/21 05:52:58 INFO: Running database migration 14… [MBF5Y] 2025/08/21 05:52:58 INFO: Running database migration 16… [MBF5Y] 2025/08/21 05:52:58 INFO: Running database migration 17… [MBF5Y] 2025/08/21 05:52:58 INFO: Running database migration 19… [MBF5Y] 2025/08/21 05:52:58 INFO: Running database migration 20… [MBF5Y] 2025/08/21 05:52:58 INFO: Compacting database after migration… [MBF5Y] 2025/08/21 05:52:58 INFO: Overall send rate is unlimited, receive rate is unlimited [MBF5Y] 2025/08/21 05:52:58 INFO: No stored folder metadata for “3ymum-xi7xn”; recalculating [MBF5Y] 2025/08/21 05:52:58 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting 2025/08/21 05:52:58 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 7168 kiB, got: 416 kiB). See UDP Buffer Sizes · quic-go/quic-go Wiki · GitHub for details. [MBF5Y] 2025/08/21 05:52:58 INFO: Using discovery mechanism: global discovery server https://discovery-lookup.syncthing.net/v2/?noannounce

etc

It seems to be rebuilding the database from scratch…

mexsudo · August 21, 2025, 1:16pm

mexsudo · August 21, 2025, 6:48pm

BTW: I now find the log in

/home/peter/.local/state/syncthing/syncthing.log

system · September 20, 2025, 6:49pm

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