Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 3 subscribers
  • Views 3579 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

EndPointProtectionLogging

scottj_01

All-

 

I seem to frequently encounter an issue with end point protection logging where the log indicates a communications error in the log. This problem comes a goes at will usually appearing on somtime during the weekend. Please see the log below, clearly the problem is not my UTM most likely a back end issue. Would it be possible to solve this permanently? I am using version 9.501-5. This has happened with eariler versons too.

 

2017:06:26-16:50:06 oasis epsecd[5622]: W main::_log:435() =>  severity="warn" sys="System" sub="eplog" 
name="Listing [https://b96b5717-8d7b-3ba2-922c-733b1654d3a0-wdx-8d7b.broker.sophos.com//b96b5717-8d7b-3ba2-922c-733b1654d3a0/] 
failed with return code 35: SSL connect error Unknown SSL protocol error in connection to 
b96b5717-8d7b-3ba2-922c-733b1654d3a0-wdx-8d7b.broker.sophos.com:443 
2017:06:26-16:50:06 oasis epsecd[5622]: "

Thanks,
Jim


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

    I wouldn't worry about it, Jim.  I'm used to logs being chatty and minor, intermittent issues with Sophos servers being reported in the epsecd log.

    Cheers - Bob

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

    I wouldn't worry about it, Jim.  I'm used to logs being chatty and minor, intermittent issues with Sophos servers being reported in the epsecd log.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data
Unfiltered HTML