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 bugzilla.redhat.com.

Bug 1442677

Summary: transmission-daemon did not get built with systemd notify support
Product: [Fedora] Fedora Reporter: Jonathan Briggs <zlynx>
Component: transmissionAssignee: Gwyn Ciesla <gwync>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: abdulkarimmemon, charles, gwync, helio, jspaleta, kumarpraveen.nitdgp, raghusiddarth, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-17 16:13:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonathan Briggs 2017-04-17 05:42:07 UTC
Description of problem:
The latest transmission-daemon (version transmission-daemon-2.92-4.fc25.x86_64) did not get built with systemd notify support, but its unit file requires it.

The effect is that it times out and restarts constantly. Well it does for me because I modified the unit file to restart on failure.

This is a regression because it used to work.

Please check the build log, see what went wrong with systemd auto detection, and rebuild it with a forced configure option instead of auto detect if necessary.

Apr 16 16:47:08 catbox.zlynx.org systemd[1]: transmission-daemon.service: Start operation timed out. Terminating.
Apr 16 16:47:13 catbox.zlynx.org systemd[1]: Failed to start Transmission BitTorrent Daemon.
Apr 16 16:47:13 catbox.zlynx.org systemd[1]: transmission-daemon.service: Unit entered failed state.
Apr 16 16:47:13 catbox.zlynx.org systemd[1]: transmission-daemon.service: Failed with result 'timeout'.
Apr 16 16:47:13 catbox.zlynx.org systemd[1]: transmission-daemon.service: Service hold-off time over, scheduling re
Apr 16 16:47:13 catbox.zlynx.org systemd[1]: Stopped Transmission BitTorrent Daemon.
Apr 16 16:47:13 catbox.zlynx.org systemd[1]: Starting Transmission BitTorrent Daemon...

Comment 1 Jonathan Briggs 2017-04-17 05:46:20 UTC
Ah ha!
From https://kojipkgs.fedoraproject.org//packages/transmission/2.92/4.fc25/data/logs/x86_64/build.log

checking for SYSTEMD_DAEMON... no

Comment 2 Jonathan Briggs 2017-04-17 05:49:52 UTC
Hey what's this? From https://kojipkgs.fedoraproject.org//packages/transmission/2.90/1.fc25/data/logs/x86_64/build.log

+ ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --disable-static --enable-utp --enable-daemon --enable-nls --enable-cli --enable-daemon --with-systemd-daemon --enable-external-natpmp

That one specified --with-systemd-daemon but 2.92 build did not.

Comment 3 Gwyn Ciesla 2017-04-17 16:13:33 UTC

*** This bug has been marked as a duplicate of bug 1442085 ***