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.

Sign up for GitHub

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

Jump to bottom

Move Lotman.DbLocation Permission Error Handling to Pelican Layer #1956

Open
Saartank opened this issue Jan 28, 2025 · 0 comments · May be fixed by #2008
Open

Move Lotman.DbLocation Permission Error Handling to Pelican Layer #1956

Saartank opened this issue Jan 28, 2025 · 0 comments · May be fixed by #2008
Assignees
@jhiemstrawisc
Labels
enhancement New feature or request lotman
Milestone
v7.14

Comments

@Saartank
Copy link
Collaborator

Currently, if XRootD does not have the correct permissions for Lotman.DbLocation, the cache startup fails, with XRootD reporting a filesystem error and creating a core dump. These types of errors should be handled in the Pelican layer itself, especially since identifying issues through XRootD logs can be challenging.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jhiemstrawisc jhiemstrawisc

Labels
enhancement New feature or request lotman
Projects
None yet
Milestone
v7.14
Development

Successfully merging a pull request may close this issue.

Handle Lotman.LotHome directory creation/permissions in Pelican jhiemstrawisc/pelican
2 participants
@Saartank @jhiemstrawisc