Thread Info
  • State Suggested Answer
  • +4 person also asked this people also asked this
  • Locked Locked
  • Replies 28 replies
  • Answers 2 answers
  • Subscribers 11 subscribers
  • Views 48507 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

Error Filling http.log directory in UTM 9

KevinNadin

I have a ticket open with Sophos Support, but thought I would put it out to the support community also. After the latest update (9.510-5), we started filling our http.log file with the following error:

2018:08:30-08:44:20 ansophos httpproxy[5511]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x3539ca00" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"

Has anyone seen this before? I have removed he UTM from the domain and rejoined it but it still has not resolved the issue. 



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

    Same issue after update to 9.510-5. Any news or solution?

     

     
    2018:10:23-14:46:38 xxxx httpproxy[7622]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x8a00600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
    2018:10:23-14:46:38 xxxx httpproxy[7622]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x8a00600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
    2018:10:23-14:46:38 xxxx httpproxy[7622]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x8a00600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
    2018:10:23-14:46:38 xxxx httpproxy[7622]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x8a00600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
    2018:10:23-14:46:38 xxxx httpproxy[7622]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x8a00600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
    2018:10:23-14:46:38 xxxx httpproxy[7622]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x8a00600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
     
Reply
  • 0

    Same issue after update to 9.510-5. Any news or solution?

     

     
    2018:10:23-14:46:38 xxxx httpproxy[7622]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x8a00600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
    2018:10:23-14:46:38 xxxx httpproxy[7622]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x8a00600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
    2018:10:23-14:46:38 xxxx httpproxy[7622]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x8a00600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
    2018:10:23-14:46:38 xxxx httpproxy[7622]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x8a00600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
    2018:10:23-14:46:38 xxxx httpproxy[7622]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x8a00600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
    2018:10:23-14:46:38 xxxx httpproxy[7622]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x8a00600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
     
Children
  • 0 in reply to tryf

    What happens if you restart winbindd?

    /var/mdw/scripts/ntlm restart

    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

    thx. I tried /ntlm and in the next step /httpproxy restart. Now, the firewall is reporting the following error messages (http.log).

    epool.c ... broken pipe / connection refused. Not sure, but with previous versions I didn't notice such errors messages.

    2018:10:24-11:02:16 xxxx httpproxy[3166]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="plain_write_vector" file="epoll.c" line="1117" message="Write error on the epoll handler 1048 (Broken pipe)"
    2018:10:24-11:02:19 xxxx httpproxy[3166]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="plain_write_vector" file="epoll.c" line="1117" message="Write error on the epoll handler 214 (Connection refused)"
    2018:10:24-11:02:19 xxxx httpproxy[3166]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="plain_write_vector" file="epoll.c" line="1117" message="Write error on the epoll handler 214 (Connection refused)"
    2018:10:24-11:02:46 xxxx httpproxy[3166]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="plain_write_vector" file="epoll.c" line="1117" message="Write error on the epoll handler 579 (Broken pipe)"
    2018:10:24-11:02:51 xxxx httpproxy[3166]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="plain_write_vector" file="epoll.c" line="1117" message="Write error on the epoll handler 210 (Broken pipe)"
    2018:10:24-11:03:25 xxxx httpproxy[3166]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="plain_write_vector" file="epoll.c" line="1117" message="Write error on the epoll handler 257 (Broken pipe)"
     
  • 0 in reply to tryf

    One of the unwritten rules here is "one topic per thread" - that's to make it easier for future members to find an answer to a question that's already been answered without starting a new thread.  Using an appropriate title, please ask your second question in the Web Protection forum.

    You might want to try a Google on:

    site:community.sophos.com/products/unified-threat-management/f "Write error on the epoll handler"

    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

    thx. I only want to mentioned it briefly. It could be related to my previous error messages. They came up again (almost daily) and filling to log file:

     

      
    2018:10:24-16:17:24 xxxx httpproxy[28682]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0xdf992600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
2018:10:24-16:17:24 xxxx httpproxy[28682]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0xd702c400" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
2018:10:24-16:17:24 xxxx httpproxy[28682]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0xdf992600" function="read_winbindd_response" file="auth_adir.c" line="239" message="epoll_read_until: Transport endpoint is not connected"
  • 0 in reply to tryf

    Have you already tried un-joining and re-joining the domain as suggested above?

    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

    Yes, I have done those steps and it's only a workaround.

Unfiltered HTML