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

HowTo: error diagnosis, and recovery #566

Open
hjoliver opened this issue Nov 18, 2022 · 1 comment
Open

HowTo: error diagnosis, and recovery #566

hjoliver opened this issue Nov 18, 2022 · 1 comment
Labels
content Addition or modification of documentation
Milestone

Comments

@hjoliver
Copy link
Member

hjoliver commented Nov 18, 2022

New users often don't know where to look when things go wrong.

It might be a while before all the relevant info gets exposed in the GUI, and even then we should document lower level process.

  1. check the scheduler log, to see if the scheduler encountered a problem, or if a task did
  2. if a task failed in execution, check its job.out and job.err
  3. if a task failed job submission, check job-activity.log

And document how recover from common kinds of failure. (Partially dependent on near-future development of cylc set-outputs etc.)

@hjoliver hjoliver added this to the 8.x milestone Nov 18, 2022
@dpmatthews dpmatthews modified the milestones: 8.x, 8.0.3 Nov 24, 2022
@oliver-sanders oliver-sanders modified the milestones: 8.0.3, 8.1.0, 8.x Nov 30, 2022
@oliver-sanders
Copy link
Member

Good idea, some kind of troubleshooting section.

@oliver-sanders oliver-sanders modified the milestones: 8.x, pending Apr 17, 2023
@oliver-sanders oliver-sanders added the content Addition or modification of documentation label Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Addition or modification of documentation
Projects
None yet
Development

No branches or pull requests

3 participants