SFOS 16.05.6 MR-6 Broken STAS?

Please report to Aditya Patel or to sachingurung the ticket number.

They have to investigate!

It Was 7440971

But that was closed and merged to another and I dont have that ticket.

Hi Ian , 

Unfortunately, the issue is yet not resolved in Mr 7. 

I configured last Friday STAS on a Windows Server 2008 R2. The firewall is a Sophos XG210 (SFOS 16.05.6 MR-6) with HA Active-Passive. Our customer doesn't have any problems. STAS version is 2.2.1.0 and we use WMI polling without any problems. Maybe an update problem? Have you tested a reinstall?

Regards Roman

Development Team found an issue that was introduced with MR6. The fix will be merged as soon as possible. Tests are still going on.

Sorry about that. Please be patient.

Update: NC-21538 is used to track this issue

dna said:

The fix will be merged as soon as possible

Awesome - I am still on MR-5 since 6 broke the STAS

Will the fix be merged to MR-6 or MR-7 or a separate hotfix?

Do you know what the actual issue was as some reported issues whilst others were fine - was is a config thing?

The fix won't go into MR-7 but is planned for the next possible release which is either v17 beta and/or another maintenance release.

Chances are higher to trigger the problem in setups where allot of users login simultaneously. This explains why everything is fine for some customers.

Furthermore there is a chance to provoke the problem by misconfiguration (e.g. by having 2 STAS collectors which are both feeded from the same STAS agent and configuring both STAS collector in different collector groups on SFOS. Thus every login event will be reported twice, almost at the same time).

Hi All,

I tried to recreate the issue and I can say that it is not resolved in MR-7. The issue is that XG assigns similar authid in the database table which causes a logout. The fix to this issue comes in our next maintenance release i.e., v16.05 MR-8. 

Reference: NC-21538

Thanks

Any hint on when this update MR-8 will be released?

I am running MR-3 and experiencing problems with STAS and high CPU.

If every testresult is as expected, MR8 should be available in the course of 1 week from now.