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

shell: fatal error log messages are lost #5954

Open
grondo opened this issue May 10, 2024 · 0 comments
Open

shell: fatal error log messages are lost #5954

grondo opened this issue May 10, 2024 · 0 comments

Comments

@grondo
Copy link
Contributor

grondo commented May 10, 2024

Problem: Just after the shell connects to the broker and a flux_t handle is available, the evlog based shell logger disables log output to stderr completely. However, at this time there might not yet be another destination for these messages, and so they are lost. For example, when the job shell gets an error parsing jobspec, the user will only see:

flux-job: task(s) exited with exit code 1
flux-job: No job output found

If there is no other destination for a fatal error log, the shell should somehow detect that and write the message to stderr so that the job-exec module can add it to the eventlog.

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

1 participant