Ubuntu
deluge package

deluged systemd unit doesn't fail if configuration file isn't accessible

Bug #1582237 reported by Karl-Philipp Richter on 2016-05-16

6

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	deluge (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

The log file `/var/log/deluge/deluge-all.log` reveals `[WARNING ] 15:27:09 config:361 Unable to open config file /var/lib/deluge/.config/deluge/web.conf: [Errno 13] Keine Berechtigung: '/var/lib/deluge/.config/deluge/web.conf'`, but the status of the `systemd` unit is `active` which doesn't make sense because one wouldn't want `deluge` to run with values which aren't configured or be in an unpredicatable state.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: deluged 1.3.12-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon May 16 15:27:57 2016
InstallationDate: Installed on 2015-04-20 (391 days ago)
InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2)
PackageArchitecture: all
ProcEnviron:
TERM=screen.xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: deluge
UpgradeStatus: Upgraded to xenial on 2016-03-03 (73 days ago)
mtime.conffile..etc.init.d.deluged: 2016-05-16T15:26:05.696954

Tags:

Revision history for this message

Karl-Philipp Richter (krichter722) wrote on 2016-05-16:

#1

Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (109.7 KiB, text/plain; charset="utf-8")
modified.conffile..etc.init.d.deluged.txt Edit (3.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Cas (calumlind) wrote on 2016-05-16:

#2

That is a warning nor an error. And you will normally get when first starting deluge-web without any existing config files, it will be created upon shutdown and you will not see it again.

Revision history for this message

Cas (calumlind) wrote on 2016-05-16:

#3

Just to add that a systemd unit would stop if Deluge raised an actual error for inaccessible config so this is not an issue.

Changed in deluge (Ubuntu):
status:	New → Invalid

Revision history for this message

Karl-Philipp Richter (krichter722) wrote on 2017-03-08:

#4

> That is a warning nor an error. And you will normally get when first starting deluge-web without any existing config files, it will be created upon shutdown and you will not see it again.

I'd say that if the application can't run without the required file, it's a severe/actual error because it's no functional/operational. Why is the file not created at start instead of shutdown? The message should contain the information given here.

Revision history for this message

Karl-Philipp Richter (krichter722) wrote on 2017-03-08:

#5

> Just to add that a systemd unit would stop if Deluge raised an actual error for inaccessible config so this is not an issue.

Unfortunately, it does not (see http://dev.deluge-torrent.org/ticket/2988#ticket), but that's most likely a bug.

Revision history for this message

Cas (calumlind) wrote on 2017-03-08:

#6

> I'd say that if the application can't run without the required file, it's a severe/actual error because it's no functional/operational. Why is the file not created at start instead of shutdown? The message should contain the information given here.

It is running, you said so yourself. The values are stored in memory while running and default values are generated from code if the file is missing so the warning log can be ignored when first starting. The values are then written to file on shutdown.

As you mention in that ticket, you are using init.d so it is not applicable.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

deluge-bugs #2988 Edit

Bug watches keep track of this bug in other bug trackers.