Error 400 and 500 when opening and uploading files to shares

NHMDenmark / DaSSCo-asset-service

DaSSCo asset service is part of DaSSCo storage system

0 stars 0 forks source link

Error 400 and 500 when opening and uploading files to shares #38

Open Baeist opened 2 months ago

Baeist commented 2 months ago

I am unable to (re)open a share or upload files to already existing shares. Sometimes its status 500 and sometimes its 400 with the message that the "Share directory doesnt exist". I can still create new assets, but their share directories doesnt exist when uploading a file, but they can have their share allocation changed. @bhsi-snm @NTechThomas

Baeist commented 1 month ago

Cant upload file for newly created share

Cant open share

NTechThomas commented 1 month ago

I am looking into this, for now as a workaround you can delete the share and then open it again manually

Baeist commented 1 month ago

That does not work for me.

Sequence

Baeist commented 1 month ago

This issue was replicated after running a test set of 10 new assets through the entire pipeline (create asset, upload files, sync erda, open share, download files, update metadata). The first 4 (ucloud-test-23, 24 , 25 and 29) assets went through every step, then 2 assets got stuck with the asset_received status issue 45, and then the bug happened and no further uploading or opening of shares are possible for any assets.

NTechThomas commented 3 weeks ago

Here is the current status of this issue:

I belive we have fixed the issue with ERDA-connection dropping when opening and synchronizing multiple shares after each other.
- The issue is due to the fact that ERDA seems to only let us open 3 connections in a timespan of 5 minutes and if we open more, all connections will fail for the next 5 min.
- We have fixed it by having the app maintain 3 connections that are then reused across the app.
There is another isssue with disk space on the server which is the cause of the missing directories. We will need more space on the server to fix this bug.