FS#48396 - [transmission-cli] transmission daemon 2.90 fails to start
Attached to Project:
Arch Linux
Opened by Dan McGee (toofishes) - Wednesday, 02 March 2016, 02:00 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Wednesday, 02 March 2016, 09:02 GMT
Opened by Dan McGee (toofishes) - Wednesday, 02 March 2016, 02:00 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Wednesday, 02 March 2016, 09:02 GMT
|
Details
Description:
The unit appears to be setup with `Type=Notify`, but no notification is happening, so it fails to start. $ sudo systemctl restart transmission <<< lots of time >>> Job for transmission.service failed because a timeout was exceeded. See "systemctl status transmission.service" and "journalctl -xe" for details. $ systemctl status transmission.service ● transmission.service - Transmission BitTorrent Daemon Loaded: loaded (/usr/lib/systemd/system/transmission.service; disabled; vendor preset: disabled) Active: failed (Result: timeout) since Tue 2016-03-01 19:57:52 CST; 18s ago Process: 28854 ExecStart=/usr/bin/transmission-daemon -f --log-error (code=exited, status=0/SUCCESS) Main PID: 28854 (code=exited, status=0/SUCCESS) Mar 01 19:56:18 galway systemd[1]: Stopped Transmission BitTorrent Daemon. Mar 01 19:56:18 galway systemd[1]: Starting Transmission BitTorrent Daemon... Mar 01 19:57:48 galway systemd[1]: transmission.service: Start operation timed out. Terminating. Mar 01 19:57:52 galway systemd[1]: Failed to start Transmission BitTorrent Daemon. Mar 01 19:57:52 galway systemd[1]: transmission.service: Unit entered failed state. Mar 01 19:57:52 galway systemd[1]: transmission.service: Failed with result 'timeout'. |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Wednesday, 02 March 2016, 09:02 GMT
Reason for closing: Fixed
Additional comments about closing: transmission 2.90-2
Wednesday, 02 March 2016, 09:02 GMT
Reason for closing: Fixed
Additional comments about closing: transmission 2.90-2