log: log RPC port on startup #26131
Merged
log: log RPC port on startup #26131
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
I just spent a few hours trying to figure out why "18444" wasn't getting me to regtest's RPC server. I'm not the sharpest tool in the shed, but I was maybe understandably confused because "Bound to 127.0.0.1:18445" appears in the logs, which I assumed was the P2P port. This change logs the RPC listening address, which seems like a basic piece of information that shouldn't be buried in debug logs.
jamesob
force-pushed
the
jamesob-22-09-log-rpc-port
branch
from
ef51b09
to
9d14f27
Compare
|
Wouldn't the solution be to set the log level to INFO? |
jonatack
reviewed
Sep 20, 2022
|
ACK 9d14f27 I have also spent time in the past looking for the correct ports, so this makes sense to me. |
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsNo conflicts as of last run. |
|
Good for merge? |
sidhujag
pushed a commit
to syscoin/syscoin
that referenced
this pull request
Oct 4, 2022
9d14f27 log: log RPC port on startup (James O'Beirne) Pull request description: I just spent a few hours trying to figure out why "18444" wasn't getting me to regtest's RPC server. I'm not the sharpest tool in the shed, but I was maybe understandably confused because "Bound to 127.0.0.1:18445" appears in the logs, which I assumed was the P2P port. This change logs the RPC listening address by default on startup, which seems like a basic piece of information that shouldn't be buried under `-debug`. ACKs for top commit: dergoegge: ACK 9d14f27 jarolrod: ACK 9d14f27 aureleoules: ACK 9d14f27 Tree-SHA512: 5c86f018c0b8d6264abf878c921afe53033b23ab4cf289276bb1ed28fdf591c9d8871a4baa4098c363cb2aa9a637d2e4e18e56b14dfc7d767ee40757d7ff2e7c
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.
I just spent a few hours trying to figure out why "18444" wasn't getting me to regtest's RPC server. I'm not the sharpest tool in the shed, but I was maybe understandably confused because "Bound to 127.0.0.1:18445" appears in the logs, which I assumed was the P2P port.
This change logs the RPC listening address by default on startup, which seems like a basic piece of information that shouldn't be buried under
-debug.