"database is locked" error, cannot join communities by specific user

[pavloburykh]

At some point one of my test users has become unable to join communities. Requests stuck in Pending state, control node does not receive community requests.

Ping me up in DM and I will share seed phrase of the user so you can reproduce.

Steps:

1. Restore given user
2. Try to join any community by this user
3. Observe the result

Actual result: community request stucks in Pending.

There are lot of "database is locked" errors in geth.log

logs (27).zip

ERROR[03-27|09:53:56.805|github.com/status-im/status-go/services/wallet/collectibles/manager.go:769]                                  collectionsDataDB SetData failed         communityID=0x039bdd758f1122e17e086d3dd068391688e8b2655d6c86619e1ef5080f42c6cce3 err="database is locked"
ERROR[03-27|09:53:56.805|github.com/status-im/status-go/services/wallet/collectibles/manager.go:794]                                  fetchCommunityAssets failed              communityID=0x039bdd758f1122e17e086d3dd068391688e8b2655d6c86619e1ef5080f42c6cce3 err="database is locked"
ERROR[03-27|09:53:56.806|github.com/status-im/status-go/services/wallet/collectibles/manager.go:769]                                  collectionsDataDB SetData failed         communityID=0x039bdd758f1122e17e086d3dd068391688e8b2655d6c86619e1ef5080f42c6cce3 err="database is locked"
ERROR[03-27|09:53:56.806|github.com/status-im/status-go/services/wallet/collectibles/manager.go:794]                                  fetchCommunityAssets failed              communityID=0x039bdd758f1122e17e086d3dd068391688e8b2655d6c86619e1ef5080f42c6cce3 err="database is locked"
ERROR[03-27|09:53:56.815|github.com/status-im/status-go/services/wallet/collectibles/manager.go:769]                                  collectionsDataDB SetData failed         communityID=0x039bdd758f1122e17e086d3dd068391688e8b2655d6c86619e1ef5080f42c6cce3 err="database is locked"
ERROR[03-27|09:53:56.815|github.com/status-im/status-go/services/wallet/collectibles/manager.go:794]                                  fetchCommunityAssets failed              communityID=0x039bdd758f1122e17e086d3dd068391688e8b2655d6c86619e1ef5080f42c6cce3 err="database is locked"
ERROR[03-27|09:53:56.819|github.com/status-im/status-go/services/wallet/collectibles/manager.go:777]                                  collectiblesDataDB SetCommunityInfo failed communityID=0x039bdd758f1122e17e086d3dd068391688e8b2655d6c86619e1ef5080f42c6cce3 err="database is locked"
ERROR[03-27|09:53:56.819|github.com/status-im/status-go/services/wallet/collectibles/manager.go:794]                                  fetchCommunityAssets failed              communityID=0x039bdd758f1122e17e086d3dd068391688e8b2655d6c86619e1ef5080f42c6cce3 err="database is locked"
ERROR[03-27|09:53:56.822|github.com/status-im/status-go/services/wallet/collectibles/manager.go:769]                                  collectionsDataDB SetData failed         communityID=0x039bdd758f1122e17e086d3dd068391688e8b2655d6c86619e1ef5080f42c6cce3 err="database is locked"
ERROR[03-27|09:53:56.822|github.com/status-im/status-go/services/wallet/collectibles/manager.go:794]                                  fetchCommunityAssets failed              communityID=0x039bdd758f1122e17e086d3dd068391688e8b2655d6c86619e1ef5080f42c6cce3 err="database is locked"

https://github.com/status-im/status-mobile/assets/97245802/8454cccb-53ba-4484-8b72-96e0a45ead27

Additional Information

• Status version: nightly
• Operating System: Android, iOS

[qfrank]

Hi @pavloburykh , i'm unable to reproduce error("database is locked") with your provided seedphrase. Also I can join the 1st and 4th community i created, i'm just wondering if the control node of 2nd and 3rd community are online?

[pavloburykh]

if the control node of 2nd and 3rd community are online?

Hi @qfrank! It is not online 24/7, although it was online when we have been testing it together yesterday and you have failed to join despite of that.

[qfrank]

Upon investigation, we found that the issue is user-specific and not related to the "database is locked" error. The error logs did not provide any useful information on either side. With the specific mobile user and desktop user (who is the control node), the community request stuck at pending can be reproduced in 100%. Given that this is a user-specific issue, we have decided to deprioritize it for now. We might need to write a test to recover the specific user to simulate such issue to debug. We recommend focusing on other higher-priority issues unless further evidence suggests a broader impact. cc @pavloburykh @cammellos

[ilmotta]

Just checking @qfrank @flexsurfer, this issue was moved back again to In Progress, but the last comment says the issue is now deprioritized.

Shouldn't we move it back to No Status and close it?

[qfrank]

What I can tell: I was not working on this after moving to low-priority :) @ilmotta

[churik]

@pavloburykh are you still the owner of the affected user and the issue is still there?

[pavloburykh]

@pavloburykh are you still the owner of the affected user and the issue is still there?

I can find that user. But it has been already debugged and it is not clear what causes the bug.

[churik]

Let's close it then for now and re-open if it reproduces again. Thank you @pavloburykh