If you are currently working on cronjobs: I had more than one time on different on-premise machines the problem that /…/log/asterisk/fail2ban…log can not be rotated after whatever 7 or 10 days because of the “t” fixed in the access rights. Therefore I always need to chmod 640 /…fail2ban_yyyymmtt.log first manually to delete the “t” first. However, just creates an error-mail for not correct rotation meaning deletion is these cases. An naturally can’t delete the old fail2ban-log.
1 Like
It looks a bug when we are running fwconsole restart.
Need to run fwconsole chmod at the end.
Until we will fixe this issue, do that please.
I’m able to reproduce, So, I’m trying to figure out why and the time to fix it…
Thanks Franck. I was not aware of this specific command and will use it meanwhile.
This issue is present on FreePBX 14, 15, and 16
I found where the issue comes from.
I will fixe it immediately, just wait a while before to be published. 
3 Likes
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.