In deluge-web.service-3 it tries to use environment variables. ExecStart=/usr/bin/deluge-web -d -c ${DELUGED_HOME} ${DELUGED_OPTS} But deluge-web.service.conf actually defines them as Environment="DELUGE_WEB_HOME=/var/lib/deluge" "DELUGE_WEB_OPTS=" This causes deluge-web.service to fail. Reproducible: Always Steps to Reproduce: systemctl start deluge-web.service Expected Results: ExecStart=/usr/bin/deluge-web -d -c ${DELUGE_WEB_HOME} ${DELUGE_WEB_OPTS}
Hi, rn they change on the service file was made, but I still have exactly the same problem, like the Environment variable is not propagating to the service file.
(In reply to Lagu from comment #1) > Hi, rn they change on the service file was made, but I still have exactly > the same problem, like the Environment variable is not propagating to the > service file. Have you run "systemctl daemon-reload" to refresh the configuration?
Hi! this issue still happens, is because there is a mix of configuration files. Usually we would go to /etc/conf.d/deluge and update the env variables. But the variables are not loaded from there, are loaded from /etc/systemd/system/deluged.service.d/00gentoo.conf Also, I tried to add new params to that file for logs and deluged stops with feb 13 09:55:56 localhost.localdomain deluged[143047]: deluged: error: argument -p/--port: invalid int value: ' 58846 -L debug -l /var/lib/deluge/deluge.log' About the variables also happens with deluge-web
