[SOLVED] systemctl transmission-daemon fails to load config file
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've checked for missing commas, and if requested statements are also complimentary (e.g. when a Boolean is requested that i also give a Boolean and not a string.)
I've also set the settings.json file to 777 to check if maybe the file is not accessible but that did not change anything.
I've noticed that there are a lot of different locations of the settings.json file could it be the problem that i'm editing the wrong one ? unfortunately systemctl does not say which file it's loading.
I've never used any torrent client where I specifically set it up using the config file, but instead used their interface for this.
My suggestion is that you run it default, get the default config file, or even make some settings changes that you can do using the GUI and then check that config file against what you intend to use.
Apparently the settings.json file located in $HOME/.config/transmission folder was loaded rather than the /etc/transmission-daemon/settings.json location. The settings file there turned out to be corrupt. Overwriting it with the /etc/transmission-daemon/settings.json solved the issue!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.