Closed pdoroba closed 4 years ago
As far as I can tell this issue began after the latest container update. I haven't made any configuration changes on the transmission container in over a year.
I think there is an issue parsing /config/settings.json after last "latest" update particularly with env TRANSMISSION_UMASK set to 002
docker logs show error:
JSON parse failed in /config/settings.json at pos 2217: INVALID_NUMBER -- remaining text "02, "upload-"
which for me the 02, refers to the TRANSMISSION_UMASK 002 ENV var
I tried changing TRANSMISSION_UMASK to just 2 and container started up no problem
yes, the settings are not correct and the umask need to be fixed as @mikeeman mentioned
I am experiencing the same issue with parsing the settings.json:
JSON parse failed in /data/transmission-home/settings.json at pos 2221: INVALID_NUMBER -- remaining text "02, "upload-"
Docker compose for the transmission-vpn containing:
- TRANSMISSION_UMASK=002
Change it to just 2, not 002 Json doesn’t support 002, so if you set it to 2 it will be same
OK, changed to 2
instead of 002
and it's working. Thanks.
Thank you! That fixed the problem. What's odd is that I've been running the container with that configuration for over a year without issue. The only changes I've made in recent months was to rename the docker compose file with traefik_v1.7 as I work on moving to traefik 2.2. That was over 2 months ago and transmission didn't start throwing a fit until a day ago. Thanks again! I appreciate the help and quick resolution.
For context, I too was running the container with TRANSMISSION_UMASK=002 for the longest time and only the latest update broke this on May 26th, 2020, might still make sense to look into this and fix the root cause, I only proposed a workaround.
I think most people will have TRANSMISSION_UMASK=002 and will have this issue, may want to reopen this or create a new issue to help those people since the last "latest" image was a breaking change
wonder if a recent Docker update caused the issue? on my Ubuntu 16.04 I see a docker-ce update I did on 5/20
hmm, ive always had UMASK=2 due to the json way of parsing.. 002 shouldnt be working, but yeah, there might something in recent docker updates about this
just checked and the default value in the repo for this is UMASK=2..
ok understood thanks
Yeah, if you had it working with 002 that is very strange, as json doesnt accept that. from transmission: https://github.com/transmission/transmission/wiki/Editing-Configuration-Files umask: Number (default = 18) Sets transmission's file mode creation mask. See the umask(2) manpage for more information. Users who want their saved torrents to be world-writable may want to set this value to 0. Bear in mind that the json markup language only accepts numbers in base 10, so the standard umask(2) octal notation "022" is written in settings.json as 18.
so closing this
I just updated my Transmission container and had this error too:
[2020-07-05 12:23:06.275] JSON parse failed in /config/settings.json at pos 2211: INVALID_NUMBER -- remaining text "02,
"upload-"
I also had TRANSMISSION_UMASK
set to 002
and changing it to 2
fixed it, I never set it to 002 so this was the default when I created the container.
Maybe the container needs to tolerate 002 so that others who update their container don't face the same issue.
The container default is 2, feel free to check the history of the settings file if you want but I don’t believe this was changed. It’s a 3pp that parses the json..I don’t think it’s reasonable to handle wrong config more than output an error and then let the end user correct it. From previous discussion, many followed some kind of guide that was using wrong settings and then blame this container..
On Sun, Jul 5, 2020 at 21:44 OscarVanL notifications@github.com wrote:
I just updated my Transmission container and had this error too:
[2020-07-05 12:23:06.275] JSON parse failed in /config/settings.json at pos 2211: INVALID_NUMBER -- remaining text "02, "upload-"
I also had TRANSMISSION_UMASK set to 002 and changing it to 2 fixed it, I never set it to 002 so this was the default when I created the container.
Maybe the container needs to tolerate 002 so that others who update their container don't face the same issue.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/haugene/docker-transmission-openvpn/issues/1210#issuecomment-653884482, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7OFYR2E6PNICJGFID2OV3R2BYTRANCNFSM4NLRTCIQ .
Describe the problem
Can't connect to web UI.
Add your docker run command