transmission-daemon fails

Bug #1754419 reported by Ken Sharp
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Transmission
Fix Released
Undecided
Unassigned

Bug Description

Updating to 2.93-1ubuntu1~16.04.1ubuntu1 from the transmissionbt PPA causes transmission-daemon to fail.

-- Unit transmission-daemon.service has begun starting up.
Mar 08 17:01:43 homeserver systemd[3085]: transmission-daemon.service: Failed at step USER spawning /usr/bin/transmission-daemo
-- Subject: Process /usr/bin/transmission-daemon could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/bin/transmission-daemon could not be executed and failed.
--
-- The error number returned by this process is 3.
Mar 08 17:01:43 homeserver systemd[1]: transmission-daemon.service: Main process exited, code=exited, status=217/USER
Mar 08 17:01:43 homeserver systemd[1]: Failed to start Transmission BitTorrent Daemon.
-- Subject: Unit transmission-daemon.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit transmission-daemon.service has failed.
--
-- The result is failed.

This first problem is resolved by changing User from transmission to debian-transmission - the user is incorrect.

This does not get the daemon working, however:

$ sudo apt -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up transmission-daemon (2.93-1ubuntu1~16.04.1ubuntu1) ...
Job for transmission-daemon.service failed because a timeout was exceeded. See "systemctl status transmission-daemon.service" and "journalctl -xe" for details.
invoke-rc.d: initscript transmission-daemon, action "start" failed.
● transmission-daemon.service - Transmission BitTorrent Daemon
   Loaded: loaded (/lib/systemd/system/transmission-daemon.service; enabled; vendor preset: enabled)
   Active: failed (Result: timeout) since Thu 2018-03-08 17:07:23 GMT; 24ms ago
  Process: 3448 ExecStart=/usr/bin/transmission-daemon -f --log-debug (code=exited, status=0/SUCCESS)
 Main PID: 3448 (code=exited, status=0/SUCCESS)

Mar 08 17:07:23 homeserver transmission-daemon[3448]: [2018-03-08 17:07:23.013] Port Forwarding Stopped (port-forwarding.c:180)
Mar 08 17:07:23 homeserver transmission-daemon[3448]: [2018-03-08 17:07:23.013] Port Forwarding (NAT-PMP) readnatpmpres...c:75)
Mar 08 17:07:23 homeserver transmission-daemon[3448]: [2018-03-08 17:07:23.013] Port Forwarding (UPnP) Stopping port fo...:270)
Mar 08 17:07:23 homeserver transmission-daemon[3448]: [2018-03-08 17:07:23.013] Port Forwarding State changed from "For...c:92)
Mar 08 17:07:23 homeserver transmission-daemon[3448]: [2018-03-08 17:07:23.014] RPC Server Stopped listening on 0.0.0.0...:874)
Mar 08 17:07:23 homeserver systemd[1]: Failed to start Transmission BitTorrent Daemon.
Mar 08 17:07:23 homeserver systemd[1]: transmission-daemon.service: Unit entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package transmission-daemon (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 transmission-daemon
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have no idea what the problem is at this point.

Tags: artful xenial
Revision history for this message
Ken Sharp (kennybobs) wrote :

E-mailed transmissionbt list.

affects: transmission (Ubuntu) → transmission
Revision history for this message
Ken Sharp (kennybobs) wrote :

Looks like it's already been noticed.
https://lists.launchpad.net/transmissionbt/msg00007.html

tags: added: artful
Revision history for this message
Ken Sharp (kennybobs) wrote :
Changed in transmission:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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