Can't enable logging when starting Deluge Daemon

General support for problems installing or using Deluge
CervantesX
New User
New User
Posts: 3
Joined: Wed Jan 06, 2021 3:33 am

Can't enable logging when starting Deluge Daemon

Postby CervantesX » Wed Jan 06, 2021 3:55 am

Hi,
I'm on a Raspberry Pi 4B running linux.

I've created a deluged.service file in /etc/systemd/system to automatically start the service.
It seems to work, but I'm having trouble transferring the completed torrents to a mapped network drive (defined in fstab)
I'd like to enable error logging. However, when I change the ExecStart line from:

Code: Select all

ExecStart=/usr/bin/deluged -d


to:

Code: Select all

ExecStart=/usr/bin/deluged -d -l /var/log/deluge/daemon.log -L debug --logrotate


the daemon does not start. I've tried sudo systemctl restart deluged after a reload and the service does not restart.

I'm pretty much a noob with linux so I'm not sure where to go from here. The logging directory is writable (chown 755'd it), the service comes right up again if I remove the logging arguments. Does anyone have any insight?

My end goal is the headless Pi running the Deluged thin client, accessed via an Android app and saving completed files to the mounted SMB share.

shamael
Compulsive Poster
Compulsive Poster
Posts: 623
Joined: Sat Oct 08, 2016 9:28 am

Re: Can't enable logging when starting Deluge Daemon

Postby shamael » Wed Jan 06, 2021 1:42 pm

Hi,

Seems fine except the "logrotate" I never used. May you try to remove it?
have your tried as root ("sudo bash" if needed)?

Please post your complete unit and daemon version too, may be useful

benba
Member
Member
Posts: 21
Joined: Mon Oct 28, 2019 10:09 am

Re: Can't enable logging when starting Deluge Daemon

Postby benba » Wed Jan 06, 2021 4:40 pm

systemctl status deluged

or

journaltctl -u deluged -e

paste output

CervantesX
New User
New User
Posts: 3
Joined: Wed Jan 06, 2021 3:33 am

Re: Can't enable logging when starting Deluge Daemon

Postby CervantesX » Wed Jan 06, 2021 10:18 pm

Removing logrotate didn't seem to make a difference. However, looking through more error logs I see it was getting kicked out as an invalid argument. It's valid for command line usage though. Weird.

How do I find my unit and daemon version?

shamael wrote:Hi,

Seems fine except the "logrotate" I never used. May you try to remove it?
have your tried as root ("sudo bash" if needed)?

Please post your complete unit and daemon version too, may be useful

CervantesX
New User
New User
Posts: 3
Joined: Wed Jan 06, 2021 3:33 am

Re: Can't enable logging when starting Deluge Daemon

Postby CervantesX » Wed Jan 06, 2021 11:39 pm

journalctl -u deluged -e was what I needed to see the error, which was that I'd called the logging directory "deluged" but had the daemon pointing to "deluge". :?

Now that I've got that cleared up, I ran a torrent and checked the log and saw my error was "Permission denied" when trying to access the share to move the completed file to the NAS.

I have a Synology NAS, and I've set up a Samba share. I've created users on the NAS (one for pi and one for deluge).
However, when I mount the drive from FSTAB with

Code: Select all

//192.168.1.2/video /mnt/NAS cifs,_netdev,auto,user=deluged,password=password,vers=3.0,uid=118,gid=126,rw,sec=ntlm


it still shows the mounted directories as owned by ROOT with nothing else allowed to write to them, and so far my efforts to change that have hit a wall. The UID and GID are that of the deluge account.

Does anyone have a suggestion of where I can go from here, to get write permissions for the 'deluge' user working correctly?


benba wrote:systemctl status deluged

or

journaltctl -u deluged -e

paste output

benba
Member
Member
Posts: 21
Joined: Mon Oct 28, 2019 10:09 am

Re: Can't enable logging when starting Deluge Daemon

Postby benba » Thu Jan 07, 2021 2:06 pm

with user=deluged i think the mount point have to be owned by this user;

Code: Select all

sudo chown /mnt/NAS deluged


or

Code: Select all

su -
chown /mnt/NAS deluged


Return to “Support”

Who is online

Users browsing this forum: Baidu [Spider] and 12 guests