Guest User!

You are not Sophos Staff.

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

Sophos UTM - Sophos LiveConnect is disabled

Since 7 January 2016 my Sophos LiveConnect is disabled on the UTM. Before this everything working fine?

The PCs can are working fine, but if the UTM cannot connect to the LiveConnect changes cant be done.

2016:01:07-20:05:31 myfirewall epsecd[5258]:  1. Epsec::Utils::Logging::_log:59() /</usr/local/bin/epp_client.plx>Epsec/Utils/Logging.pm
2016:01:07-20:05:31 myfirewall epsecd[5258]:  2. Epsec::Logic::Client::on_error:1461() /</usr/local/bin/epp_client.plx>Epsec/Logic/Client.pm
2016:01:07-20:05:31 myfirewall epsecd[5258]:  3. Epsec::Logic::Base::run:60() /</usr/local/bin/epp_client.plx>Epsec/Logic/Base.pm
2016:01:07-20:05:31 myfirewall epsecd[5258]:  4. main::top-level:63() client.pl
2016:01:07-20:05:31 myfirewall epsecd[5258]: <=========================================================================
2016:01:07-20:05:31 myfirewall epsecd[5258]: I id="4210" severity="info" sys="System" sub="epsecd" name="Sleeping for 180 seconds"
2016:01:07-20:08:33 myfirewall epsecd[5258]: W id="424200" severity="warn" sys="System" sub="epsecd" name="Socket connect to sss1-c1f5.broker.sophos.com:443 error: Connection refused"
2016:01:07-20:08:33 myfirewall epsecd[5258]: W id="424200" severity="warn" sys="System" sub="epsecd" name="Error creating socket. " syscall_error="Connection refused"
2016:01:07-20:08:33 myfirewall epsecd[5258]: >=========================================================================
2016:01:07-20:08:33 myfirewall epsecd[5258]: E id="4281" severity="crit" sys="System" sub="epsecd" name="Unexpected error: Unknown error at /</usr/local/bin/epp_client.plx>Epsec/Logic/Client.pm line 151." effect="Can't talk to Sophos LiveConnect"
2016:01:07-20:08:33 myfirewall epsecd[5258]:
2016:01:07-20:08:33 myfirewall epsecd[5258]:  1. Epsec::Utils::Logging::_log:59() /</usr/local/bin/epp_client.plx>Epsec/Utils/Logging.pm
2016:01:07-20:08:33 myfirewall epsecd[5258]:  2. Epsec::Logic::Client::on_error:1461() /</usr/local/bin/epp_client.plx>Epsec/Logic/Client.pm
2016:01:07-20:08:33 myfirewall epsecd[5258]:  3. Epsec::Logic::Base::run:60() /</usr/local/bin/epp_client.plx>Epsec/Logic/Base.pm
2016:01:07-20:08:33 myfirewall epsecd[5258]:  4. main::top-level:63() client.pl
2016:01:07-20:08:33 myfirewall epsecd[5258]: <=========================================================================
2016:01:07-20:08:33 myfirewall epsecd[5258]: I id="4210" severity="info" sys="System" sub="epsecd" name="Sleeping for 240 seconds"
2016:01:07-20:12:40 myfirewall epsecd[5258]: I id="4232" severity="info" sys="System" sub="epsecd" name="Not syncing web policy resources as web control is disabled"
2016:01:07-20:12:44 myfirewall epsecd[5258]: I id="4231" severity="info" sys="System" sub="epsecd" name="Syncing SWC with web control global status "
2016:01:07-22:02:26 myfirewall epsecd[5258]: I id="4213" severity="info" sys="System" sub="epsecd" name="User triggered changes in webadmin"
2016:01:07-23:02:02 myfirewall epsecd[5258]: I id="4213" severity="info" sys="System" sub="epsecd" name="User triggered changes in webadmin"



This thread was automatically locked due to age.
Parents
  • I had also opened a case with Sophos on this (India, really??) and just received this update:

    "The current issue with our endpoint brokers is still being worked on by our GES team. As per last triage it should be stable after January 29th."

    Dave
Reply
  • I had also opened a case with Sophos on this (India, really??) and just received this update:

    "The current issue with our endpoint brokers is still being worked on by our GES team. As per last triage it should be stable after January 29th."

    Dave
Children
No Data