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

Web Config Log Levels Not Used For XRootd #2009

Open
4 of 7 tasks
CannonLock opened this issue Feb 11, 2025 · 0 comments
Open
4 of 7 tasks

Web Config Log Levels Not Used For XRootd #2009

CannonLock opened this issue Feb 11, 2025 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@CannonLock
Copy link
Contributor

Pelican Version:
Run ./pelican --version to get version number.

Pelican Service:

  • Client
  • Plugin
  • Registry
  • Director
  • Origin
  • Cache
  • Other (please give the detail)

Describe the bug
A clear and concise description of what the bug is.

The log levels for the Cache/Origin in Loggin.* are not applied to XRootd if they are in the web-config.yaml.

To Reproduce
Steps to reproduce the behavior.

Start a Origin -> change logging.level: Debug in the web UI -> Note nothing happened in the logs

Change logging.level: Debug in pelican.yaml -> Start a Origin -> Note the logs that now appear

Expected behavior
A clear and concise description of what you expected to happen.

I expect the config changes in the web ui to propogate to changes in the XRootd server

Desktop (please complete the following information):

  • OS: MacOS
@CannonLock CannonLock added the bug Something isn't working label Feb 11, 2025
@CannonLock CannonLock added this to the v7.15 milestone Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants