July 29, 20241 yr Container path can/needs to be the same, but you need to adjust the unraid side path. Obviously now everything in a given syncthing folder has to lie on the same physical disk unlike previously, and you'd need to consolidate before changing anything if it isn't. Edited July 29, 20241 yr by Kilrah
August 2, 20241 yr Hi, After the latest update, my binhex-syncthing container refuses to start. Get the following in the log files. Any ideas how can this issue be resolved? Thanks Traceback (most recent call last): File "/usr/bin/supervisord", line 33, in <module> sys.exit(load_entry_point('supervisor==4.2.5', 'console_scripts', 'supervisord')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/supervisor/supervisord.py", line 359, in main go(options) File "/usr/lib/python3.12/site-packages/supervisor/supervisord.py", line 369, in go d.main() File "/usr/lib/python3.12/site-packages/supervisor/supervisord.py", line 72, in main self.options.make_logger() File "/usr/lib/python3.12/site-packages/supervisor/options.py", line 1501, in make_logger self.logger.info(msg) File "/usr/lib/python3.12/site-packages/supervisor/loggers.py", line 327, in info self.log(LevelsByName.INFO, msg, **kw) File "/usr/lib/python3.12/site-packages/supervisor/loggers.py", line 345, in log handler.emit(record) File "/usr/lib/python3.12/site-packages/supervisor/loggers.py", line 227, in emit self.doRollover() File "/usr/lib/python3.12/site-packages/supervisor/loggers.py", line 275, in doRollover self.removeAndRename(self.baseFilename, dfn) File "/usr/lib/python3.12/site-packages/supervisor/loggers.py", line 250, in removeAndRename self._rename(sfn, dfn) File "/usr/lib/python3.12/site-packages/supervisor/loggers.py", line 235, in _rename return os.rename(src, tgt) ^^^^^^^^^^^^^^^^^^^ OSError: [Errno 5] Input/output error: '/config/supervisord.log' -> '/config/supervisord.log.1' Traceback (most recent call last): File "/usr/bin/supervisord", line 33, in <module> sys.exit(load_entry_point('supervisor==4.2.5', 'console_scripts', 'supervisord')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/supervisor/supervisord.py", line 359, in main go(options) File "/usr/lib/python3.12/site-packages/supervisor/supervisord.py", line 369, in go d.main() File "/usr/lib/python3.12/site-packages/supervisor/supervisord.py", line 72, in main self.options.make_logger() File "/usr/lib/python3.12/site-packages/supervisor/options.py", line 1501, in make_logger self.logger.info(msg) File "/usr/lib/python3.12/site-packages/supervisor/loggers.py", line 327, in info self.log(LevelsByName.INFO, msg, **kw) File "/usr/lib/python3.12/site-packages/supervisor/loggers.py", line 345, in log handler.emit(record) File "/usr/lib/python3.12/site-packages/supervisor/loggers.py", line 227, in emit self.doRollover() File "/usr/lib/python3.12/site-packages/supervisor/loggers.py", line 275, in doRollover self.removeAndRename(self.baseFilename, dfn) File "/usr/lib/python3.12/site-packages/supervisor/loggers.py", line 250, in removeAndRename self._rename(sfn, dfn) File "/usr/lib/python3.12/site-packages/supervisor/loggers.py", line 235, in _rename return os.rename(src, tgt) ^^^^^^^^^^^^^^^^^^^ OSError: [Errno 5] Input/output error: '/config/supervisord.log' -> '/config/supervisord.log.1' Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2024-08-02 11:56:08.714489 [info] Host is running unRAID 2024-08-02 11:56:08.726229 [info] System information Linux 9a146909e976 6.1.49-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 30 09:42:35 PDT 2023 x86_64 GNU/Linux 2024-08-02 11:56:08.740237 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no' 2024-08-02 11:56:08.753825 [info] PUID defined as '99' 2024-08-02 11:56:08.799071 [info] PGID defined as '100' 2024-08-02 11:56:08.854223 [info] UMASK defined as '000' 2024-08-02 11:56:08.867045 [info] Permissions already set for '/config' 2024-08-02 11:56:08.881617 [info] Deleting files in /tmp (non recursive)... 2024-08-02 11:56:08.900323 [info] Starting Supervisor... 2024-08-02 11:56:09,010 INFO Included extra file "/etc/supervisor/conf.d/syncthing.conf" during parsing Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2024-08-02 12:02:08.336438 [info] Host is running unRAID 2024-08-02 12:02:08.348897 [info] System information Linux 9a146909e976 6.1.49-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 30 09:42:35 PDT 2023 x86_64 GNU/Linux 2024-08-02 12:02:08.362191 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no' 2024-08-02 12:02:08.375645 [info] PUID defined as '99' 2024-08-02 12:02:08.389932 [info] PGID defined as '100' 2024-08-02 12:02:08.423587 [info] UMASK defined as '000' 2024-08-02 12:02:08.436841 [info] Permissions already set for '/config' 2024-08-02 12:02:08.450793 [info] Deleting files in /tmp (non recursive)... 2024-08-02 12:02:08.468738 [info] Starting Supervisor... 2024-08-02 12:02:08,554 INFO Included extra file "/etc/supervisor/conf.d/syncthing.conf" during parsing
August 3, 20241 yr Hi, I am getting an inotify error with "For the following folders an error occurred while starting to watch for changes. It will be retried every minute, so the errors might go away soon. If they persist, try to fix the underlying issue and ask for help if you can't. Support Immichfailed to setup inotify handler. Please increase inotify limits, see https://docs.syncthing.net/users/faq.html#inotify-limits" I have searched but little info on how to increase inotify limits on a container? Can anyone offer any advice please?
August 8, 20241 yr Hello! Newby here, I been getting can't reach page. Refuse to connect page. I don't know what else to do. I have reset the server and nothing works.
August 12, 20241 yr I downloaded synchthing and it's prompting me to a username and password but I haven't set up one. How can I reset it?
August 13, 20241 yr Author 10 hours ago, Flixlover said: I downloaded synchthing and it's prompting me to a username and password but I haven't set up one. How can I reset it? So you did not set any password in the syncthing web ui and yet its prompting for username and password?. This is what i see on first startup, did you set authentication and then forget what you set it to?:- If i click on OK from the above screenshot and do nothing else and then restart the container i get no prompt for credentials.
September 5, 20241 yr I've had this problem a few times now and probably time to see if I can prevent it. I have about 18TB synced between my unraid server, another unraid server and a Windows PC. I transferred the main unraid server from one chassis to a larger one, which makes all the hard drives change physical ports, but still present and accounted for and unraid sees all disks and can start the array no problem. The previous time I moved hdd's around, unraid's syncthing was saying there was like 10TB of files to be sync'd and it takes days and days to resolve itself. It doesn't appear to be sucking CPU and network speeds are in the Kb/s. But took like 4-5 days to reach 100% sync. Today, after moving the motherboard to the new chassis yesterday, it was saying around 400GB was out of sync with the other unraid server and 4TB was out of sync with the Windows PC and it's been around 77% sync'd since almost 24 hours. Given that the data shouldn't have changed on the Windows PC or on the unraid hard drives, I'm not sure wtf syncthing is doing all this time. Or even why it didn't have the same amount of data showing unsynced between the second unraid server and windows PC. Best case, I figure out what is happening and prevent it. Alternatively, I'd like to see what can be done about speeding up the resyncing. Anyone have any idea why it thinks a bunch of files are out of sync? Thanks
September 5, 20241 yr Are all your paths through /mnt/user and not individual disks? Did you make sure time on the new machine was set correctly before starting array/syncthing? I'd think that's the most likely cause, new machine hadn't gotten NTP yet, syncthing saw date/time mismatches...
September 5, 20241 yr 8 hours ago, Kilrah said: Are all your paths through /mnt/user and not individual disks? Did you make sure time on the new machine was set correctly before starting array/syncthing? I'd think that's the most likely cause, new machine hadn't gotten NTP yet, syncthing saw date/time mismatches... Correct, only using: /media <-> /mnt/user /config <-> /mnt/cache/appdata/binhex-syncthing I can only check now, but time is within a second from my second unraid box. The server was off for like 1-2 days (same motherboard, just different chassis and hdd ports used), I don't think that would have been enough to drift more than a few seconds, but this is probably the best lead I have. It appears that the syncing isn't progressing. I'm going to have to enable more verbose syncthing logging to find out what it is doing. It is stuck on something and not working itself out. Thanks
September 6, 20241 yr Update: Today, both unraid and my Windows PC upgraded syncthing to 1.27.12 and both sides now appear to be slowly syncing again. The out of sync counts are both decreasing slowly, as opposed to not decreasing at all the previous 24hours+. Sounds like I ran into a bug at 1.27.11 and 1.27.12 corrected it. I'll need to check for release notes at some point and see if I can confirm. Edit: All, a parity check is running (slowly), so that likely isn't helping, either. I've been getting unclean shutdowns from rebooting from webGUI. I've increased the graceful shutdown time from 90 to 120 seconds, hopefully that was my issue with dockers running and so on. Edited September 6, 20241 yr by CaptainMorganCrunch parity check also running
February 7, 20251 yr On 5/29/2024 at 5:24 PM, emp83 said: This solved my problem, only in unRAID folder sync did I activate the "ignore permissions" option. This did not seem to work for me... I sync several shares with my Windows notebook (and a few with my Android phone). When I create files/folders/subfolders on Windows, the newly synced folders on the Unraid share receive 644 permissions - So they cannot be modified via "normal" users with SMB read/write permission... After checking "Ignore permissions", the behavior is the same - Is there anything else required for Syncthing to assign new data the same permissions as the share?
February 12, 20251 yr On 7/12/2023 at 12:14 PM, binhex said: you need to set consistent permissions for both containers if you need to access files/folders created by either. @binhex So how do I set consistent permissions between the syncthing docker and SMB users? All Users (incl. "nobody" which runs syncthing) are members of GUID 100 ("Users"). But when I create a file or folder on a remote device, permissions on the Unraid NAS are set to 755 for folders resp. 644 for files - So a SMB-User has no permission to create files in a new folder, or modify a file. However, when I create a file/folder via an SMB user, its permissions are set on Unraid to 777 for folders, or 766 for files (i.e. (only) the owner is allowed to execute any file, e.g. test.txt ...).. Is there any way to change the permissions for files received from remote (within the guid 100 "users") - without having to grant root permissions to Syncthing?
February 13, 20251 yr i am trying to script bandwith limits via CLI but i receive an error .. where the syncthing support forum is not yet helpful i run the command "syncthing cli config options max-recv-kbps set 50" inside the container but the following error appears: "syncthing: error: reading device ID: open /home/nobody/.local/state/syncthing/cert.pem: no such file or directory" any idea ? i would like to limit during the day and open the upload during the night ..
February 19, 20251 yr On 2/12/2025 at 4:24 PM, madmin said: However, when I create a file/folder via an SMB user, its permissions are set on Unraid to 777 for folders, or 766 for files (i.e. (only) the owner is allowed to execute any file, e.g. test.txt ...).. Is there any way to change the permissions for files received from remote (within the guid 100 "users") - without having to grant root permissions to Syncthing? Has anyone else solved this? It does not seem like an unusual use case... Or have I missed a solution in the forum?
February 19, 20251 yr Well the container has PUID/PGID/UMASK values so you should be able to set those to set the proper perms to newly created files. If it doesn't work it'd be a bug, I personally haven't looked since on my server syncthing is isolated.
February 19, 20251 yr 58 minutes ago, Kilrah said: Well the container has PUID/PGID/UMASK values so you should be able to set those to set the proper perms to newly created files. Thanks - I found that info just now, too, in the German forum, with the hint that UMASK needs to be set to 002 instead of 022 to result in the correct chmod code. That worked. Thanks for your response!
August 10, 2025Aug 10 I get this message on all folders I add and the guide is not helping.failed to set up inotify handler. Please increase inotify limits, see https://docs.syncthing.net/users/faq.html#inotify-limits
August 12, 2025Aug 12 So, Syncthing proposed an update to version 2.0.0 today. I've previously updated from older versions to newer from within the web interface, but this time it didn't come back up.I see this in the logs:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~2025-08-12 09:34:47,319 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23158311906064 for <Subprocess at 23158313690048 with name start-script in state STARTING> (stdout)>2025-08-12 09:34:47,319 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23158312503344 for <Subprocess at 23158313690048 with name start-script in state STARTING> (stderr)>2025-08-12 09:34:47,319 WARN exited: start-script (exit status 80; not expected)2025-08-12 09:34:47,319 DEBG received SIGCHLD indicating a child quit2025-08-12 09:34:50,323 INFO spawned: 'start-script' with pid 862025-08-12 09:34:50,340 DEBG 'start-script' stderr output:syncthing: error: unknown flag -c, did you mean one of "-h", "-C", "-D", "-H"?2025-08-12 09:34:50,341 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23158312310160 for <Subprocess at 23158313690048 with name start-script in state STARTING> (stdout)>2025-08-12 09:34:50,341 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23158312312608 for <Subprocess at 23158313690048 with name start-script in state STARTING> (stderr)>2025-08-12 09:34:50,341 WARN exited: start-script (exit status 80; not expected)2025-08-12 09:34:50,341 DEBG received SIGCHLD indicating a child quit2025-08-12 09:34:51,342 INFO gave up: start-script entered FATAL state, too many start retries too quickly~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~I would try to change the startup script but I don't know where to do it. Anyone else having this issue and/or know how to fix it?
August 12, 2025Aug 12 3 hours ago, dhomas said:So, Syncthing proposed an update to version 2.0.0 today. I've previously updated from older versions to newer from within the web interface, but this time it didn't come back up.I see this in the logs:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~2025-08-12 09:34:47,319 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23158311906064 for <Subprocess at 23158313690048 with name start-script in state STARTING> (stdout)>2025-08-12 09:34:47,319 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23158312503344 for <Subprocess at 23158313690048 with name start-script in state STARTING> (stderr)>2025-08-12 09:34:47,319 WARN exited: start-script (exit status 80; not expected)2025-08-12 09:34:47,319 DEBG received SIGCHLD indicating a child quit2025-08-12 09:34:50,323 INFO spawned: 'start-script' with pid 862025-08-12 09:34:50,340 DEBG 'start-script' stderr output:syncthing: error: unknown flag -c, did you mean one of "-h", "-C", "-D", "-H"?2025-08-12 09:34:50,341 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23158312310160 for <Subprocess at 23158313690048 with name start-script in state STARTING> (stdout)>2025-08-12 09:34:50,341 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23158312312608 for <Subprocess at 23158313690048 with name start-script in state STARTING> (stderr)>2025-08-12 09:34:50,341 WARN exited: start-script (exit status 80; not expected)2025-08-12 09:34:50,341 DEBG received SIGCHLD indicating a child quit2025-08-12 09:34:51,342 INFO gave up: start-script entered FATAL state, too many start retries too quickly~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~I would try to change the startup script but I don't know where to do it. Anyone else having this issue and/or know how to fix it?So, I stopped the container and tried starting it via 'docker run' which didn't fail at startup, but seemed to hang. I may have not started it correctly, though. I ended up rolling back to Syncthing v1.3.0 and everything is back to normal. I think the binhex container will need to be tweaked to work with version 2.0.0, though.
August 18, 2025Aug 18 On 8/12/2025 at 7:19 PM, dhomas said:So, I stopped the container and tried starting it via 'docker run' which didn't fail at startup, but seemed to hang. I may have not started it correctly, though. I ended up rolling back to Syncthing v1.3.0 and everything is back to normal.I think the binhex container will need to be tweaked to work with version 2.0.0, though.yep syncthing is broken after update, it even corrupted my plex database for some reason ! i have/had the linuxserver version Edited August 18, 2025Aug 18 by Mr Q
August 19, 2025Aug 19 @binhex Hi binhex. We need your help with syncthing v2. I'm not sure how a new docker will work if you need to run an upgrade process. I guess the script would need to be changed to do that if the current version is lower than version 2.
August 19, 2025Aug 19 i had no issues updating to 2.0 several weeks ago on 4 clients, all unraid. did not yet update to 2.0.2
August 21, 2025Aug 21 Author On 8/19/2025 at 1:14 AM, TimTheSettler said:@binhex Hi binhex. We need your help with syncthing v2. I'm not sure how a new docker will work if you need to run an upgrade process. I guess the script would need to be changed to do that if the current version is lower than version 2.Hi, sorry for the delay, i have been sitting on a very large boat for 2 weeks :-). OK ive taken a look at the issue and its simply that the syncthing dev's have made a breakiing change to the cli options, so you now need to specify double hyphens for the cli options, changed my start script and its built and gone through my smoke test and passed, so the new release is now there.
August 21, 2025Aug 21 Author On 8/18/2025 at 11:12 PM, Mr Q said:yep syncthing is broken after updateJust as a side note here, please do not use built in update functionality for any docker applications, it will likely result in a broken container,wait for the dev to update the image.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.