Bug 1014473

Summary:	denyhosts fails to start, for lack of /var/log/secure
Product:	[Fedora] Fedora	Reporter:	David Jansen <jansen>
Component:	denyhosts	Assignee:	Jason Tibbitts <j>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	dennis, j, karthic_babu, kraymond
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-11 10:13:24 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:

Description David Jansen 2013-10-02 07:38:55 UTC

Description of problem:
denyhosts in Fedora 20 alpha fails to start, because there is no /var/log/secure . no doubt due to the fact, that logging is handled through the systemd journal in stead of rsyslog

Version-Release number of selected component (if applicable):
denyhosts-2.6-29.fc20.noarch

How reproducible:

Steps to Reproduce:
1. install denyhosts
2. enable and start the denyhosts.service
3.

Actual results:

# systemctl status denyhosts.service
denyhosts.service - SSH log watcher
   Loaded: loaded (/usr/lib/systemd/system/denyhosts.service; enabled)
   Active: failed (Result: exit-code) since Wed 2013-10-02 09:22:11 CEST; 1min 11s ago
  Process: 22955 ExecStart=/usr/bin/denyhosts.py --daemon --config=/etc/denyhosts.conf (code=exited, status=1/FAILURE)
  Process: 22952 ExecStartPre=/bin/rm -f /run/lock/subsys/denyhosts (code=exited, status=0/SUCCESS)

Oct 02 09:22:10 eendracht.strw.leidenuniv.nl systemd[1]: Starting SSH log watcher...
Oct 02 09:22:11 eendracht.strw.leidenuniv.nl denyhosts.py[22955]: Can't read: /var/log/secure
Oct 02 09:22:11 eendracht.strw.leidenuniv.nl denyhosts.py[22955]: [Errno 2] No such file or directory: '/var/log/secure'
Oct 02 09:22:11 eendracht.strw.leidenuniv.nl denyhosts.py[22955]: Error deleting DenyHosts lock file: /var/lock/subsys/denyhosts
Oct 02 09:22:11 eendracht.strw.leidenuniv.nl denyhosts.py[22955]: [Errno 2] No such file or directory: '/var/lock/subsys/denyhosts'
Oct 02 09:22:11 eendracht.strw.leidenuniv.nl systemd[1]: denyhosts.service: control process exited, code=exited status=1
Oct 02 09:22:11 eendracht.strw.leidenuniv.nl systemd[1]: Failed to start SSH log watcher.
Oct 02 09:22:11 eendracht.strw.leidenuniv.nl systemd[1]: Unit denyhosts.service entered failed state.


Expected results:
a running denyhosts daemon

Additional info:

Comment 1 Kevin Raymond 2013-12-11 10:08:24 UTC

Issue still there

Comment 2 Kevin Raymond 2013-12-11 10:13:24 UTC


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

Comment 3 Karthic 2014-11-08 18:07:15 UTC

My server was attacked brutally and I was searching for a solution. I could not see a good solution except the whole thing sucks. I worked on my solution and would like to share with any one having the same issue and needs a solution.

I added a tactical command to /var/spool/cron/root to run every five minutes. It works now. Here is the command:

journalctl -u sshd --since=today | grep -e Failed >/var/log/secure

Comment 4 Jason Tibbitts 2014-11-12 01:09:25 UTC

It is, like, a whole lot easier to install a syslog daemon.