Bug 1302753 - bad directory search
Summary: bad directory search
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: fail2ban
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-28 14:34 UTC by la_antorcha_guia
Modified: 2016-01-29 20:53 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-29 20:53:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description la_antorcha_guia 2016-01-28 14:34:17 UTC
Description of problem:
customisation.local:
apache_error_log = /var/log/httpd/*/*/*error*

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


How reproducible:
apache_error_log = /var/log/httpd/*/*/*error* on config file. The path should have "/*/", in other case fail2ban works.

Steps to Reproduce:
1. configure multiple directories search expression
2. run fail2ban
3. fail to start: ERROR  No file(s) found for glob

Actual results:
exits with ERROR  No file(s) found for glob

Expected results:
work with "/*/*/.../*file*" expressions

Additional info:
fail2ban-0.9.3-1.fc23.noarch

Comment 1 Orion Poplawski 2016-01-29 20:53:05 UTC
I'm sorry, I really don't understand what problem you are having.  I think it may be because your customization file needs to be named jail.local with:

[DEFAULT]
apache_error_log = /var/log/httpd/*/*/*error*

[apache-auth]
enabled = true

then:

# mkdir -p /var/log/httpd/{a,b,c,d}/{a,b,c,d}
# touch /var/log/httpd/{a,b,c,d}/{a,b,c,d}/error{1,2,3,4}
# systemctl start fail2ban
# fail2ban-client get apache-auth logpath
Current monitored log file(s):
|- /var/log/httpd/a/a/error1
|- /var/log/httpd/a/a/error2
|- /var/log/httpd/a/a/error3
|- /var/log/httpd/a/a/error4
|- /var/log/httpd/a/b/error1
....


Looks like I also had an issue with selinux-policy-3.13.1-152.fc23, but updating to 3.13.1-158.2.fc23 seemed to clear that up.  So maybe that was an issue for you too.


Note You need to log in before you can comment on or make changes to this bug.