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 Connect Client shows failed status

Big_Buck over 6 years ago

Sophos Connect Clients shows failed status on XG105 appliance on "pattern Updates" menu.

Paul Jr

This thread was automatically locked due to age.

0 FloSupport over 6 years ago

Hey Paul,

Are you still experiencing this pattern update failure?

v1.2.001 is the latest pattern version that is available.

Regards,

Florentino
Director, Global Community & Digital Support
Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question, please use the 'Verify Answer' button.

The Award-winning Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up 0 Vote Down

Cancel
0 Big_Buck over 6 years ago in reply to FloSupport

Yes.

On a XG105, Sophos Connect Clients is still at version 1.2.001 (which, curiously seems to be the latest one), with last succesfull update dating back to 15 april 2019, and still showing few days later a status failed.

On all XG210, we have the same version, with status Success.

Paul Jr
Cancel
Vote Up 0 Vote Down

Cancel
0 Big_Buck over 6 years ago in reply to FloSupport

Still showing failed status.
Cancel
Vote Up 0 Vote Down

Cancel
0 FloSupport over 6 years ago in reply to Big_Buck

Could you please perform a pattern update check while tailing your u2d.log, thanks!

Regards,

Florentino
Director, Global Community & Digital Support
Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question, please use the 'Verify Answer' button.

The Award-winning Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up 0 Vote Down

Cancel
0 Big_Buck over 6 years ago in reply to FloSupport

Hello

I have used reports to generate a text file with up2date logs.

Shows also error to send mail to 127.0.0.1

Sent to your private mail.

Paul Jr
Cancel
Vote Up 0 Vote Down

Cancel
0 Big_Buck over 6 years ago in reply to FloSupport

Updated to 17.5.5.

Still shows the same error.

Paul Jr
Cancel
Vote Up 0 Vote Down

Cancel
0 Big_Buck over 6 years ago in reply to Big_Buck

11 of May

Still shows the same error.

Paul Jr
Cancel
Vote Up 0 Vote Down

Cancel
0 LuCar Toni over 6 years ago in reply to Big_Buck

Did you already checked the u2d log?

https://community.sophos.com/kb/en-us/132211

__________________________________________________________________________________________________________________
Cancel
Vote Up 0 Vote Down

Cancel
0 Big_Buck over 6 years ago in reply to LuCar Toni

Hello

Few hours before you posted, I swap the problematic XG105 with another one we have that does not show the same error. So for now, I cannot go to the Up2Date logs. I will reset the problematic one to OEM when v18 beta shows up in few months. So we may never know what happen.

Paul Jr
Cancel
Vote Up 0 Vote Down

Cancel