You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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.
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
The text was updated successfully, but these errors were encountered:
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 inconfig.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
| 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="*"
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.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
Versions (Add all that apply)
25.2.0
]openjdk-java-21
]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
The text was updated successfully, but these errors were encountered: