Installation gets stuck

Support
1

I wanted to install Syncthing on my RasppberryPi (operating system Ubuntu Server) and followed the installation steps from: https://apt.syncthing.net/. I’m yet not sure if the installation was actually succecssful.

Basically, the commands from the steps above were all executed but after that, when I type in syncthing, it gets stuck on the wy. Below is the log (note: before the last 4 log outputs, I manually aborted the procedure). Can anyone help me on what’s happened here?

pi@raspberrypi:~$ syncthing -verbose
[start] 2022/12/07 10:32:28 INFO: syncthing v1.22.2 "Fermium Flea" (go1.19.2 linux-arm) teamcity@build.syncthing.net 2022-11-28 03:48:37 UTC
[BOEUZ] 2022/12/07 10:32:29 INFO: My ID: BOEUZYY-54BD62B-KSVFTEW-AWMRX6V-KWINPHR-UJSFJJC-CKWQXDJ-LQ6KIAQ
[BOEUZ] 2022/12/07 10:32:30 INFO: Single thread SHA256 performance is 53 MB/s using minio/sha256-simd (53 MB/s using crypto/sha256).
[BOEUZ] 2022/12/07 10:32:30 VERBOSE: Starting up (/home/pi/.config/syncthing)
[BOEUZ] 2022/12/07 10:32:31 INFO: Hashing performance is 47.83 MB/s
[BOEUZ] 2022/12/07 10:32:31 INFO: Overall send rate is unlimited, receive rate is unlimited
[BOEUZ] 2022/12/07 10:32:31 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[BOEUZ] 2022/12/07 10:32:31 INFO: QUIC listener ([::]:22000) starting
[BOEUZ] 2022/12/07 10:32:31 VERBOSE: Listen address quic://0.0.0.0:22000 resolution has changed: lan addresses: [quic://0.0.0.0:22000 quic://192.168.1.5:22000 quic://10.83.3.1:22000] wan addresses: [quic://0.0.0.0:22000]
[BOEUZ] 2022/12/07 10:32:31 INFO: TCP listener ([::]:22000) starting
[BOEUZ] 2022/12/07 10:32:31 VERBOSE: Listen address tcp://0.0.0.0:22000 resolution has changed: lan addresses: [tcp://0.0.0.0:22000 tcp://192.168.1.5:22000 tcp://10.83.3.1:22000] wan addresses: [tcp://0.0.0.0:0 tcp://0.0.0.0:22000]
[BOEUZ] 2022/12/07 10:32:31 INFO: Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[BOEUZ] 2022/12/07 10:32:31 INFO: Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[BOEUZ] 2022/12/07 10:32:31 INFO: Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[BOEUZ] 2022/12/07 10:32:31 INFO: Using discovery mechanism: IPv4 local broadcast discovery on port 21027
[BOEUZ] 2022/12/07 10:32:31 INFO: Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
[BOEUZ] 2022/12/07 10:32:31 INFO: Ready to synchronize "Default Folder" (default) (sendreceive)
[BOEUZ] 2022/12/07 10:32:31 INFO: GUI and API listening on 127.0.0.1:8384
[BOEUZ] 2022/12/07 10:32:31 INFO: Access the GUI via the following URL: http://127.0.0.1:8384/
[BOEUZ] 2022/12/07 10:32:31 INFO: My name is "raspberrypi"
[BOEUZ] 2022/12/07 10:32:31 VERBOSE: Folder "default" is now scan-waiting
[BOEUZ] 2022/12/07 10:32:31 VERBOSE: Folder "default" is now scanning
[BOEUZ] 2022/12/07 10:32:31 VERBOSE: Startup complete
[BOEUZ] 2022/12/07 10:32:31 INFO: Completed initial scan of sendreceive folder "Default Folder" (default)
[BOEUZ] 2022/12/07 10:32:31 VERBOSE: Folder "default" is now idle
[BOEUZ] 2022/12/07 10:32:41 INFO: Detected 1 NAT service
[BOEUZ] 2022/12/07 10:32:50 INFO: quic://0.0.0.0:22000 detected NAT type: Port restricted NAT
[BOEUZ] 2022/12/07 10:32:50 INFO: quic://0.0.0.0:22000 resolved external address quic://186.151.24.133:21377 (via stun.syncthing.net:3478)
[BOEUZ] 2022/12/07 10:32:50 VERBOSE: Listen address quic://0.0.0.0:22000 resolution has changed: lan addresses: [quic://0.0.0.0:22000 quic://192.168.1.5:22000 quic://10.83.3.1:22000] wan addresses: [quic://0.0.0.0:22000 quic://186.151.24.133:21377]
[BOEUZ] 2022/12/07 10:33:48 INFO: Joined relay relay://104.245.38.195:22067
[BOEUZ] 2022/12/07 10:33:51 VERBOSE: Listen address dynamic+https://relays.syncthing.net/endpoint resolution has changed: lan addresses: [relay://104.245.38.195:22067/?globalLimitBps=51200&id=LARCFRF-B6CZRQD-JTWAK4K-HVRGQ5D-U4CY7MR-OY5QWLB-2MAWBSF-J2GGQQH&networkTimeout=2m0s&pingInterval=1m0s&providedBy=akame&sessionLimitBps=9600&statusAddr=%3A22070] wan addresses: [relay://104.245.38.195:22067/?globalLimitBps=51200&id=LARCFRF-B6CZRQD-JTWAK4K-HVRGQ5D-U4CY7MR-OY5QWLB-2MAWBSF-J2GGQQH&networkTimeout=2m0s&pingInterval=1m0s&providedBy=akame&sessionLimitBps=9600&statusAddr=%3A22070]
^C[monitor] 2022/12/07 11:08:51 INFO: Signal 2 received; exiting
[BOEUZ] 2022/12/07 11:08:51 INFO: QUIC listener ([::]:22000) shutting down
[BOEUZ] 2022/12/07 11:08:51 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[BOEUZ] 2022/12/07 11:08:52 INFO: TCP listener ([::]:22000) shutting down
[BOEUZ] 2022/12/07 11:08:52 INFO: Exiting
wolfslair@raspberrypi:~$ ^C
wolfslair@raspberrypi:~$  Listen address dynamic+https:wolfslair@raspberrypi:~$ syncthing -verbose
[start] 2022/12/07 10:32:28 INFO: syncthing v1.22.2 "Fermium Flea" (go1.19.2 linux-arm) teamcity@build.syncthing.net 2022-11-28 03:48:37 UTC
[BOEUZ] 2022/12/07 10:32:29 INFO: My ID: BOEUZYY-54BD62B-KSVFTEW-AWMRX6V-KWINPHR-UJSFJJC-CKWQXDJ-LQ6KIAQ
[BOEUZ] 2022/12/07 10:32:30 INFO: Single thread SHA256 performance is 53 MB/s using minio/sha256-simd (53 MB/s using crypto/sha256).
[BOEUZ] 2022/12/07 10:32:30 VERBOSE: Starting up (/home/wolfslair/.config/syncthing)
[BOEUZ] 2022/12/07 10:32:31 INFO: Hashing performance is 47.83 MB/s
[BOEUZ] 2022/12/07 10:32:31 INFO: Overall send rate is unlimited, receive rate is unlimited
[BOEUZ] 2022/12/07 10:32:31 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[BOEUZ] 2022/12/07 10:32:31 INFO: QUIC listener ([::]:22000) starting
[BOEUZ] 2022/12/07 10:32:31 VERBOSE: Listen address quic://0.0.0.0:22000 resolution has changed: lan addresses: [quic://0.0.0.0:22000 quic://192.168.1.5:22000 quic://10.83.3.1:22000] wan addresses: [quic://0.0.0.0:22000]
[BOEUZ] 2022/12/07 10:32:31 INFO: TCP listener ([::]:22000) starting
[BOEUZ] 2022/12/07 10:32:31 VERBOSE: Listen address tcp://0.0.0.0:22000 resolution has changed: lan addresses: [tcp://0.0.0.0:22000 tcp://192.168.1.5:22000 tcp://10.83.3.1:22000] wan addresses: [tcp://0.0.0.0:0 tcp://0.0.0.0:22000]
[BOEUZ] 2022/12/07 10:32:31 INFO: Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[BOEUZ] 2022/12/07 10:32:31 INFO: Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[BOEUZ] 2022/12/07 10:32:31 INFO: Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[BOEUZ] 2022/12/07 10:32:31 INFO: Using discovery mechanism: IPv4 local broadcast discovery on port 21027
[BOEUZ] 2022/12/07 10:32:31 INFO: Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
[BOEUZ] 2022/12/07 10:32:31 INFO: Ready to synchronize "Default Folder" (default) (sendreceive)
[BOEUZ] 2022/12/07 10:32:31 INFO: GUI and API listening on 127.0.0.1:8384
[BOEUZ] 2022/12/07 10:32:31 INFO: Access the GUI via the following URL: http://127.0.0.1:8384/
[BOEUZ] 2022/12/07 10:32:31 INFO: My name is "raspberrypi"
[BOEUZ] 2022/12/07 10:32:31 VERBOSE: Folder "default" is now scan-waiting
[BOEUZ] 2022/12/07 10:32:31 VERBOSE: Folder "default" is now scanning
[BOEUZ] 2022/12/07 10:32:31 VERBOSE: Startup complete
[BOEUZ] 2022/12/07 10:32:31 INFO: Completed initial scan of sendreceive folder "Default Folder" (default)
[BOEUZ] 2022/12/07 10:32:31 VERBOSE: Folder "default" is now idle
[BOEUZ] 2022/12/07 10:32:41 INFO: Detected 1 NAT service
[BOEUZ] 2022/12/07 10:32:50 INFO: quic://0.0.0.0:22000 detected NAT type: Port restricted NAT
[BOEUZ] 2022/12/07 10:32:50 INFO: quic://0.0.0.0:22000 resolved external address quic://186.151.24.133:21377 (via stun.syncthing.net:3478)
[BOEUZ] 2022/12/07 10:32:50 VERBOSE: Listen address quic://0.0.0.0:22000 resolution has changed: lan addresses: [quic://0.0.0.0:22000 quic://192.168.1.5:22000 quic://10.83.3.1:22000] wan addresses: [quic://0.0.0.0:22000 quic://186.151.24.133:21377]
[BOEUZ] 2022/12/07 10:33:48 INFO: Joined relay relay://104.245.38.195:22067
[BOEUZ] 2022/12/07 10:33:51 VERBOSE: Listen address dynamic+https://relays.syncthing.net/endpoint resolution has changed: lan addresses: [relay://104.245.38.195:22067/?globalLimitBps=51200&id=LARCFRF-B6CZRQD-JTWAK4K-HVRGQ5D-U4CY7MR-OY5QWLB-2MAWBSF-J2GGQQH&networkTimeout=2m0s&pingInterval=1m0s&providedBy=akame&sessionLimitBps=9600&statusAddr=%3A22070] wan addresses: [relay://104.245.38.195:22067/?globalLimitBps=51200&id=LARCFRF-B6CZRQD-JTWAK4K-HVRGQ5D-U4CY7MR-OY5QWLB-2MAWBSF-J2GGQQH&networkTimeout=2m0s&pingInterval=1m0s&providedBy=akame&sessionLimitBps=9600&statusAddr=%3A22070]
^C[monitor] 2022/12/07 11:08:51 INFO: Signal 2 received; exiting
[BOEUZ] 2022/12/07 11:08:51 INFO: QUIC listener ([::]:22000) shutting down
[BOEUZ] 2022/12/07 11:08:51 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[BOEUZ] 2022/12/07 11:08:52 INFO: TCP listener ([::]:22000) shutting down
[BOEUZ] 2022/12/07 11:08:52 INFO: Exiting
2

