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.

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

If beeflow is started on a compute node and the allocation is stopped before beeflow is stopped it cannot be started up again #956

Closed
pagrubel opened this issue Nov 6, 2024 · 1 comment

Comments

@pagrubel
Copy link
Collaborator

pagrubel commented Nov 6, 2024

This shouldn't occur by the user, we only added the -B flag to beeflow core start for CI purposes. However, someone might start beeflow from a compute node anyway. In my case the wf_manager would not start and then I couldn't do a beeflow core stop. We should make it easier to recover from that. I was able to do so by deleting client.db, but that doesn't seem like the best route.

I guess this is not a priority, just wanted to put it on the radar screen.

@kchilleri
Copy link
Collaborator

Duplicate of issue #974.

@kchilleri kchilleri closed this as not planned Won't fix, can't repro, duplicate, stale Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants