transmission-daemon: error loading working config-file. User priveliges?
Transmission-daemon has worked perfectly on a small headless server for a long time. However, it currently gives me the following error:
transmission-daemon Error loading config file -- exiting. (daemon.c:462)
Due to problems with permissions, all daemons are running as the user "robots" All config files are owned by "robots" and by the group "robots" of which I am a member.
For debugging purposes I tried running the daemon under my own account
transmission-daemon -f --log-debug -g /etc/transmission-daemon/
the daemon started succesfully without errors. From this I conclude that the configfile itself is OK. (I also tested this by substituting
USER=robots
by
USER=lars
The results remain the same; the daemon runs without errors. The config files in /etc/transmission-daemon /etc/init.d/ and /etc/defaults/ are all working fine when the daemon is running under my name.
I changed the permissions of the /etc/transmission-daemon/ and all the files and folders within to 777, and changed the owner and group back to robots. (because running the daemon under the name "lars" changes the ownership of the configfiles to "lars".
chmod 777 -R /etc/transmission-daemon/
chown robots:robots -R /etc/transmission-daemon/
chmod 777 /etc/defaults/transmission-daemon
chown robots:robots /etc/defaults/transmission-daemon
without succes... the daemon exits with the same error as stated above.
I don't know what I'm missing here, does anybody have an idea?
Thanks in advance
server permissions services transmission
add a comment |
Transmission-daemon has worked perfectly on a small headless server for a long time. However, it currently gives me the following error:
transmission-daemon Error loading config file -- exiting. (daemon.c:462)
Due to problems with permissions, all daemons are running as the user "robots" All config files are owned by "robots" and by the group "robots" of which I am a member.
For debugging purposes I tried running the daemon under my own account
transmission-daemon -f --log-debug -g /etc/transmission-daemon/
the daemon started succesfully without errors. From this I conclude that the configfile itself is OK. (I also tested this by substituting
USER=robots
by
USER=lars
The results remain the same; the daemon runs without errors. The config files in /etc/transmission-daemon /etc/init.d/ and /etc/defaults/ are all working fine when the daemon is running under my name.
I changed the permissions of the /etc/transmission-daemon/ and all the files and folders within to 777, and changed the owner and group back to robots. (because running the daemon under the name "lars" changes the ownership of the configfiles to "lars".
chmod 777 -R /etc/transmission-daemon/
chown robots:robots -R /etc/transmission-daemon/
chmod 777 /etc/defaults/transmission-daemon
chown robots:robots /etc/defaults/transmission-daemon
without succes... the daemon exits with the same error as stated above.
I don't know what I'm missing here, does anybody have an idea?
Thanks in advance
server permissions services transmission
add a comment |
Transmission-daemon has worked perfectly on a small headless server for a long time. However, it currently gives me the following error:
transmission-daemon Error loading config file -- exiting. (daemon.c:462)
Due to problems with permissions, all daemons are running as the user "robots" All config files are owned by "robots" and by the group "robots" of which I am a member.
For debugging purposes I tried running the daemon under my own account
transmission-daemon -f --log-debug -g /etc/transmission-daemon/
the daemon started succesfully without errors. From this I conclude that the configfile itself is OK. (I also tested this by substituting
USER=robots
by
USER=lars
The results remain the same; the daemon runs without errors. The config files in /etc/transmission-daemon /etc/init.d/ and /etc/defaults/ are all working fine when the daemon is running under my name.
I changed the permissions of the /etc/transmission-daemon/ and all the files and folders within to 777, and changed the owner and group back to robots. (because running the daemon under the name "lars" changes the ownership of the configfiles to "lars".
chmod 777 -R /etc/transmission-daemon/
chown robots:robots -R /etc/transmission-daemon/
chmod 777 /etc/defaults/transmission-daemon
chown robots:robots /etc/defaults/transmission-daemon
without succes... the daemon exits with the same error as stated above.
I don't know what I'm missing here, does anybody have an idea?
Thanks in advance
server permissions services transmission
Transmission-daemon has worked perfectly on a small headless server for a long time. However, it currently gives me the following error:
transmission-daemon Error loading config file -- exiting. (daemon.c:462)
Due to problems with permissions, all daemons are running as the user "robots" All config files are owned by "robots" and by the group "robots" of which I am a member.
For debugging purposes I tried running the daemon under my own account
transmission-daemon -f --log-debug -g /etc/transmission-daemon/
the daemon started succesfully without errors. From this I conclude that the configfile itself is OK. (I also tested this by substituting
USER=robots
by
USER=lars
The results remain the same; the daemon runs without errors. The config files in /etc/transmission-daemon /etc/init.d/ and /etc/defaults/ are all working fine when the daemon is running under my name.
I changed the permissions of the /etc/transmission-daemon/ and all the files and folders within to 777, and changed the owner and group back to robots. (because running the daemon under the name "lars" changes the ownership of the configfiles to "lars".
chmod 777 -R /etc/transmission-daemon/
chown robots:robots -R /etc/transmission-daemon/
chmod 777 /etc/defaults/transmission-daemon
chown robots:robots /etc/defaults/transmission-daemon
without succes... the daemon exits with the same error as stated above.
I don't know what I'm missing here, does anybody have an idea?
Thanks in advance
server permissions services transmission
server permissions services transmission
asked May 5 '13 at 9:54
larslars
101117
101117
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Problem solved!
The folder
/var/lib/transmission-daemon/
als needs to be owned by the correct user, so in addition to the commands stated in my question above:
sudo chown -R robots:robots /var/lib/transmission-daemon/
Replace the user "robots" and the group "robots" to the names used on your system.
add a comment |
Debian users may take a look at file: /lib/systemd/system/transmission-daemon.service to verify the required user is also set in that file.
Then, verify the home directory for that user because the configuration will then be read from ~/.config/transmission-daemon/
Hmm, debian isn't really on topic here...
– anonymous2
Jul 8 '16 at 13:49
add a comment |
Empty file /etc/transmission-daemon/settings.json
invokes this error in my case.
rm /etc/transmission-daemon/settings.json solves problem.
Debug hinit:
sudo -u debian-transmission strace transmission-daemon -f --log-debug -g /etc/transmission-daemon/
New contributor
noname is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f290943%2ftransmission-daemon-error-loading-working-config-file-user-priveliges%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Problem solved!
The folder
/var/lib/transmission-daemon/
als needs to be owned by the correct user, so in addition to the commands stated in my question above:
sudo chown -R robots:robots /var/lib/transmission-daemon/
Replace the user "robots" and the group "robots" to the names used on your system.
add a comment |
Problem solved!
The folder
/var/lib/transmission-daemon/
als needs to be owned by the correct user, so in addition to the commands stated in my question above:
sudo chown -R robots:robots /var/lib/transmission-daemon/
Replace the user "robots" and the group "robots" to the names used on your system.
add a comment |
Problem solved!
The folder
/var/lib/transmission-daemon/
als needs to be owned by the correct user, so in addition to the commands stated in my question above:
sudo chown -R robots:robots /var/lib/transmission-daemon/
Replace the user "robots" and the group "robots" to the names used on your system.
Problem solved!
The folder
/var/lib/transmission-daemon/
als needs to be owned by the correct user, so in addition to the commands stated in my question above:
sudo chown -R robots:robots /var/lib/transmission-daemon/
Replace the user "robots" and the group "robots" to the names used on your system.
edited May 6 '13 at 17:18
Testic
31
31
answered May 6 '13 at 13:03
larslars
101117
101117
add a comment |
add a comment |
Debian users may take a look at file: /lib/systemd/system/transmission-daemon.service to verify the required user is also set in that file.
Then, verify the home directory for that user because the configuration will then be read from ~/.config/transmission-daemon/
Hmm, debian isn't really on topic here...
– anonymous2
Jul 8 '16 at 13:49
add a comment |
Debian users may take a look at file: /lib/systemd/system/transmission-daemon.service to verify the required user is also set in that file.
Then, verify the home directory for that user because the configuration will then be read from ~/.config/transmission-daemon/
Hmm, debian isn't really on topic here...
– anonymous2
Jul 8 '16 at 13:49
add a comment |
Debian users may take a look at file: /lib/systemd/system/transmission-daemon.service to verify the required user is also set in that file.
Then, verify the home directory for that user because the configuration will then be read from ~/.config/transmission-daemon/
Debian users may take a look at file: /lib/systemd/system/transmission-daemon.service to verify the required user is also set in that file.
Then, verify the home directory for that user because the configuration will then be read from ~/.config/transmission-daemon/
edited Jul 8 '16 at 13:33
answered Jul 8 '16 at 13:19
user566058user566058
412
412
Hmm, debian isn't really on topic here...
– anonymous2
Jul 8 '16 at 13:49
add a comment |
Hmm, debian isn't really on topic here...
– anonymous2
Jul 8 '16 at 13:49
Hmm, debian isn't really on topic here...
– anonymous2
Jul 8 '16 at 13:49
Hmm, debian isn't really on topic here...
– anonymous2
Jul 8 '16 at 13:49
add a comment |
Empty file /etc/transmission-daemon/settings.json
invokes this error in my case.
rm /etc/transmission-daemon/settings.json solves problem.
Debug hinit:
sudo -u debian-transmission strace transmission-daemon -f --log-debug -g /etc/transmission-daemon/
New contributor
noname is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Empty file /etc/transmission-daemon/settings.json
invokes this error in my case.
rm /etc/transmission-daemon/settings.json solves problem.
Debug hinit:
sudo -u debian-transmission strace transmission-daemon -f --log-debug -g /etc/transmission-daemon/
New contributor
noname is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Empty file /etc/transmission-daemon/settings.json
invokes this error in my case.
rm /etc/transmission-daemon/settings.json solves problem.
Debug hinit:
sudo -u debian-transmission strace transmission-daemon -f --log-debug -g /etc/transmission-daemon/
New contributor
noname is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Empty file /etc/transmission-daemon/settings.json
invokes this error in my case.
rm /etc/transmission-daemon/settings.json solves problem.
Debug hinit:
sudo -u debian-transmission strace transmission-daemon -f --log-debug -g /etc/transmission-daemon/
New contributor
noname is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
noname is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 hours ago
nonamenoname
1
1
New contributor
noname is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
noname is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
noname is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f290943%2ftransmission-daemon-error-loading-working-config-file-user-priveliges%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown