Error when startup: code: -32601, message: Method not found, data: None
mhlxs opened this issue · 1 comments
mhlxs commented
A error occured when i start storage node.
Config config.toml
# RPC endpoint to sync event logs on EVM compatible blockchain.
#blockchain_rpc_endpoint = "https://rpc-testnet.0g.ai"
blockchain_rpc_endpoint="http://localhost:26657"Error when startup:
2024-05-18T10:01:49.574455Z INFO zgs_node: Starting services...
2024-05-18T10:01:50.066414Z DEBUG storage::log_store::log_manager: LogManager::new() with chunk_list_len=0 start_tx_seq=Some(0) last_chunk=22
2024-05-18T10:01:50.168410Z DEBUG network::service: Loaded network key from disk.
2024-05-18T10:01:50.193779Z WARN log_entry_sync::sync_manager: unable to get finalized block: Err(JsonRpcClientError(JsonRpcError(JsonRpcError { code: -32601, message: "Method not found", data: None })))
2024-05-18T10:01:50.198436Z DEBUG network::discovery::enr: ENR loaded from disk file="network/enr.dat"
2024-05-18T10:01:50.198684Z INFO network::nat: UPnP Attempting to initialise routes
2024-05-18T10:01:50.198722Z INFO network::service: Libp2p Starting peer_id=16Uiu2HAmF52b7fjW6W2E651Cqr2pcBCxecCwQi4WQ1wT5vD4dNCX bandwidth_config=3-Average
2024-05-18T10:01:50.219336Z DEBUG network::service: Attempting to open listening ports address=0.0.0.0 tcp_port=1234 udp_port=1234
2024-05-18T10:01:50.224224Z INFO network::discovery: ENR Initialised enr=enr:-Hy4QIe3R67ny0z_jpySrA2HlPW4l9d6uF6Hm2-CCGTZtFe4UVq7dVS5IJG9C-qFa1YdV8NOdxvB0DVQ6yn5jbe33rkBgmlkgnY0iXNlY3AyNTZrMaEDI9_YHknFhCr1msvR-3U2Hd75VGCF-swAU1jRVWpngiCDdGNwggTS seq=1 id=0x5675..9878 ip=None udp=None tcp=Some(1234) udp4_socket=None
2024-05-18T10:01:50.245293Z DEBUG discv5::handler: Handler Starting
2024-05-18T10:01:50.245313Z DEBUG discv5::socket::send: Send handler starting
2024-05-18T10:01:50.245312Z DEBUG discv5::socket::recv: Recv handler starting
2024-05-18T10:01:50.269505Z DEBUG network::discovery: Discovery service started
2024-05-18T10:01:50.269518Z INFO network::discovery: Contacting Multiaddr boot-nodes for their ENR
2024-05-18T10:01:50.269604Z INFO discv5::service: Discv5 Service started
2024-05-18T10:01:50.294429Z DEBUG discv5::service: Sending RPC Request: id: 41a42b23207dc9ce: FINDNODE Request: distance: [0] to node: Node: 0xc909..1134, addr: 54.219.26.22:1234
2024-05-18T10:01:50.294448Z DEBUG discv5::service: Sending RPC Request: id: eadc02f03c26edc0: FINDNODE Request: distance: [0] to node: Node: 0x3ec9..8916, addr: 52.52.127.117:1234
2024-05-18T10:01:50.373567Z DEBUG discv5::service: Received RPC response: NODES: total: 1, Nodes: [ENR: NodeId: 0xc909..1134, IpV4 Socket: None IpV6 Socket: None] to request: FINDNODE Request: distance: [0] from: Node: 0xc909..1134, addr: 54.219.26.22:1234
2024-05-18T10:01:50.373631Z DEBUG network::discovery: Adding node to routing table node_id=0xc909..1134 peer_id=16Uiu2HAmTVDGNhkHD98zDnJxQWu3i1FL1aFYeh9wiQTNu4pDCgps ip=None udp=None tcp=Some(1234)
2024-05-18T10:01:50.373641Z WARN discv5::discv5: ENR attempted to be added without a UDP socket has been ignored
2024-05-18T10:01:50.373646Z ERROR network::discovery: Could not add peer to the local routing table addr=/ip4/54.219.26.22/udp/1234/p2p/16Uiu2HAmTVDGNhkHD98zDnJxQWu3i1FL1aFYeh9wiQTNu4pDCgps error=ENR has no UDP socket to connect to
2024-05-18T10:01:50.211120Z ERROR log_entry_sync::sync_manager: log sync failure: e=(code: -32601, message: Method not found, data: None)
Stack backtrace:
0: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
1: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
2: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
3: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
4: <futures_util::future::future::flatten::Flatten<Fut,<Fut as core::future::future::Future>::Output> as core::future::future::Future>::poll
5: tokio::runtime::task::core::Core<T,S>::poll
6: tokio::runtime::task::harness::Harness<T,S>::poll
7: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
8: tokio::runtime::scheduler::multi_thread::worker::Context::run
9: tokio::runtime::context::scoped::Scoped<T>::set
10: tokio::runtime::context::runtime::enter_runtime
11: tokio::runtime::scheduler::multi_thread::worker::run
12: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
13: tokio::runtime::task::core::Core<T,S>::poll
14: tokio::runtime::task::harness::Harness<T,S>::poll
15: tokio::runtime::blocking::pool::Inner::run
16: std::sys_common::backtrace::__rust_begin_short_backtrace
17: core::ops::function::FnOnce::call_once{{vtable.shim}}
18: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/alloc/src/boxed.rs:2007:9
19: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/alloc/src/boxed.rs:2007:9
20: std::sys::unix::thread::Thread::new::thread_start
at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/sys/unix/thread.rs:108:17
21: <unknown>
22: <unknown>
2024-05-18T10:01:50.406093Z INFO zgs_node::client::environment: Internal shutdown received reason="log sync failure"
2024-05-18T10:01:50.406111Z INFO zgs_node: Shutting down... reason=Failure("log sync failure")
2024-05-18T10:01:50.406135Z DEBUG task_executor: Async task shutdown, exit received task="log_reload"
mhlxs commented
把端口改为 `` 即可：
blockchain_rpc_endpoint = "http://localhost:8545"