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

Scheduler throws all non-starters after a long run. #1363

Closed
mfeit-internet2 opened this issue Nov 3, 2023 · 1 comment
Closed

Scheduler throws all non-starters after a long run. #1363

mfeit-internet2 opened this issue Nov 3, 2023 · 1 comment
Assignees

Comments

@mfeit-internet2
Copy link
Member

mfeit-internet2 commented Nov 3, 2023

CERN is seeing a situation after about a week where the error variable is getting set with global scope and the schedule_task() function is picking it up, assuming there is actually an error and posting explanation-free non-starters.

A two-part fix is required:

First is to force error into local scope by initializing it withing the function:

diff scheduler-orig scheduler-patched
748a749,750
>     error = None
>

Second is to figure out where error is being assigned with global scope. (Edit: Looks like this is the only place where this variable is used, so initializing it should be a good fix.)

System showing the error is pse01-gva.cern.ch.

@arlake228
Copy link
Collaborator

Closing this since we included fix above in 5.0.6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants