[go: nahoru, domu]

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

Handling of busy LSF deamon #177

Open
DrChainsaw opened this issue Oct 7, 2021 · 4 comments
Open

Handling of busy LSF deamon #177

DrChainsaw opened this issue Oct 7, 2021 · 4 comments

Comments

@DrChainsaw
Copy link
Collaborator

I sometimes get the following failure when adding LSF workers:

ClusterManagers.LSFException("LSF daemon (LIM) not responding ... still trying")

I'm not sure if this message is the same on all systems, but if it is then maybe its worth adding to the set of expected responses here.

@bjarthur
Copy link
Collaborator
bjarthur commented Oct 7, 2021

i have not seen that error message. what version of LSF are you using? mine is:

$ lsid
IBM Spectrum LSF Standard 10.1.0.9, Oct 16 2019
Copyright International Business Machines Corp. 1992, 2016.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

@DrChainsaw
Copy link
Collaborator Author

This is mine:

$ lsid
IBM Spectrum LSF Standard 10.1.0.10, Apr 10 2020

Just to clarify: This message comes every now and then as a result of any lsf command (e.g. bsub, bjobs, bhosts etc) and prints every few seconds. After a while (max a few minutes) the lsf command is successfully executed.

It might be some (potentially home-made) overload protection. I will ask my admins about it.

@DrChainsaw
Copy link
Collaborator Author

Admins responded that the message most likely appears due to restarts in conjunction with reconfiguration of the server.

@DrChainsaw
Copy link
Collaborator Author

Maybe one could use this list to sort out the non-fatal messages? I'm pretty sure I have seen the LSF is processing your request. Please wait… message as well.

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