==================================================================
Please DO NOT REPLY to this mail or send email to the developers
about this bug. Please follow-up to Bugzilla using this link:
https://bugs.contribs.org/show_bug.cgi?id=9556
Have you checked the Frequently Asked Questions (FAQ)?
http://wiki.contribs.org/SME_Server:Documentation:FAQ
Please also take the time to read the following useful guide:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
==================================================================
--- Comment #2 from Stefano Zamboni <[email protected]> ---
doh!
it seems I need more coffee.. yes, you're right, error_log exists
[root@fileserver ~]$ ll /var/log/httpd/ | grep error_log
lrwxrwxrwx 1 root root 45 2 giu 12:44 admin_error_log ->
/var/log/httpd/admin_error_log.20160602124426
-rw-r--r-- 1 root root 336 29 feb 01:12 admin_error_log.20160222011207
-rw-r--r-- 1 root root 336 1 mar 01:12 admin_error_log.20160229011206
-rw-r--r-- 1 root root 2786 8 mar 01:12 admin_error_log.20160301011205
-rw-r--r-- 1 root root 3414 12 mar 14:48 admin_error_log.20160308011206
-rw-r--r-- 1 root root 336 15 mar 01:12 admin_error_log.20160312144805
-rw-r--r-- 1 root root 336 22 mar 01:12 admin_error_log.20160315011207
-rw-r--r-- 1 root root 10919 26 mar 13:01 admin_error_log.20160322011206
-rw-r--r-- 1 root root 336 29 mar 01:12 admin_error_log.20160326130120
-rw-r--r-- 1 root root 336 1 apr 01:12 admin_error_log.20160329011206
-rw-r--r-- 1 root root 336 8 apr 01:12 admin_error_log.20160401011206
-rw-r--r-- 1 root root 336 15 apr 01:12 admin_error_log.20160408011206
-rw-r--r-- 1 root root 336 22 apr 01:12 admin_error_log.20160415011206
-rw-r--r-- 1 root root 336 29 apr 01:12 admin_error_log.20160422011205
-rw-r--r-- 1 root root 336 1 mag 01:12 admin_error_log.20160429011207
-rw-r--r-- 1 root root 336 8 mag 01:12 admin_error_log.20160501011205
-rw-r--r-- 1 root root 336 15 mag 01:12 admin_error_log.20160508011207
-rw-r--r-- 1 root root 4852 22 mag 01:12 admin_error_log.20160515011205
-rw-r--r-- 1 root root 336 29 mag 01:12 admin_error_log.20160522011207
-rw-r--r-- 1 root root 324 29 mag 18:21 admin_error_log.20160529011206
-rw-r--r-- 1 root root 336 1 giu 01:12 admin_error_log.20160529182027
-rw-r--r-- 1 root root 324 2 giu 12:48 admin_error_log.20160601011207
-rw-r--r-- 1 root root 258 2 giu 12:51 admin_error_log.20160602124426
lrwxrwxrwx 1 root root 44 1 giu 01:12 bkpc_error_log ->
/var/log/httpd/bkpc_error_log.20160601011207
-rw-r--r-- 1 root root 371 29 feb 01:12 bkpc_error_log.20160222011207
-rw-r--r-- 1 root root 371 1 mar 01:12 bkpc_error_log.20160229011206
-rw-r--r-- 1 root root 371 8 mar 01:12 bkpc_error_log.20160301011205
-rw-r--r-- 1 root root 760 15 mar 01:12 bkpc_error_log.20160308011206
-rw-r--r-- 1 root root 371 22 mar 01:12 bkpc_error_log.20160315011207
-rw-r--r-- 1 root root 826 29 mar 01:12 bkpc_error_log.20160322011206
-rw-r--r-- 1 root root 371 1 apr 01:12 bkpc_error_log.20160329011206
-rw-r--r-- 1 root root 371 8 apr 01:12 bkpc_error_log.20160401011206
-rw-r--r-- 1 root root 371 15 apr 01:12 bkpc_error_log.20160408011206
-rw-r--r-- 1 root root 371 22 apr 01:12 bkpc_error_log.20160415011206
-rw-r--r-- 1 root root 371 29 apr 01:12 bkpc_error_log.20160422011205
-rw-r--r-- 1 root root 371 1 mag 01:12 bkpc_error_log.20160429011207
-rw-r--r-- 1 root root 371 8 mag 01:12 bkpc_error_log.20160501011205
-rw-r--r-- 1 root root 371 15 mag 01:12 bkpc_error_log.20160508011207
-rw-r--r-- 1 root root 371 22 mag 01:12 bkpc_error_log.20160515011205
-rw-r--r-- 1 root root 371 29 mag 01:12 bkpc_error_log.20160522011207
-rw-r--r-- 1 root root 826 1 giu 01:12 bkpc_error_log.20160529011206
-rw-r--r-- 1 root root 748 2 giu 12:51 bkpc_error_log.20160601011207
lrwxrwxrwx 1 root root 39 2 giu 12:44 error_log ->
/var/log/httpd/error_log.20160602124426
-rw-r--r-- 1 root root 24626 29 feb 01:12 error_log.20160222011207
-rw-r--r-- 1 root root 3265 1 mar 01:12 error_log.20160229011206
-rw-r--r-- 1 root root 29898 8 mar 01:12 error_log.20160301011205
-rw-r--r-- 1 root root 23716 12 mar 13:35 error_log.20160308011206
-rw-r--r-- 1 root root 11142 15 mar 01:12 error_log.20160312144805
-rw-r--r-- 1 root root 32458 22 mar 01:12 error_log.20160315011207
-rw-r--r-- 1 root root 18278 26 mar 06:45 error_log.20160322011206
-rw-r--r-- 1 root root 6038 29 mar 01:12 error_log.20160326130120
-rw-r--r-- 1 root root 17493 1 apr 01:12 error_log.20160329011206
-rw-r--r-- 1 root root 26499 8 apr 01:12 error_log.20160401011206
-rw-r--r-- 1 root root 22862 15 apr 01:12 error_log.20160408011206
-rw-r--r-- 1 root root 24029 22 apr 01:12 error_log.20160415011206
-rw-r--r-- 1 root root 33751 29 apr 01:12 error_log.20160422011205
-rw-r--r-- 1 root root 7789 1 mag 01:12 error_log.20160429011207
-rw-r--r-- 1 root root 24005 8 mag 01:12 error_log.20160501011205
-rw-r--r-- 1 root root 27699 15 mag 01:12 error_log.20160508011207
-rw-r--r-- 1 root root 29136 22 mag 01:12 error_log.20160515011205
-rw-r--r-- 1 root root 23973 29 mag 01:12 error_log.20160522011207
-rw-r--r-- 1 root root 2723 29 mag 18:21 error_log.20160529011206
-rw-r--r-- 1 root root 11162 1 giu 01:12 error_log.20160529182027
-rw-r--r-- 1 root root 4710 2 giu 11:16 error_log.20160601011207
-rw-r--r-- 1 root root 5992 3 giu 14:37 error_log.20160602124426
I don't think I have a problem on my server, since I see the same on another
machine of mine:
[root@server log]# rpm -qa | grep fail2ban
smeserver-fail2ban-0.1.12-1.el6.fws.noarch
fail2ban-0.9.3-1.el6.1.noarch
Jun 1 01:12:08 server kernel: imklog 5.8.10, log source = /proc/kmsg started.
Jun 1 01:12:08 server rsyslogd: [origin software="rsyslogd" swVersion="5.8.10"
x-pid="12098" x-info="http://www.rsyslog.com";] start
Jun 1 01:12:08 server esmith::event[12056]: Avvio del logger di sistema: [ OK
]#015
Jun 1 01:12:08 server esmith::event[12056]: adjusting supervised httpd-e-smith
(sigusr1)
Jun 1 01:12:08 server esmith::event[12056]: adjusting supervised httpd-e-smith
(up)
Jun 1 01:12:08 server esmith::event[12056]: adjusting supervised httpd-admin
(sigusr1)
Jun 1 01:12:08 server esmith::event[12056]: adjusting supervised httpd-admin
(up)
Jun 1 01:12:08 server esmith::event[12056]:
adjust-services=action|Event|logrotate|Action|adjust-services|Start|1464736326
656598|End|1464736328 398627|Elapsed|1.74202
9
Jun 1 01:12:08 server esmith::event[12056]: Running event handler:
/etc/e-smith/events/logrotate/S98fail2ban-resume-logs
Jun 1 01:12:10 server esmith::event[12056]: Current monitored log file(s):
Jun 1 01:12:10 server esmith::event[12056]: `- /var/log/httpd/error_log
Jun 1 01:12:10 server esmith::event[12056]: Current monitored log file(s):
Jun 1 01:12:10 server esmith::event[12056]: `- /var/log/httpd/error_log
Jun 1 01:12:11 server esmith::event[12056]: Current monitored log file(s):
Jun 1 01:12:11 server esmith::event[12056]: `- /var/log/httpd/error_log
Jun 1 01:12:11 server esmith::event[12056]: Current monitored log file(s):
Jun 1 01:12:11 server esmith::event[12056]: `- /var/log/httpd/error_log
Jun 1 01:12:12 server esmith::event[12056]: Current monitored log file(s):
Jun 1 01:12:12 server esmith::event[12056]: `- /var/log/secure
Jun 1 01:12:12 server esmith::event[12056]: Current monitored log file(s):
Jun 1 01:12:12 server esmith::event[12056]: `- /var/log/secure
Jun 1 01:12:12 server esmith::event[12056]:
S98fail2ban-resume-logs=action|Event|logrotate|Action|S98fail2ban-resume-logs|Start|1464736328
398950|End|1464736332 497206
|Elapsed|4.098256
anyway, no need for any patch about path, you're right
--
You are receiving this mail because:
You are the QA Contact for the bug._______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
