I suggest changing the defaults such that the default path's line up with the mount to the host FS (whether that is making the default be `/home/nobody` instead of `/media` or changing the syncthing config). Nothing wrong with your container but if you use the default path in syncthing itself for adding folders to it will be at '~' AKA '/home/nobody' and will save the data into the container image and fill up the docker.img really quickly. You can do file level backups, limit what you want backed up, and can even do image level backups. It just works! It is like your own Crashplan, but free. While this may not work for your setup, I'm using UMASK 000, PUID 99, PGID 100.Īnother thing you can look at is. Make sure you are running syncthing with the correct UMASK/PUID/PGID, and make sure that the folder in the share has the correct permissions.
#SYNCTHING TUTORIAL PC#
Maybe I'm not using syncthing correctly.but what I was trying to do was have it backup the My Documents folder on the PC to the Unraid share (which is backed up via CrashPlan). When I create the folder, syncthing gives me an error about not having access to create the directory? I went into the versioning tab, and set it to 30 days. I create a backup folder with a path that points to the backup share on my Unraid server (/mnt/user/Backup/PC-001/My Documents). I keep getting an error message when I try to start syncthing. I'm trying to use syncthing as a backup of the My Documents folder on a PC on the network.
#SYNCTHING TUTORIAL WINDOWS#
Nmap scanning windows shows every interrsting port closed, even if the firewall has rules for syncthing or is disabled completely.ĭo I do anything wrong? Is this a configuration issue on my machine? A Docker bug? When I add 21067, it does not show up in the 'docker allocations' (neither do other ports I tested with - on this and other containers), and nmap obviously shows it as closed. Using nmap from windows and another Linux machine, 22000 is detected as closed. In the end I found out, that this container is missing the announce UDP port 21067 from its configuration and 22000 stays closed. (Unraid server and windows box.) It was especially weird, because all other devices had no issues. Two of my devices are not capable of finding each other in the same LAN.
#SYNCTHING TUTORIAL UPDATE#
There was a bug in a recent release, a quick following update fixed this, so please do a 'check for updates' and then 'update all' and this should get it working. I did look around the interwebs but didn't find anyone having this issue. Today at 10:55 PM 22:55:28,065 INFO gave up: syncthing entered FATAL state, too many start retries too quickly
Today at 10:55 PM 22:55:27,064 DEBG received SIGCHLD indicating a child quit Today at 10:55 PM 22:55:27,064 INFO exited: syncthing (exit status 1 not expected) Today at 10:55 PM 22:55:27,064 DEBG fd 15 closed, stopped monitoring (stderr)> Today at 10:55 PM 22:55:27,064 DEBG fd 11 closed, stopped monitoring (stdout)> Looks like the latest update broke something I have two different unraid servers and syncthing broke when I updated them on both servers.
0 kommentar(er)
