WAF stops processing requests

Hello there,

Thank you for contacting the Sophos Community.

The customer stopped responding to the case, so it went cold, however, there was a suspected ID attached to the case with ID NC-66112 unfortunately the customer also stopped responding.

If you are having issues with WAF, please open a support case and send me the Case ID so I can left a note there. 

Please submit any output you have for

/var/cores

ATOP utilization

garner.log

reverseproxy.log

csc.log (debug mode csc custom debug)

 error_log.log

syslog.log

Regards,

Case: 04102921

Hello,

Thank you for the Case ID, I have left a note for the engineer to check your logs.

Regards,

Awaiting responses from support, to get the older logs, or we must wait until the issue happens again to pull the reverseproxy logs while the issue is happening. Please keep this post open, I will reply with the answer when we discover it.

Still working with support. The sporadic nature of the issue is making this a lengthy process. I will keep this post open until we have a solution or have identified the flaw.

If others have the same issue, please leave a comment.

Does anyone else have this problem?

The support case was closed, because they have a policy to close cases within a certain amount of time. Waiting for this anomaly to happen again and will open another case.

The support and development teams will not investigate this without others coming forward with this issue. Please sound off if you are having this issue.

WAF is now not responding, raising a new critical case. However I can only keep this state for 30 minutes tops, as this is a live system and I am going to have to stop and restart the WAF service to get back to work.

New Case

04220992

We have had this happen today and constantly over the logs past year. Every time we open a case, they can’t resolve it because it doesn’t say anything in the logs that there is a problem, but there is. We have 7 firewalls and 4 of the 7 show this problem.