MikoPBX log files:
Asterisk
tail -f /storage/usbdisk1/mikopbx/log/asterisk/verbose tail -f /storage/usbdisk1/mikopbx/log/asterisk/error tail -f /storage/usbdisk1/mikopbx/log/asterisk/messages tail -f /storage/usbdisk1/mikopbx/log/asterisk/security_log
System
tail -f /storage/usbdisk1/mikobpx/log/system/messages
PHP
tail -f /storage/usbdisk1/mikobpx/log/php/error.log
Fail2ban
Under attack?
At times MikoPBX doesn’t pick up attack IP. You’ll see this by tailing the security log:
tail -f /storage/usbdisk1/mikopbx/log/asterisk/security_log
Then you can manually add an IP address to the fail2ban like so:
fail2ban-client set asterisk_security_log banip a.b.c.d
Fail2ban Logging and Database
On a MikoLogs to syslog, and database file is here:
/storage/usbdisk1/mikopbx/fail2ban/fail2ban.sqlite3
Fail2ban Process
6730 root 0:02 {fail2ban-server} /usr/bin/python /offload/rootfs/usr/bin/fail2ban-server --async -b -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x --loglevel INFO --logtarget SYSLOG --syslogsocket auto
Example
# tail -f /storage/usbdisk1/mikopbx/log/system/messages Mar 8 08:37:07 daemon.info fail2ban.jail[16404]: INFO Jail 'asterisk_ami' started Mar 8 08:37:08 daemon.notice fail2ban.actions[16404]: NOTICE [mikopbx-www] Restore Ban a.b.c.d Mar 8 08:37:08 daemon.notice fail2ban.actions[16404]: NOTICE [asterisk_security_log] Restore Ban a.b.c.d Mar 8 08:37:08 daemon.notice fail2ban.actions[16404]: NOTICE [asterisk_public] Restore Ban a.b.c.d Mar 8 08:37:08 daemon.notice fail2ban.actions[16404]: NOTICE [asterisk_security_log] Restore Ban a.b.c.d Mar 8 08:37:08 daemon.notice fail2ban.actions[16404]: NOTICE [asterisk_public] Restore Ban a.b.c.d