In shipped denyhosts.conf, the pid file is set as: LOCK_FILE = /var/run/denyhosts.pid But in systemd service file, it is named like: PIDFile=/var/run/denyhosts So systemd awaits forever for the PID file to appear... Besides that, in one of my systems journalctl happened to not being redirected to syslog, so auth.log got no log for failed ssh login attempts. Is there an easy way for this package on install to check that journal is correctly forwarded to syslog ? Or perhaps denyhosts can read a journald/systemd log instead of auth.log ? TIA
It looks like the systemd unit bug is corrected in version 3.1 upstream (cauldron has 3.0). Could we have it updated ? Thanks.
CC: (none) => jamagallon
(In reply to JA Magallón from comment #1) > It looks like the systemd unit bug is corrected in version 3.1 upstream > (cauldron has 3.0). > Could we have it updated ? > > Thanks. Assigning to the registered maintainer.
Keywords: (none) => TriagedCC: (none) => marja11Assignee: bugsquad => cooker
(In reply to Juan Magallon from comment #0) > In shipped denyhosts.conf, the pid file is set as: > > LOCK_FILE = /var/run/denyhosts.pid > > But in systemd service file, it is named like: > > PIDFile=/var/run/denyhosts > > So systemd awaits forever for the PID file to appear... Sorry for the long delay. Should be fixed in Cauldron. Just pushed the new version. > Besides that, in one of my systems journalctl happened to not being > redirected to syslog, so auth.log got no log for failed ssh login attempts. You need to start rsyslog. It should be installed as a dependency, but you need to enable it.
Status: NEW => ASSIGNEDSee Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=23551
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2018-0154.html
Resolution: (none) => FIXEDStatus: ASSIGNED => RESOLVED