FS#63927 - [fail2ban] Systemd warning about legacy PIDFile directory

Attached to Project: Community Packages
Opened by wangqr (wangqr) - Thursday, 26 September 2019, 20:40 GMT
Last edited by freswa (frederik) - Wednesday, 26 February 2020, 22:53 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
There are repeated warnings in journalctl about PIDFile= references a path below legacy directory /var/run/ if I run fail2ban as systemd service. In PKGBUILD I see a patch which might be related to this issue, but the link is broken (the link target is blank and cannot pass the sha512sums test).

See also:

https://github.com/fail2ban/fail2ban/commit/7f0bba94ba895561c98ed32692494da9fba565ac
https://github.com/fail2ban/fail2ban/commit/d5a5efcd5af272372153e86436d7c8cde2ddf66d


Additional info:
* package version(s)
fail2ban 0.10.4-1

* config and/or log files etc.
systemd[1]: /usr/lib/systemd/system/fail2ban.service:13: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.

* link to upstream bug report, if any
https://github.com/fail2ban/fail2ban/pull/2174

Steps to reproduce:
Install fail2ban, start the systemd service, check journalctl -e
This task depends upon

Closed by  freswa (frederik)
Wednesday, 26 February 2020, 22:53 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.10.5-1

Loading...