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

Collect log to diagnose CVMFS issues #369

Open
mambelli opened this issue Nov 1, 2023 · 1 comment
Open

Collect log to diagnose CVMFS issues #369

mambelli opened this issue Nov 1, 2023 · 1 comment
Labels
FEATURE For FEATURES glidein for affected component Medium Medium priority

Comments

@mambelli
Copy link
Contributor

mambelli commented Nov 1, 2023

Is your feature request related to a problem? Please describe.
CVMFS allows to collect information when something goes wrong:

attr -g logbuffer /cvmfs/<repo>|tail -50

This can collect info on what went wrong. To run after the Glidein tests if they failed, and after the job if it failed because of CVMFS

Describe the solution you'd like
This would allow us to collect logs. Glideins could send them to the Factory for troubleshooting

Describe alternatives you've considered
NA

Info (please complete the following information):

  • Priority: medium
  • Stakeholders:
  • Components: glidein

Additional context
Dave suggested this. Fermilab will add it to the Jobsub wrapper

@github-actions github-actions bot added FEATURE For FEATURES glidein for affected component Medium Medium priority labels Nov 1, 2023
@shreyb
Copy link

shreyb commented Nov 1, 2023

Regarding the additional context: this is the (currently open) PR in the jobsub project to collect CVMFS logs: fermitools/jobsub_lite#489

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FEATURE For FEATURES glidein for affected component Medium Medium priority
Projects
None yet
Development

No branches or pull requests

2 participants