-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vault (consortia) down and generate vault token #533
Comments
Hi @evegufy currently we are checking... |
Hi @evegufy vault-cluster is back again. little question: Did you increased your requests against the vault clusters or was modified, that the cluster have maybe a higher load (ressource impact ) against vault with your bdrs_token? After checking, seems the load or mem limits are not enough, towards the current load. |
Please recheck or verfiy and close the issue. Thx in advance. |
@FaGru3n the vault is up again in general, thank you! but the vault token for the bdrs has not been regenerated, could you please still do that? |
Hi @FaGru3n are you asking if the bdrs is causing a higher load at the vault? is that the question? |
Hi @evegufy, I re-created the token |
@SebastianBezold thank you! @kbData bdrs is up again. |
Many thanks. |
Is your support request related to a problem? Please describe.
The consortia vault (https://vault.demo.catena-x.net) is down again.
Could you please check?
Could you please also regenerate the bdrs token once it's back, see #529
Please also reg
Describe the solution you'd like
Vault is available.
The text was updated successfully, but these errors were encountered: