We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Pelican Version: Run ./pelican --version to get version number.
./pelican --version
Pelican Service:
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
logging.level: Debug
Change logging.level: Debug in pelican.yaml -> Start a Origin -> Note the logs that now appear
pelican.yaml
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):
The text was updated successfully, but these errors were encountered:
Saartank
No branches or pull requests
Pelican Version:
Run
./pelican --version
to get version number.Pelican Service:
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 logsChange
logging.level: Debug
inpelican.yaml
-> Start a Origin -> Note the logs that now appearExpected 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):
The text was updated successfully, but these errors were encountered: