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

Dump Authfile debugging info into the container log (SOFTWARE-5614) #105

Conversation

brianhlin
Copy link
Member

We may not get all the info we need but it should help us narrow down where the problem's occurring. Maybe we should set -e.

@matyasselmeci
Copy link
Contributor

Sure. I'd like to see what happens for the stash-origin-auth instance update even if the stash-origin instance update fails, so I'd rather not do set -e. We could, however, capture the return codes and, if either of them fail, exit explicitly (again, after both had been tried).

@matyasselmeci
Copy link
Contributor

Also dump the files on failure? Something like

shopt -s nullglob
for f in /run/stash-origin/* /run/stash-origin-auth/*; do
    echo "======= $f ======="
    cat "$f"
    echo
done
shopt -u nullglob

@brianhlin
Copy link
Member Author

@matyasselmeci the actual fix for the problem is in fa7d1de

@matyasselmeci matyasselmeci merged commit 1cf8675 into opensciencegrid:master Jul 14, 2023
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

Successfully merging this pull request may close these issues.

2 participants