Deluge Daemon ignoring ~/.config/deluge/core.conf file changes

[Garu94]

I killed deluged, edited the core.conf file and then started it again, but the downloading directory was not the one I set in the core.conf found in ~/.config/deluge/core.conf .
Where is deluged reading configuration info from?

Also, some of the changes I made seems to be lost after reboot of my Pi, why is this happening?

[mhertz]

Yes, deluge reads settings from there, _from_ the user deluge is running under, which often is deluge user e.g under arch-linux the deluge user's home dir is defined to be /srv/deluge, so if running deluge from its systemd service, the conf read is /srv/deluge/.config/deluge/core.conf. If running simply deluged from your user account, then same dir used(as your homedir).

Sorry, don't know about your other issue.

[Garu94]

I set up the deluged systemd service to be launched as pi, but still it seems like not to read the core.conf from /home/pi/.config/deluge/core.conf though

[mhertz]

How about when running 'sudo -u pi deluged' ?

[Garu94]

Still the same result, here my core.conf file:
https://imgur.com/a/gYyNyZx

and when I try to ls /media/usb1/shares/torrents/downloading, the torrent that is now being downloaded is not shown, while I can find it in /home/pi/Downloads

[mhertz]

Strange.

To see what deluged has download_location set/read as:

Code: Select all

sudo -u pi deluge-console config download_location

You can also set the setting from consoleUI directly, instead of editing core.conf, but should be exactly the same as editing core.conf under correct dir/path with closed daemon, but nonetheless:

Code: Select all

sudo -u pi deluge-console config -s download_location /media/usb1/shares/torrents/downloading

I'd recommend enabling debug-logging to further investigate what's going on here:

Code: Select all

sudo -u pi deluged -L debug -l deluged.log

(You don't need the preceding 'sudo -u pi ' part if already running under pi user btw.)

Also, make sure a plugin not interferring e.g. labelplus has own download settings and auto-labeling etc, but a debug-log will also reveal that. To see enabled plugins:

Code: Select all

sudo -u pi deluge-console plugin -s

[Garu94]

I logged as user pi, and running

Code: Select all

deluged
deluge-console config download_location

I confirm that it show as output

Code: Select all

/home/pi/Downloads

While core.conf in /home/pi/.config/deluge/core.conf is the one I showed before. This is really weird to me
Also the move_completed flag (or how is it called) seems to be ignored, so I would say the whole .conf file is ignored.

[mhertz]

Running 'deluged -L debug -l deluged.log' will reveal in deluged.log file which/where core.conf it's pulling settings from.

[Garu94]

https://imgur.com/a/Uyts5DM
This is the output, apparently it seems that deluged is not able to read /home/pi/.config/deluge/core.conf and it takes default values. What do you think could be the problem?

[mhertz]

Either permission issue e.g run chmod 777 on config, or, you've broken the Json format, which is easy to do e.g missing a space etc. For the latter, then rename core.conf to e.g core-bak.conf with deluged stopped, then start deluged shortly and close it again afterwards, which will generate a new core.conf where you(carefully) edit download_location etc, or simply use deluge-console which avoids such issues.