Judging by the log messages, it seems that Syncthing started properly. What is the actual problem? You should be able to access the Web GUI using the address listed there, i.e. 127.0.0.1:8384. You will need to do it from the device itself. Have you got a monitor and keyboard attached to it?

If not, you will need to set up remote access which requires a few additional steps.

1 Like
3

The apt install command would have returned an error if the installation had failed. To check if Syncthing has been installed, use the following command

dpkg --list syncthing

“dpkg” is the Debian package manager. The output will look something like this:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-==================================
ii  syncthing      1.18.0~ds1-3 amd64        decentralized file synchronization

The “ii” code at the start of the line means the Syncthing has been installed.

I agree with @tomasz86, the terminal output you posted says Syncthing is working normally.

Syncthing wasn’t actually stuck, it was running and waiting for activity which it would have continued to print into the terminal (useful during initial setup).

The only thing that looks odd is your username changes in the middle of the terminal session from “pi” to “wolfslair” but the Syncthing device id was still “BOEUZ”. Did you rename the username?

First decide if it’s going to be “pi” or “wolfslair” who will be running Syncthing. If it’s going to be “wolfslair”, then Syncthing will store its configuration under /home/wolfslair/.config/syncthing (similar for user “pi”).

Then since you’ll probably want to be able to launch Syncthing without keeping a terminal session open and/or a monitor and keyboard connected to the Raspberry Pi, decide how you want to autostart Syncthing (see “Starting Syncthing Automatically” in the documentation for suggestions).

The crib notes version for Ubuntu Desktop/Server:

  1. Log on as “wolfslair”.
  2. loginctl enable-linger wolfslair
  3. systemctl --user enable syncthing.service
  4. systemctl --user start syncthing.service

Step one tells systemd’s login manager that you want a service to continue running when you aren’t logged on (otherwise it’ll start when you log on and stop when you logoff).

Step two tells systemd that you want to enable the Syncthing service to run under user “wolfslair” (systemd supports system and user services).

Step three tells systemd to start the specified service. Alternatively, reboot the Raspberry Pi and Syncthing will auto-start during boot.

See also:

1 Like
4

Thank you very much, guys. With your comments I could figure it out.

5

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