Cleanup origin startup stdout

[bbockelm]

When watching folks during the PEARC tutorial, it was quite apparent how confusing our startup has become -- lots of "stuff" gets printed to stdout not from Pelican.

Here's what we have currently:

Initializing run environment for Pelican...
Jul 22, 2024 6:45:54 PM edu.uiuc.ncsa.security.core.util.MyLoggingFacade info
INFO: scitokens-server:Logging to file /dev/pts/0
Jul 22, 2024 6:45:54 PM edu.uiuc.ncsa.security.core.util.MyLoggingFacade info
INFO: scitokens-server:OAuth 2 for MyProxy, version 5.4.1 startup on Mon Jul 22 18:45:54 UTC 2024
Jul 22, 2024 6:45:54 PM edu.uiuc.ncsa.security.core.util.MyLoggingFacade info
INFO: scitokens-server:loading configuration.
Jul 22, 2024 6:45:54 PM edu.uiuc.ncsa.security.core.util.MyLoggingFacade info
INFO: oa4mp:Error loading authorization configuration. Disabling use of headers
Jul 22, 2024 6:45:54 PM edu.uiuc.ncsa.security.core.util.MyLoggingFacade info
INFO: oa4mp:ping enabled
Jul 22, 2024 6:45:54 PM edu.uiuc.ncsa.security.core.util.MyLoggingFacade info
INFO: oa4mp:No claim source configuration found.
Jul 22, 2024 6:45:54 PM edu.uiuc.ncsa.security.core.util.MyLoggingFacade info
INFO: oa4mp:Starting to load LDAP configuration.
No chain present for host cert; trying to derive one
No chain present; will use empty file
Starting Pelican...
Running pelican with arguments: origin serve -p 8444
Version: 7.9.3-next
Build Date: 2024-06-25T16:40:15Z
Build Commit: a024f4636b25ecccb26308769c0256d488d62392
Built By: goreleaser
2024/07/22 18:45:54 OK   20240528174529_create_db_tables.sql (2.76ms)
2024/07/22 18:45:54 goose: successfully migrated database to version: 20240528174529

Pelican admin interface is not initialized

I think we should dump:

• All the oa4mp/Java stuff
• The "No chain present" lines (may be related to the above?)
• The Build date / commit /built by
• Output from goose / ORM.

Marking as critical as I think this might be a simple fix but bigger payoff for new people.

[bbockelm]

Some additional details:

• This occurs when you run the origin as a standalone container (there, the log files are redirected for logging -- the above is the stdout not using the logging system). The tutorial where we noticed the errant printout is here if you'd like to reproduce.
• The entry point for the container image is here.
• I expect the OA4MP stdout is coming from here: https://github.com/PelicanPlatform/pelican/blob/main/images/entrypoint.sh#L38 . We could redirect the output to a buffer and only print out the information if the command fails.
• Similarly, the chain manipulation here could be hidden if there's no error.
• For these two:
  • The Build date / commit /built by
  • Output from goose / ORM. I don't know where they come from -- goose, at least, may need to be investigated to see if it can hook into a logging system.