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.

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

Passing --rpc-http-enabled=true via command line does not enable rpc for specific options combination #8359

Open
cdivitotawela opened this issue Feb 27, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@cdivitotawela
Copy link
Contributor

When a specific combination of options passed via command line including --rpc-http-enabled=true does not enable the RPC end point and logs a WARN message --rpc-http-enabled has not been set in the command line. However same config included in config.toml file issue does not occur. Only specific combination of command line options are set in the bug report to help reproduce the issue. Used the latest docker image.

Steps to Reproduce

  1. Start besu using command and watch the starting logs. WARN log appears | main | WARN | Besu | --rpc-http-host, --rpc-http-port and --rpc-http-cors-origins has been ignored because --rpc-http-enabled was not defined on the command line.
docker run hyperledger/besu:25.2.0 \
  --rpc-http-enabled=true \
  --rpc-http-host=0.0.0.0 \
  --rpc-http-port=8545 \
  --tx-pool-enable-save-restore=true \
  --tx-pool-disable-locals=true \
  --tx-pool-no-local-priority=true \
  --rpc-http-cors-origins="*"
  1. Removing any one of the options --tx-pool-enable-save-restore or --tx-pool-disable-locals or --tx-pool-no-local-priority or --rpc-http-cors-origins won't log the WARN message.

  2. Besu should not report that --rpc-http-enabled was not defined on the command line` when the option is defined in the command line.

Actual behavior:
When option --rpc-http-enabled is defined in the command line a WARN message indicates --rpc-http-enabled was not defined on the command line

Frequency: Everytime

Logs

2025-02-27 02:11:41.708+00:00 | main | INFO  | Besu | Starting Besu
2025-02-27 02:11:41.887+00:00 | main | WARN  | Besu | --rpc-http-host, --rpc-http-port and --rpc-http-cors-origins has been ignored because --rpc-http-enabled was not defined on the command line.
2025-02-27 02:11:41.888+00:00 | main | WARN  | Besu | --rpc-ws-host has been ignored because --rpc-ws-enabled was not defined on the command line.
2025-02-27 02:11:41.891+00:00 | main | WARN  | Besu | --graphql-http-host has been ignored because --graphql-http-enabled was not defined on the command line.
2025-02-27 02:11:41.944+00:00 | main | WARN  | Besu | --rpc-http-host, --rpc-http-port and --rpc-http-cors-origins has been ignored because --rpc-http-enabled was not defined on the command line.
2025-02-27 02:11:41.944+00:00 | main | WARN  | Besu | Engine API authentication enabled without key file. Expect ephemeral jwt.hex file in datadir
2025-02-27 02:11:41.947+00:00 | main | INFO  | Besu | Connecting to 0 static nodes.

Versions (Add all that apply)

  • Software version: [25.2.0]
  • Java version: [openjdk-java-21]
  • Docker Version: [27.4.0]

Additional Information (Add any of the following or anything else that may be relevant)

Attached scripts.zip helps to reproduced the issue

@cdivitotawela cdivitotawela added the bug Something isn't working label Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant