** Description changed: [ Impact ] * Transmission fails to start out of the box due to a misconfigured systemd service. - * systemd waits for Transmission to notify it that it's ready, but Transmission does not do this as compiled in Ubuntu. - * systemd concludes that Transmission is stuck and restarts it. + * systemd waits for Transmission to notify it that it's ready, but Transmission does not do this as compiled in Ubuntu. + * systemd concludes that Transmission is stuck and restarts it until it hits the retry limit and gives up. * Changing Transmission's service type from `notify` to `simple` prevents systemd from waiting on a notification that will never arrive. [ Test Plan ] ```bash lxc launch ubuntu:noble nn-transmission-repro lxc exec nn-transmission-repro bash <<EOF apt update; apt install -y transmission-daemon # long hang, waiting for maximum retries systemctl is-active transmission-daemon # failed EOF ``` [ Where problems could occur ] * If Transmission genuinely becomes stuck, systemd won't be able to tell anymore. [ Original report follows ] Title: Transmission-daemon systemd service times out on fresh installations Description: On a fresh installation of Xubuntu/Ubuntu, the transmission-daemon fails to start via systemd due to a timeout. The daemon itself runs fine in the foreground, and manual execution shows no issues. It appears that the systemd service script is waiting for a readiness message that is no longer sent by the current version of Transmission. Steps to Reproduce: Install Xubuntu/Ubuntu on a fresh system. Install transmission-daemon using sudo apt install transmission-daemon. Modify the configuration in /etc/transmission-daemon/settings.json as needed. Start the service with sudo systemctl start transmission-daemon. Observe that the service fails with a timeout error. Expected Behavior: Transmission-daemon should start without timing out when launched via systemd. Actual Behavior: Transmission-daemon starts fine in the foreground but fails to report its status correctly to systemd, resulting in a timeout error. Workaround: Changing the systemd service file by adjusting the ExecStart command to explicitly specify the configuration directory (e.g., adding --config-dir /etc/transmission-daemon) and possibly setting Type=simple along with an increased TimeoutStartSec resolves the issue. Description: Ubuntu 24.04.2 LTS Release: 24.04 transmission-daemon: Installed: 4.0.5-1build5 Candidate: 4.0.5-1build5 Version table: *** 4.0.5-1build5 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: transmission-daemon 4.0.5-1build5 [modified: lib/systemd/system/transmission-daemon.service] ProcVersionSignature: Ubuntu 6.8.0-56.58-generic 6.8.12 Uname: Linux 6.8.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 25 20:39:26 2025 InstallationDate: Installed on 2025-03-26 (0 days ago) InstallationMedia: Xubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> SourcePackage: transmission UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.transmission-daemon.README.json: [deleted] modified.conffile..etc.transmission-daemon.settings.json: [deleted]
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2104214 Title: transmissions daemon not being detected as started up by systemctl even though it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/2104214/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
