Skip to content

Conversation

@tomhughes
Copy link
Member

This attempts to fix #43 by reducing the level of the message to LOG_INFO in the hope that it will then only go to the log file and not to the console as well.

@apmon
Copy link
Member

apmon commented Aug 19, 2013

LOG_NOTICE seems consistent with other startup messages printed by Apache.

The issue is as far as I can tell is that the configuration happens to early in the server process, before the logging facility is set up. Thats why it gets printed to the console rather than the apache log file where it belongs. The notice needs to happen at a slightly later stage e.g. possibly the post_config hook(?), which is probably related to #42. But I haven't quite figured out where best in a way that works for me.

@tomhughes
Copy link
Member Author

Logging is definitely up and running because the message does go to the log as well. I think it is just that anything at NOTICE or higher during startup is also sent to the console.

@pantierra
Copy link
Collaborator

Closing here, as the error it tries to fix is not reproducible anymore and it is not clear if this here would be the right solutioin.

@pantierra pantierra closed this Jul 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Log spam at startup/reload

3 participants