This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Restore default logging if logging.json is removed when SIGHUP. #7792
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
logging.jsonis removed when SIGHUP. Before if nologging.jsonwas found during a SIGHUP, then no modifications were made to logging.peer_ilogmessages topeer_dlogsince info is now default.Consensus Changes
API Changes
Documentation Additions
[ x ] Documentation Additions
Update docs to reflect that default logging can be restored by removing the
logging.jsonand sending a SIGHUP to the process.producer_plugin,net_plugin_impl,transaction_tracing,http_plugin, and all non-default loggers are now enabled atinfolevel logging. To restore previous behavior these loggers will need to be configured in alogging.jsonwith levelofffor logging.