• Posts

  • Joined

  • Last visited

Everything posted by jayjay

  1. I have to come back to a previous issue (Resilio Sync not listening to port 3838 on Ubuntu 20.04) which hasn't been solved. In many case LAN search is not working for the Resilio Sync client on my Ubuntu 20.04 server as Resilio Sync is not listening to multicast on port 3838, which is required to LAN search. This happens often after a reboot and if a do a service restart of the resilio sync process it is always the case. If everything is fine netstat -npl |grep rslsync showstcp 0 0* LISTEN 2448/rslsynctcp6 0 0 :::40935 :::* LISTEN 2448/rslsyncudp 0 0* 2448/rslsyncudp 0 0* 2448/rslsyncudp 0 0* 2448/rslsyncudp6 0 0 :::3838 :::* 2448/rslsyncudp6 0 0 :::40935 :::* 2448/rslsync In case it is not working it showstcp 0 0* LISTEN 1870/rslsynctcp6 0 0 :::40935 :::* LISTEN 1870/rslsyncudp 0 0* 1870/rslsyncudp6 0 0 :::40935 :::* 1870/rslsync Previously triggering a network restart using "netplan apply" solved the problem as resilio started to listen to port 3838 after the restart. However this is no longer the case. A network restart doesn't change anything. Previously resilio detected the network restart and reloaded its network configuration (logged in sync.log), but seems to be no longer the case. Any idea why Resilio is not binding to port 3838? For the detail configuration files see my previous issue report mentioned above.
  2. I am running several resilio sync instances in parallel on my Ubuntu 20.04 home server. But it is in configuration mode without a WebUI. The setup is as follows (as root): Setup an account for each user on your home server. You can disable login if you don't want these users to login onto you server by changing "bin/bash" to "/bin/false" for the specific user in the /etc/passwd file. I assume that sync directories for each user are under its home directory. But you can also have them elsewhere. Make the necessary sync directories under each user home folder like mkdir /home/<username>/pictures and mkdir /home/<username>/music and ensure that they are owned by the user (i.e. chown <username>:<username> /home/<username/pictures). For each instance generate a dedicated system service unit file /usr/lib/systemd/system/resilio-<username>.service [Unit] Description=Resilio Sync service <username> Documentation=https://help.resilio.com After=network.target network-online.target [Service] Type=forking User=<username> Group=<username> UMask=0002 Restart=on-failure PIDFile=/data/user/<username>/.btsync/sync.pid ExecStart=/usr/bin/rslsync --config /etc/resilio-sync/<username>.json ExecStartPost=/usr/bin/sleep 1 [Install] WantedBy=default.target For each instance generate a dedicated resilio sync config file /etc/resilio-sync/<username>.json { "device_name": "<servername>-<username>", "storage_path" : "/home/<username>/.btsync", "pid_file" : "/home/<username>/.btsync/sync.pid", "listening_port" : 40932, // <- define a different port for each instance ..... // <- other configuration as needed "webui" : { }, "shared_folders" : // <- add entries for each folder you want to share [ { "secret" : "XXXXXXXXXXXXXXXXXXXXXXXXXXX", "dir" : "/home/<username>/pictures", ..... <- other configuration as needed }, { "secret" : "YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY", "dir" : "/home/<username>/music", ..... <- other configuration as needed } ] } If you want to use the WebUI for more flexible configuration you have to remove the entries in the "shared_folders" section and add entries to the "webui" section. especially for "listen" : "" // <- use dedicated port for each instance/user you have to use dedicated ports for each user so that each has its own WebUI. You my also have dedicated login credetinals for each user. I assume you could also work without a resilio sync config file by using the command line options of rslync (i.e. --storage <path>, --identity <user name>, --webui.listen <IP>:<port>) if you don't need additoonal special configuration (see https://help.resilio.com/hc/en-us/articles/204762449-Guide-to-Linux-and-Sync-peculiarities).
  3. It ist not a firewall a Firewall, open Port or Antivirus topic. All Resilio Sync clients are in the lokal LAN and it works wit the Windows clients. Rslsync ist just not binding to the necessary ports when it starts. When I trigger a network reconfiguration I does so and it works until rslsync is restarted again. Seems an issue of the Linux version of rslsync.
  4. When LAN Scan is not working and I restart the network with netplan apply the binding to port 3838 is established and LAN Scan starts working. So something seems not working with the network setup at the initial start of rslsync.
  5. I have Resilio Sync 2.7.2 (1375) setup on a Ubuntu 20.04 server following the install from repository instructions at https://help.resilio.com/hc/en-us/articles/206178924-Installing-Sync-package-on-Linux. I have enabled LAN search but that is not working . The server is not automatically detected by other machines, while the Resilio Sync installations on several Windows machines find each other via LAN search. When I enable tracker server or configure the sever als known hosts on the Windows installations it is working fine. So LAN search seems not to be working on the server. However in case of some reboots of the server it is working. But when I do a restart of the resilio-sync service it s again not working my config.json on the Ubuntu server is as follows: { "device_name": "XYZ", "storage_path" : "/var/lib/resilio-sync/", "pid_file" : "/var/run/resilio-sync/sync.pid", "check_for_updates" : false, "use_upnp" : false, "download_limit" : 0, "upload_limit" : 0, "disk_low_priority" : false, "lan_encrypt_data" : true, "listening_port" : 40935, "folder_defaults.use_tracker" : false, "folder_defaults.use_relay" : false, "folder_defaults.lan_discovery_mode" : 3, "rate_limit_local_peers" : false, "folder_rescan_interval" : 600, "sync_trash_ttl" : 7, "webui" : { }, "shared_folders" : [ { "secret" : "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "dir" : "/home/rslsync/test", "search_lan" : true, "use_sync_trash" : true } ] } and /usr/lib/systemd/system/resilio-sync.service [Unit] Description=Resilio Sync service Documentation=https://help.resilio.com After=network.target network-online.target [Service] Type=forking UMask=0002 Restart=on-failure PermissionsStartOnly=true User=rslsync Group=rslsync Environment="SYNC_USER=rslsync" Environment="SYNC_GROUP=rslsync" Environment="SYNC_RUN_DIR=/var/run/resilio-sync" Environment="SYNC_LIB_DIR=/var/lib/resilio-sync" Environment="SYNC_CONF_DIR=/etc/resilio-sync" PIDFile=/var/run/resilio-sync/sync.pid ExecStartPre=/bin/mkdir -p ${SYNC_RUN_DIR} ${SYNC_LIB_DIR} ExecStartPre=/bin/chown -R ${SYNC_USER}:${SYNC_GROUP} ${SYNC_RUN_DIR} ${SYNC_LIB_DIR} ExecStart=/usr/bin/rslsync --config ${SYNC_CONF_DIR}/config.json ExecStartPost=/bin/sleep 1 [Install] WantedBy=multi-user.target I checked with tcpdump for packets send to port 3838 (the port used for LAN Sync according to https://help.resilio.com/hc/en-us/articles/204754759-What-ports-and-protocols-are-used-by-Sync-), but nothing is send when Resilio Sync is started on the server. The sync.log file on the server shows only bindings of listening sockets to and [::]:40935 but not to port 3838. and netstat -npl |grep rslsync shows tcp 0 0* LISTEN 1870/rslsync tcp6 0 0 :::40935 :::* LISTEN 1870/rslsync udp 0 0* 1870/rslsync udp6 0 0 :::40935 :::* 1870/rslsync So rslsync is not listening to port 3838 and it hasn't joined the multicast group which are needed for LAN Scan! In the few cases it is actually working after a reboot netstat -npl |grep rslsync shows tcp 0 0* LISTEN 2448/rslsync tcp6 0 0 :::40935 :::* LISTEN 2448/rslsync udp 0 0* 2448/rslsync udp 0 0* 2448/rslsync udp 0 0* 2448/rslsync udp6 0 0 :::3838 :::* 2448/rslsync udp6 0 0 :::40935 :::* 2448/rslsync and the sync.log file shows the binding to port 3838 and joining to multicast group However when I perform a restart with systemctl restart resilio-sync this is gone and it is no longer working. I further analyzed the sync.log files for both cases: In case LAN Sync is working I find the following entries in sync.log: [20201127 15:24:33.668] [NETLINK] Network interfaces configuration was changed ... [20201127 15:24:39.929] Posting message to change network to WIRED_NETWORK ... [20201127 15:24:39.931] Got network change event (suggested type: WIRED_NETWORK) [20201127 15:24:39.931] We are about network reload ... [20201127 15:24:40.131] Network reloaded and after that binding to port 3838 and joining the multicast group is done . In case LAN Scan is not working I don't find such network related entries in sync.log. It seems that this network interface configuration change initiates the enabling of the LAN Scan ports. Why are the LAN Scan ports only enabled in case of a network interface configuration change?