Vault desync and restarting container issues

[anykeyh]

Hello, I'm vault owner having issues making things work properly.

My vault is running on cloud machine (2vcpu/2gb ram as stated in the documentation) using docker-compose up

Often my transactions are stuck:

https://btc.harmony.one/dashboard/vaults/0x8D91eCB8440011577A62a274a42F35Bf51e2f5E7/redeems/53638847569553460732156364332640431072789681727946223794684582003232765928995/redeems/53638847569553460732156364332640431072789681727946223794684582003232765928995

(note: As I restarted the vault, now it says "waiting for execute" and I can click on redeem manually. Before it was saying "waiting for the vault" or something similar and nothing could have been done)

The vault is still running (says online on the vault page + I can access my personal dashboard). I then need to restart the vault to perform the pending operation.

The second problem is restarting the vault need to resync the Bitcoin chain into MongoDB on each restart. At first, it wasn't so long (only 25 minutes), but as time pass it starts to take multiple hours to resync to 100%. Meanwhile the node is running at 100% CPU on the two vcpu:

I'm not sure if it is possible at least to save the current state of the blockchain when stopping the container. I don't mind restarting once a day but as time pass it become longer and longer to resync the node.

[anykeyh]

Follow up:

Just got the problem again today. Need to restart the vault and wait for resync

Here, the vault is running without any errors yet it not able to proceed the transaction...

[DayatBatam]

Same problem with me :
4 time redeem in a raw (different user), all of them waiting for transaction then expired and have to cancel manually
Redeem # 19072394018270758250489615794719714095461060607827445422015696384401026751896
Redeem # 8372345034855612704343393073382233732670900249781889069945506286296781116587
Redeem # 6639895637325534507216364663273289998606634546819137974294574689458850355888
Redeem # 81717107533723028964342497332804172180487993468614797425173775008601749413409
Not able to proceed the transaction

[anykeyh]

I'm bumping again this issue because this is a really annoying one.

Can the team acknowledge they know about this issue? Seems to happen to many vault owners. Working on new features while the basic is not working is - in my opinion - not a good way to proceed.