Deactivating a user will keep the account status online

[pauloriply]

At first time we had two instance installation with separetaed DB on DigitalOcean.
After we found out about that multiple installation became only for EE, we have just removed one instance.
It behaves strangely after we delete one of two instance.
We authorize our users over Active Directory.

Description:

When an employee is fired, we go to AD and lock him there.
After that we go to RC admin panel and lock him there, but if user has been online he has still online status. It's wrong.

Steps to reproduce:

1 - User now online
2 - User is activated
3 - Go to admin panel -> users
4 - Select user
5 - Click on -> "Deactivate user"

Expected behavior:

Set offline status for user, that has diactivated

Actual behavior:

After user has diactivated status still online

Server Setup Information:

• Version of Rocket.Chat Server: 5.3.0
• Operating System: ubuntu 20.04
• Deployment Method: tar
• Number of Running Instances: 1
• DB Replicaset Oplog: yes
• NodeJS Version: v14.19.3
• MongoDB Version: 5.0.8 / wiredTiger (oplog Enabled)

No logs in debug mode.

[maluhub]

@pauloriply This seems related to: #27145, because we are facing your behaviour too.
could you check if you are facing it too?
The other issue we found is that autoaway doesn't work.
Strange thing is that we have 12 accounts. 3 of them are working well, the rest is affected.

[pauloriply]

@maluhub maluhub
Confirm.
Not all account has affected by this behaviour but lot of them.
Some accounts, after disabling changed status.

[maluhub]

@pauloriply We've manged to solve this issue by clearing usersSessions collection in mongoDB. Login to ssh and do the following:

rocketchat-server.mongo
use parties  
db.usersSessions.deleteMany({})  

[maluhub]

Additionally you can clear current status of all online users by executing:

db.users.updateMany({status:"online"},{$set:{status:"offline"}})

[pauloriply]

Still in 5.4.0

[Corinari]

does also still occur in 5.4.1

[bognerf]

And in 5.4.2

[sampaiodiego]

this is fixed in recent versions