simple-taiko-node: Prover not working with panick mode on Raiko

Describe the bug

Prover just working and suddenly stop working with error on Raiko container :

# Generating proof for block 79103 on taiko_a7
Generating input...
thread 'tokio-runtime-worker' panicked at host/src/preflight.rs:44:56:
invalid rpc url: RelativeUrlWithoutBase
Error: task 9978 panicked
# Generating proof for block 79073 on taiko_a7
Generating input...
thread 'tokio-runtime-worker' panicked at host/src/preflight.rs:44:56:
invalid rpc url: RelativeUrlWithoutBase
Error: task 9979 panicked
thread 'tokio-runtime-worker' panicked at host/src/preflight.rs:44:56:
invalid rpc url: RelativeUrlWithoutBase
# Generating proof for block 80046 on taiko_a7
Generating input...
Error: task 9980 panicked
# Generating proof for block 78974 on taiko_a7
Generating input...
Error: task 9981 panicked
thread 'tokio-runtime-worker' panicked at host/src/preflight.rs:44:56:
invalid rpc url: RelativeUrlWithoutBase

for this env TAIKO_NODE_IP=xx.xx.xx.xx I input IP only without HTTP:// not sure if related to this issue… because I only see above error after successful prove some proof

Steps to reproduce

Steps to reproduce here.

Spam policy

  • I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 15 (10 by maintainers)

Most upvoted comments

Adding http actually fixed the error for me too! Thanx!

Hello I will close this issue now. Since no more issue after added http:// thanks

Processing withdrawals... Done in 0.000 seconds
Generating block header... Done in 0.000 seconds
2024-05-06T14:45:51.283437Z  INFO raiko_host::execution: Verifying final state using provider data ...
2024-05-06T14:45:51.283452Z  INFO raiko_host::execution: Final block hash derived successfully. 0x864946dd13052ace53d32b196540441642bc3563b388b369dccb56df55b69610
2024-05-06T14:45:51.283454Z  INFO raiko_host::execution: Final block header derived successfully. Header { parent_hash: 0x51b2a16eb4269c3013e27c5f3d2d68f22fbcda38f437d00fe51e7931b7b2315a, ommers_hash: 0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347, beneficiary: 0xffdc94aab53881413e11cf7ff2c132f07266a905, state_root: 0x6ef6ff9503a054d2b042031876c45023b3606e283c7553c401427829ee36682c, transactions_root: 0x48452d319cbd5067d64b53d1356e398c258914fb14809f6eb05a72171431da3d, receipts_root: 0x8f2e8a04b046b311fd31055f8439eb498d67c6453515611346617bfd656200a0, withdrawals_root: Some(0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421), logs_bloom: 0x00000000000080000000000000000000000000000000000000000000000000400000000000000000000000000010000000000000000000000000000000002140000000000000002000000000000000000000000200000000000000020000011000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000002000000041000000000000000000000000000000001004200000000000000000020000000000000200000000000020000000000000000008000000000020000000000000000000000000000000000000000000000000000000000000400000, difficulty: 0x0_U256, number: 96597, gas_limit: 240250000, gas_used: 176717, timestamp: 1715006616, mix_hash: 0x82b4f42b6754c26c8706940b71e2cf3f78b08f025ad0f288e0d10bf74374f7ea, nonce: 0, base_fee_per_gas: Some(99627953), blob_gas_used: None, excess_blob_gas: None, parent_beacon_block_root: None, extra_data: 0x302e31382e302d64657600000000000000000000000000000000000000000000 }
Guest program peak memory used: 4.098204 MB
Generating proof...
WARNING: running SGX in hardware mode!
Current directory: "/opt/raiko/bin"

thread 'tokio-runtime-worker' panicked at /opt/raiko/provers/sgx/prover/src/lib.rs:246:48:
Unable to serialize input: Io(Os { code: 32, kind: BrokenPipe, message: "Broken pipe" })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: task 36 panicked

I have had the same error after stopping the containers and re-initializing them, doing the bootstrap again and registering it again, it already catches the requests

I saw the same error message a couple of days ago when I was trying to generate an SGX proof without running setup/bootstrap first. I don’t know however why the error message is so bad though if this would be the case, you would expect a better error message for something like this so something we need to look into if that’s the case.

Hello @smtmfft . No it’s not normal… I got 16 successful prove transactions and failed at 17th transaction…I can confirm my RPC still working now. Today I don’t have that issue use same config. I just add HTTP:// for this env only TAIKO_NODE_IP

That’s strange… as far as I know only the null entrypoint (especially the beacon one as we call it directly) could report error like these. Let me know if it happens again. Thanks!