transmission-daemon ignoring settings.json
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
2
down vote
favorite
Since I upgraded my ubuntu server installation from 16.04 to 16.10, the transmission-daemon service seems to be ignoring settings.json
.
The symptom is that the web interface gives me:
403: Forbidden
Unauthorized IP Address.
Either disable the IP address whitelist or add your address to it.
If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.
but in /etc/transmission-daemon/settings.json
we have, unchanged from before the upgrade:
"rpc-whitelist": "127.0.0.1,192.168.23.*",
"rpc-whitelist-enabled": true,
/var/lib/transmission-daemon/.config/transmission-daemon/settings.json
also points to /etc/transmission-daemon/settings.json
:
jast@achilles:/etc/transmission-daemon$ sudo ls -l /var/lib/transmission-daemon/.config/transmission-daemon/
lrwxrwxrwx 1 root root 38 Sep 5 12:56 settings.json -> /etc/transmission-daemon/settings.json
syslog after doing service transmission-daemon restart
(I think it should usually be also tellung me what ips it adds to the whitelist:
Jan 7 13:16:37 achilles transmission-daemon[4087]: Closing transmission session... done.
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84)
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95)
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84)
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95)
So where is it trying to get its config from now?
server services transmission
add a comment |Â
up vote
2
down vote
favorite
Since I upgraded my ubuntu server installation from 16.04 to 16.10, the transmission-daemon service seems to be ignoring settings.json
.
The symptom is that the web interface gives me:
403: Forbidden
Unauthorized IP Address.
Either disable the IP address whitelist or add your address to it.
If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.
but in /etc/transmission-daemon/settings.json
we have, unchanged from before the upgrade:
"rpc-whitelist": "127.0.0.1,192.168.23.*",
"rpc-whitelist-enabled": true,
/var/lib/transmission-daemon/.config/transmission-daemon/settings.json
also points to /etc/transmission-daemon/settings.json
:
jast@achilles:/etc/transmission-daemon$ sudo ls -l /var/lib/transmission-daemon/.config/transmission-daemon/
lrwxrwxrwx 1 root root 38 Sep 5 12:56 settings.json -> /etc/transmission-daemon/settings.json
syslog after doing service transmission-daemon restart
(I think it should usually be also tellung me what ips it adds to the whitelist:
Jan 7 13:16:37 achilles transmission-daemon[4087]: Closing transmission session... done.
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84)
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95)
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84)
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95)
So where is it trying to get its config from now?
server services transmission
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Since I upgraded my ubuntu server installation from 16.04 to 16.10, the transmission-daemon service seems to be ignoring settings.json
.
The symptom is that the web interface gives me:
403: Forbidden
Unauthorized IP Address.
Either disable the IP address whitelist or add your address to it.
If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.
but in /etc/transmission-daemon/settings.json
we have, unchanged from before the upgrade:
"rpc-whitelist": "127.0.0.1,192.168.23.*",
"rpc-whitelist-enabled": true,
/var/lib/transmission-daemon/.config/transmission-daemon/settings.json
also points to /etc/transmission-daemon/settings.json
:
jast@achilles:/etc/transmission-daemon$ sudo ls -l /var/lib/transmission-daemon/.config/transmission-daemon/
lrwxrwxrwx 1 root root 38 Sep 5 12:56 settings.json -> /etc/transmission-daemon/settings.json
syslog after doing service transmission-daemon restart
(I think it should usually be also tellung me what ips it adds to the whitelist:
Jan 7 13:16:37 achilles transmission-daemon[4087]: Closing transmission session... done.
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84)
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95)
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84)
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95)
So where is it trying to get its config from now?
server services transmission
Since I upgraded my ubuntu server installation from 16.04 to 16.10, the transmission-daemon service seems to be ignoring settings.json
.
The symptom is that the web interface gives me:
403: Forbidden
Unauthorized IP Address.
Either disable the IP address whitelist or add your address to it.
If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.
but in /etc/transmission-daemon/settings.json
we have, unchanged from before the upgrade:
"rpc-whitelist": "127.0.0.1,192.168.23.*",
"rpc-whitelist-enabled": true,
/var/lib/transmission-daemon/.config/transmission-daemon/settings.json
also points to /etc/transmission-daemon/settings.json
:
jast@achilles:/etc/transmission-daemon$ sudo ls -l /var/lib/transmission-daemon/.config/transmission-daemon/
lrwxrwxrwx 1 root root 38 Sep 5 12:56 settings.json -> /etc/transmission-daemon/settings.json
syslog after doing service transmission-daemon restart
(I think it should usually be also tellung me what ips it adds to the whitelist:
Jan 7 13:16:37 achilles transmission-daemon[4087]: Closing transmission session... done.
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84)
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95)
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84)
Jan 7 13:16:38 achilles transmission-daemon[5025]: [2017-01-07 13:16:38.552] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95)
So where is it trying to get its config from now?
server services transmission
server services transmission
asked Jan 7 '17 at 12:22
Justin Kaeser
11316
11316
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
7
down vote
accepted
After updating 16.04 LTS, systemd would not load my config file for transmission-daemon from the correct location.
I found a workaround at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734467
I tried the drop-in *.conf file in /etc/systemd/system/transmission.service.d/ to override ExecStart. However, using ps -ef | grep transmission I could see the wrong config location was still being used after reloads and restarts.
Reluctantly, I edited
/lib/systemd/system/transmission-daemon.service
to include the correct path by appending
-g /etc/transmission-daemon
to the ExecStart line.
[Unit]
Description=Transmission BitTorrent Daemon
After=network.target
[Service]
User=debian-transmission
Type=notify
ExecStart=/usr/bin/transmission-daemon -f --log-error -g /etc/transmission-daemon
ExecReload=/bin/kill -s HUP $MAINPID
[Install]
WantedBy=multi-user.target
add a comment |Â
up vote
0
down vote
I've got the same issue since I installed on 16.04, while it was previously working fine on 14.04.
Check this out: http://www.htpcguides.com/install-transmission-bittorrent-client-on-ubuntu-15-x/ - steps #4, #5 and #6. Basically you need to modify the systemd script variables.
I know this is something that has changed from 14.04 to 16.04, so shouldn't apply to you if was working before, but is worth a try.
can you - for future reference in case the cited source is changed/removed - please add a relevant excerpt from your link?
â Phillip -Zyan K Lee- Stockmann
Feb 16 '17 at 14:52
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
7
down vote
accepted
After updating 16.04 LTS, systemd would not load my config file for transmission-daemon from the correct location.
I found a workaround at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734467
I tried the drop-in *.conf file in /etc/systemd/system/transmission.service.d/ to override ExecStart. However, using ps -ef | grep transmission I could see the wrong config location was still being used after reloads and restarts.
Reluctantly, I edited
/lib/systemd/system/transmission-daemon.service
to include the correct path by appending
-g /etc/transmission-daemon
to the ExecStart line.
[Unit]
Description=Transmission BitTorrent Daemon
After=network.target
[Service]
User=debian-transmission
Type=notify
ExecStart=/usr/bin/transmission-daemon -f --log-error -g /etc/transmission-daemon
ExecReload=/bin/kill -s HUP $MAINPID
[Install]
WantedBy=multi-user.target
add a comment |Â
up vote
7
down vote
accepted
After updating 16.04 LTS, systemd would not load my config file for transmission-daemon from the correct location.
I found a workaround at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734467
I tried the drop-in *.conf file in /etc/systemd/system/transmission.service.d/ to override ExecStart. However, using ps -ef | grep transmission I could see the wrong config location was still being used after reloads and restarts.
Reluctantly, I edited
/lib/systemd/system/transmission-daemon.service
to include the correct path by appending
-g /etc/transmission-daemon
to the ExecStart line.
[Unit]
Description=Transmission BitTorrent Daemon
After=network.target
[Service]
User=debian-transmission
Type=notify
ExecStart=/usr/bin/transmission-daemon -f --log-error -g /etc/transmission-daemon
ExecReload=/bin/kill -s HUP $MAINPID
[Install]
WantedBy=multi-user.target
add a comment |Â
up vote
7
down vote
accepted
up vote
7
down vote
accepted
After updating 16.04 LTS, systemd would not load my config file for transmission-daemon from the correct location.
I found a workaround at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734467
I tried the drop-in *.conf file in /etc/systemd/system/transmission.service.d/ to override ExecStart. However, using ps -ef | grep transmission I could see the wrong config location was still being used after reloads and restarts.
Reluctantly, I edited
/lib/systemd/system/transmission-daemon.service
to include the correct path by appending
-g /etc/transmission-daemon
to the ExecStart line.
[Unit]
Description=Transmission BitTorrent Daemon
After=network.target
[Service]
User=debian-transmission
Type=notify
ExecStart=/usr/bin/transmission-daemon -f --log-error -g /etc/transmission-daemon
ExecReload=/bin/kill -s HUP $MAINPID
[Install]
WantedBy=multi-user.target
After updating 16.04 LTS, systemd would not load my config file for transmission-daemon from the correct location.
I found a workaround at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734467
I tried the drop-in *.conf file in /etc/systemd/system/transmission.service.d/ to override ExecStart. However, using ps -ef | grep transmission I could see the wrong config location was still being used after reloads and restarts.
Reluctantly, I edited
/lib/systemd/system/transmission-daemon.service
to include the correct path by appending
-g /etc/transmission-daemon
to the ExecStart line.
[Unit]
Description=Transmission BitTorrent Daemon
After=network.target
[Service]
User=debian-transmission
Type=notify
ExecStart=/usr/bin/transmission-daemon -f --log-error -g /etc/transmission-daemon
ExecReload=/bin/kill -s HUP $MAINPID
[Install]
WantedBy=multi-user.target
answered Mar 8 '17 at 1:24
![](https://i.stack.imgur.com/fORtA.jpg?s=32&g=1)
![](https://i.stack.imgur.com/fORtA.jpg?s=32&g=1)
Jim Ladd
9613
9613
add a comment |Â
add a comment |Â
up vote
0
down vote
I've got the same issue since I installed on 16.04, while it was previously working fine on 14.04.
Check this out: http://www.htpcguides.com/install-transmission-bittorrent-client-on-ubuntu-15-x/ - steps #4, #5 and #6. Basically you need to modify the systemd script variables.
I know this is something that has changed from 14.04 to 16.04, so shouldn't apply to you if was working before, but is worth a try.
can you - for future reference in case the cited source is changed/removed - please add a relevant excerpt from your link?
â Phillip -Zyan K Lee- Stockmann
Feb 16 '17 at 14:52
add a comment |Â
up vote
0
down vote
I've got the same issue since I installed on 16.04, while it was previously working fine on 14.04.
Check this out: http://www.htpcguides.com/install-transmission-bittorrent-client-on-ubuntu-15-x/ - steps #4, #5 and #6. Basically you need to modify the systemd script variables.
I know this is something that has changed from 14.04 to 16.04, so shouldn't apply to you if was working before, but is worth a try.
can you - for future reference in case the cited source is changed/removed - please add a relevant excerpt from your link?
â Phillip -Zyan K Lee- Stockmann
Feb 16 '17 at 14:52
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I've got the same issue since I installed on 16.04, while it was previously working fine on 14.04.
Check this out: http://www.htpcguides.com/install-transmission-bittorrent-client-on-ubuntu-15-x/ - steps #4, #5 and #6. Basically you need to modify the systemd script variables.
I know this is something that has changed from 14.04 to 16.04, so shouldn't apply to you if was working before, but is worth a try.
I've got the same issue since I installed on 16.04, while it was previously working fine on 14.04.
Check this out: http://www.htpcguides.com/install-transmission-bittorrent-client-on-ubuntu-15-x/ - steps #4, #5 and #6. Basically you need to modify the systemd script variables.
I know this is something that has changed from 14.04 to 16.04, so shouldn't apply to you if was working before, but is worth a try.
answered Feb 16 '17 at 12:38
Alessandro.
1
1
can you - for future reference in case the cited source is changed/removed - please add a relevant excerpt from your link?
â Phillip -Zyan K Lee- Stockmann
Feb 16 '17 at 14:52
add a comment |Â
can you - for future reference in case the cited source is changed/removed - please add a relevant excerpt from your link?
â Phillip -Zyan K Lee- Stockmann
Feb 16 '17 at 14:52
can you - for future reference in case the cited source is changed/removed - please add a relevant excerpt from your link?
â Phillip -Zyan K Lee- Stockmann
Feb 16 '17 at 14:52
can you - for future reference in case the cited source is changed/removed - please add a relevant excerpt from your link?
â Phillip -Zyan K Lee- Stockmann
Feb 16 '17 at 14:52
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f869046%2ftransmission-daemon-ignoring-settings-json%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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