Bug 1007520

Summary:	denyhosts.service operation timed out. Terminating.
Product:	[Fedora] Fedora	Reporter:	Daniel <daniel>
Component:	denyhosts	Assignee:	Jason Tibbitts <j>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	bloch, dennis, j, opensource, ralf
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1129747 (view as bug list)		Environment:
Last Closed:	2014-12-14 16:41:02 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 Daniel 2013-09-12 16:27:52 UTC

Description of problem:

On a server I installed the denyhosts package and enabled the service with
/bin/systemctl enable denyhosts.service.
In order to test the service before reboot I started with command: /bin/systemctl start denyhosts.service and got the following error messages:

systemd[1]: denyhosts.service operation timed out. Terminating.
systemd[1]: Unit denyhosts.service entered failed state.
systemd[1]: Failed to start SSH log watcher.
systemd[1]: Unit denyhosts.service entered failed state.

I tried to restart it (even with a reboot) via 
/bin/systemctl restart denyhosts.service and got the same error messages.
Stracing the whole thing brought no results.

The solution to the problem was, to start the denyhosts service without using systemd: /usr/bin/denyhosts.py --daemon --config=/etc/denyhosts.conf.
This took a pretty long time but went through without any error messages.

After this I could even start, stop and restart denyhosts via systemd with the above mentioned commands.

So this may be rather a systemd bug than a denyhosts bug.

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

denyhosts-2.6-28.fc19.noarch

Comment 1 Ralf Baechle 2014-08-13 15:03:36 UTC

I'm also observing the exact same issue on Fedora 20.

Comment 2 Till Maas 2014-12-14 16:41:02 UTC


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