Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1021223 - transmission-daemon starts too early
Summary: transmission-daemon starts too early
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: transmission
Version: el6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Adam Miller
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-10-20 13:02 UTC by Stephen Harris
Modified: 2020-11-30 15:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2020-11-30 15:57:32 UTC
Type: Bug

Attachments (Terms of Use)

Description Stephen Harris 2013-10-20 13:02:04 UTC
Description of problem:
/etc/init.d/transmission-daemon has a chkconfig start value of 16.  This means it starts before all filesystem (eg NFS) are fully mounted.  Users storing torrents on a network filesystem will find the torrent doesn't restart on reboot because the datafiles aren't available when the daemon starts

Version-Release number of selected component (if applicable):

How reproducible:
Always on reboot with NFS mounted torrent store

Steps to Reproduce:
1. Configure an NFS disk (eg /torrents)
2. Add a torrent with with this as the target directory.  Let run to completion
3. Reboot

Actual results:
Torrent is now flagged as "missing files"; user needs to "validate torrent files" and then "start" to let it seed again.

Expected results:
Torrent should automatically seed

Additional info:
Change "start" to 98 so that transmission-daemon is restarted after all filesystems are mounted.

Comment 1 Fedora Update System 2015-10-30 14:58:17 UTC
transmission-2.13-2.el6 has been submitted as an update to Fedora EPEL 6.

Comment 2 Fedora Update System 2015-11-01 16:47:28 UTC
transmission-2.13-2.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'yum --enablerepo=epel-testing update transmission'
You can provide feedback for this update here:

Comment 3 Ben Cotton 2020-11-05 16:46:41 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 4 Ben Cotton 2020-11-30 15:57:32 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.