Fail2ban logs filling up after update

We updated freepbx modules yesterday and now we find that the fail2ban logs are filling up constantly and we are observing high cpu usage. Can you assist me to why this is happening.

The fail2ban logs contents:

[2019-04-16 15:15:25] SECURITY[9795] res_security_log.c: SecurityEvent=“ChallengeSent”,EventTV=“2019-04-16T15:15:25.062-0500”,Severity=“Informational”,Service=“SIP”,EventVersion=“1”,AccountID=“253”,SessionID=“0x7fe9a0712b68”,LocalAddress=“IPV4/UDP/192.168.0.40/5060”,RemoteAddress=“IPV4/UDP/192.168.60.41/5060”,Challenge=“05d1a7e2”
[2019-04-16 15:15:25] SECURITY[9795] res_security_log.c: SecurityEvent=“SuccessfulAuth”,EventTV=“2019-04-16T15:15:25.084-0500”,Severity=“Informational”,Service=“SIP”,EventVersion=“1”,AccountID=“253”,SessionID=“0x7fe9a0712b68”,LocalAddress=“IPV4/UDP/192.168.0.40/5060”,RemoteAddress=“IPV4/UDP/192.168.60.41/5060”,UsingPassword=“1”
335",SessionID=“0x7fe9a0733038”,LocalAddress=“IPV4/UDP/192.168.0.40/5060”,RemoteAddress=“IPV4/UDP/192.168.60.11/5060”,UsingPassword=“1”
[2019-04-16 15:28:54] SECURITY[9795] res_security_log.c: SecurityEvent=“SuccessfulAuth”,EventTV=“2019-04-16T15:28:54.330-0500”,Severity=“Informational”,Service=“AMI”,EventVersion=“1”,AccountID=“admin”,SessionID=“0x7fe9b80e3188”,LocalAddress=“IPV4/TCP/0.0.0.0/5038”,RemoteAddress=“IPV4/TCP/127.0.0.1/42472”,UsingPassword=“0”,SessionTV=“2019-04-16T15:28:54.330-0500”

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.