Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 9815 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Getting error AH00646 (Error wrting to logger) in WAF log

Bernhard Frei

Greetings, 

I regularly get error entries in our WAF log looking like this:

2017:07:06-09:18:51 bchzhutm01 httpd[32187]: [log_config:warn] [pid 32187:tid 3752549232] (32)Broken pipe: [client 2.166.63.131:61966] AH00646: Error writing to |/bin/logger -p local1.info -t httpd

Any idea what this means or how to fix it? It's logged for various client IP addresses.

 

Thanks,

Bernhard

 



This thread was automatically locked due to age.
Parents
  • 0

    Hi, Berhnard, and welcome to the UTM Community!

    That's a line from the HTTP daemon log, not the WAF log.  I suspect it has to do with the User Portal rather than WebAdmin.  What difficulty is associated with this?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Hi Bob,

    Thanks for getting back to me. I had just noticed quite a number of those errors in the WAF log (not the httpd log, I double-checked) at the time we started using the WAF for MS Exchange. They did not seem to have any effects on the functionality of the UTM.

    Strange thing is, the errors have completely stopped somewhen on July 7, maybe after changing some WAF settings or Exception rules. 

    Anyway, since the problem has seemingly gone away, I guess there is no need to do any further digging.

     

    Best regards

    Bernhard

Reply
  • 0 in reply to BAlfson

    Hi Bob,

    Thanks for getting back to me. I had just noticed quite a number of those errors in the WAF log (not the httpd log, I double-checked) at the time we started using the WAF for MS Exchange. They did not seem to have any effects on the functionality of the UTM.

    Strange thing is, the errors have completely stopped somewhen on July 7, maybe after changing some WAF settings or Exception rules. 

    Anyway, since the problem has seemingly gone away, I guess there is no need to do any further digging.

     

    Best regards

    Bernhard

Children
No Data
Unfiltered HTML