Sophos Firewall: v18.5 MR3: Feedback and experiences

I would like to update our XG 135 to 18.5 MR3 (currently on MR1) to see if it fixes a specific problem that we have (https://community.sophos.com/sophos-xg-firewall/f/discussions/133450/unable-to-ping-certain-ip-address-intermittently). I've been through detailed debugging steps with Sophos to prove the issue and this is the next step...

I have been following this thread and decided it would be safer to wait for the automatic prompt after reading this:

Martin Hampl said:

Uploading HW-18.5.3_MR-3.SF300-408.sig to XG125 (18.5.1) as inactive image will crash and reboot the appliance

Today I received the automatic prompt so will consider applying it soon. However, I am concerned that the update will introduce more issues than it solves. There are a couple of common themes that I've picked up:

Bart van der Horst said:

Lots of spam coming through since update, did not change anything. Any clue?

Thomas_XG said:

Seems like. There are some issues with pattern-update and spam-recognition with the new SASI. v19 EAP 2 is also affected.

I don't think this will affect our configuration but I see the "osquery" issue is also quite common (and on the same XG 135 as we have):

Florian87 said:

I did upgrade to SFOS 18.5.3 MR-3-Build408 on three devices (XG106, XG125, XG135). All of them show the warning that the osquery service is stopped. The warning message sometimes disappears and then comes back, it is flapping.

Keynon Lannom said:

After upgrading XG135 - OSQUERY service is not starting.

Sophos support didn't really acknowledge the issue but suggested that manually starting "osquery" would resolve it. What is everyone else finding? Are there any other impacts of this service not running other than graph display issues in the dashboard (https://community.sophos.com/sophos-xg-firewall/sfos-v19-early-access-program/f/discussions/131619/bug---osquery-service-stopped)?

Anything else that I should be concerned about?

I am just following up to say that I applied MR3 a couple of weeks ago on our XG 135 and didn't encounter any issues, not even the "osquery" issue that I was expecting. It has been running well since and seems to have solved the specific issue that we had with intermittent connectivity to some servers.

I am just following up to say that I applied MR3 a couple of weeks ago on our XG 135 and didn't encounter any issues, not even the "osquery" issue that I was expecting. It has been running well since and seems to have solved the specific issue that we had with intermittent connectivity to some servers.

I can confirm. However it feels weird that we do not know why the issues just suddenly disappeard.

@LuCar Toni

Have issues like "osquery" been fixed by hotfixes that got applied automatically?