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

Pelican does not dump config into Logging.LogLocation #1944

Open
4 of 7 tasks
brianhlin opened this issue Jan 27, 2025 · 3 comments · May be fixed by #1970
Open
4 of 7 tasks

Pelican does not dump config into Logging.LogLocation #1944

brianhlin opened this issue Jan 27, 2025 · 3 comments · May be fixed by #1970
Assignees
@Saartank
Labels
bug Something isn't working
Milestone
v7.14

Comments

@brianhlin
Copy link
Contributor

Pelican Version:
7.12.0

Pelican Service:

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

Describe the bug

The Pelican configuration dump upon startup appears to be printed to stdout instead of a configured log file in Logging.LogLocation

To Reproduce

  1. Configure a LogLocation
  2. Start a Pelican service (any will do). Config dump will go to stdout and not the configured Logging.LogLocation

Expected behavior

I'd expect the config dump to show up in the configured Logging.LogLocation. This is useful when troubleshooting for the following reasons:

  1. Providing sentinel text to search for service restarts
  2. Providing insight into the running configuration for specific log lines
@brianhlin brianhlin added the bug Something isn't working label Jan 27, 2025
@brianhlin brianhlin added this to the v7.14 milestone Jan 27, 2025
@Saartank
Copy link
Collaborator

Hi Brian, this is by design. All the config commands are intended to be interactive. The creation of a logfile from config commands is actually a bug that we are currently working on: #1934.

The LogLocation should only be used by server modules such as Cache, Director, Registry, and Origin.

We can always pipe the output of the dump command, or would it be helpful if I added a -f option to direct the config dump to a specific file?

@brianhlin
Copy link
Contributor Author

brianhlin commented Jan 27, 2025 •
edited
Loading

@Saartank I think it definitely makes sense for pelican config dump to print only to stdout. However, when using a server module like pelican origin serve, a configuration dump is printed to stdout but all other logging gets printed in Logging.LogLocation. I would expect the config dump to also be included in Logging.LogLocation for this case.

@Saartank
Copy link
Collaborator

Sorry @brianhlin, I understand now. I got confused with the pelican config dump command.

@Saartank Saartank linked a pull request Jan 30, 2025 that will close this issue
Log Pelican config on server startup #1970
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Saartank Saartank

Labels
bug Something isn't working
Projects
None yet
Milestone
v7.14
Development

Successfully merging a pull request may close this issue.

Log Pelican config on server startup Saartank/pelican
2 participants
@brianhlin @Saartank