Skip to content
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.

Sign up for GitHub

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

Jump to bottom

There is a problem if beeflow is started on a compute node and that allocation is lost or an error occurs and it is exited before beeflow is stopped #974

Open
pagrubel opened this issue Dec 10, 2024 · 0 comments · May be fixed by #981
Open

There is a problem if beeflow is started on a compute node and that allocation is lost or an error occurs and it is exited before beeflow is stopped #974

pagrubel opened this issue Dec 10, 2024 · 0 comments · May be fixed by #981
Assignees
@kchilleri

Comments

@pagrubel
Copy link
Collaborator

Our overnight test were having a problem with this. Maybe there is a way to check if the comput node is actually allocated to the user. So when our database shows beeflow is running somewhere that we don't even have access to it causes an error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kchilleri kchilleri

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix backend issues and reset client db lanl/BEE
2 participants
@pagrubel @kchilleri