sui
sui copied to clipboard
MystenLabs
When starting a node with mainnet genesis, the log comes out and then nothing happens, what could be the reason?
log example
2023-05-03T12:40:56.507397Z INFO sui_node::admin: starting admin server filter=info address=127.0.0.1:1337
config example
`db-path: "/opt/sui/db"
network-address: "/dns/localhost/tcp/8080/http" metrics-address: "0.0.0.0:9184" this address is also used for web socket connections json-rpc-address: "0.0.0.0:9000" enable-event-processing: true
genesis: Update this to the location of where the genesis file is stored genesis-file-location: "/opt/sui/conf/genesis.blob"
authority-store-pruning-config: num-latest-epoch-dbs-to-retain: 3 epoch-db-pruning-period-secs: 3600 num-epochs-to-retain: 1 max-checkpoints-in-batch: 10 max-transactions-in-batch: 1000 use-range-deletion: true pruning-run-delay-seconds: 60`
me too, the logs having been 2 hours like this
2023-05-04T04:17:43.693857Z INFO sui_node: Sui Node version: 1.0.0-ae1212baf 2023-05-04T04:17:43.694875Z INFO sui_node: Supported protocol versions: Some(SupportedProtocolVersions { min: ProtocolVersion(1), max: ProtocolVersion(9) }) 2023-05-04T04:17:43.695625Z INFO sui_node: Started Prometheus HTTP endpoint at 0.0.0.0:9184 2023-05-04T04:17:43.702406Z INFO sui_node: Initializing sui-node listening on /dns/localhost/tcp/8080/http node=k#acceb3b9fefbe401a0fc3d540e2875dd5792cbf4139360c29a5039df9f5c921ab1f38d0ae19a39f11cefa9247feb7bc2116b3b9f8b13f0de0da4209778bbd980fced13be4e94103a47b77047496846c92e5a371e254a07b586377c87ec7ebcb6 2023-05-04T04:17:44.540869Z INFO sui_core::authority::authority_per_epoch_store: in_memory_checkpoint_roots = true 2023-05-04T04:17:44.880602Z INFO sui_node: P2p network started on 0.0.0.0:8080 2023-05-04T04:17:44.881992Z INFO sui_network::discovery: Discovery started 2023-05-04T04:17:44.882020Z INFO sui_core::authority: current protocol version is now ProtocolVersion(4) 2023-05-04T04:17:44.882025Z INFO sui_core::authority: supported versions are: SupportedProtocolVersions { min: ProtocolVersion(1), max: ProtocolVersion(9) } 2023-05-04T04:17:44.882029Z INFO connection-manager{peer=4216afdf}: anemo::network::connection_manager: ConnectionManager started 2023-05-04T04:17:44.882209Z INFO sui_network::state_sync: State-Synchronizer started 2023-05-04T04:17:44.924358Z INFO sui_core::execution_driver: Starting pending certificates execution process. 2023-05-04T04:17:45.155944Z INFO sui_json_rpc: acl=Const("*") 2023-05-04T04:17:45.159537Z INFO sui_node: SuiNode started! 2023-05-04T04:17:45.159599Z INFO narwhal_network::connectivity: Spawning future narwhal/network/src/connectivity.rs:ConnectionMonitor 2023-05-04T04:17:45.159712Z INFO sui_node::admin: starting admin server filter=info address=127.0.0.1:1337 2023-05-04T04:17:45.161113Z INFO schedule_checkpoint{seq=0 epoch=0}: sui_core::checkpoints::checkpoint_executor: Checkpoint preparation for execution took 568.552��s 2023-05-04T04:17:45.168985Z INFO sui_core::checkpoints::checkpoint_executor: Checkpoint execution took 7.877459ms seq=0 2023-05-04T04:17:45.169018Z INFO sui_core::checkpoints::checkpoint_executor: Finished syncing and executing checkpoint 0 2023-05-04T04:46:58.634815Z INFO connection{remote_addr=172.18.0.1:34426 conn_id=0}: jsonrpsee_server::server: Accepting new connection 1/4294967295 2023-05-04T04:47:00.998004Z INFO connection{remote_addr=172.18.0.1:34432 conn_id=1}: jsonrpsee_server::server: Accepting new connection 1/4294967295 2023-05-04T04:47:02.436056Z INFO connection{remote_addr=172.18.0.1:34444 conn_id=2}: jsonrpsee_server::server: Accepting new connection 1/4294967295 2023-05-04T04:47:03.211354Z INFO connection{remote_addr=172.18.0.1:34448 conn_id=3}: jsonrpsee_server::server: Accepting new connection 1/4294967295 2023-05-04T04:47:03.978803Z INFO connection{remote_addr=172.18.0.1:34456 conn_id=4}: jsonrpsee_server::server: Accepting new connection 1/4294967295 2023-05-04T04:47:04.777203Z INFO connection{remote_addr=172.18.0.1:36878 conn_id=5}: jsonrpsee_server::server: Accepting new connection 1/4294967295 2023-05-04T05:39:39.936355Z INFO connection{remote_addr=172.18.0.1:46440 conn_id=6}: jsonrpsee_server::server: Accepting new connection 1/4294967295 2023-05-04T05:39:39.936490Z INFO connection{remote_addr=172.18.0.1:46440 conn_id=6}:get_latest_checkpoint_sequence_number: sui_json_rpc::read_api: success 2023-05-04T05:39:42.244120Z INFO connection{remote_addr=172.18.0.1:46442 conn_id=7}: jsonrpsee_server::server: Accepting new connection 1/4294967295 2023-05-04T05:39:43.110819Z INFO connection{remote_addr=172.18.0.1:46452 conn_id=8}: jsonrpsee_server::server: Accepting new connection 1/4294967295 2023-05-04T05:39:57.544099Z INFO connection{remote_addr=172.18.0.1:58750 conn_id=9}: jsonrpsee_server::server: Accepting new connection 1/4294967295 2023-05-04T05:44:06.081682Z INFO connection{remote_addr=172.18.0.1:54602 conn_id=10}: jsonrpsee_server::server: Accepting new connection 1/4294967295
i think problem will be happen when configuration file does not configure P2P-config，like this
The following addition made the sync work. However, the sync does not progress beyond epoch 23.
p2p-config: seed-peers: - address: /dns/icn-00.mainnet.sui.io/udp/8084 peer-id: 303f1f35afc9a6f82f8d21724f44e1245f4d8eca0806713a07c525dadda95a66 - address: /dns/icn-01.mainnet.sui.io/udp/8084 peer-id: cb7ce193cf7a41e9cc2f99e65dd1487b6314a57c74be42cc8c9225b203301812 - address: /dns/mel-00.mainnet.sui.io/udp/8084 peer-id: d32b55bdf1737ec415df8c88b3bf91e194b59ee3127e3f38ea46fd88ba2e7849 - address: /dns/mel-01.mainnet.sui.io/udp/8084 peer-id: bbf3be337fc16614a1953da83db729abfdc40596e197f36fe408574f7c9b780e - address: /dns/ewr-00.mainnet.sui.io/udp/8084 peer-id: c7bf6cb93ca8fdda655c47ebb85ace28e6931464564332bf63e27e90199c50ee - address: /dns/ewr-01.mainnet.sui.io/udp/8084 peer-id: 3227f8a05f0faa1a197c075d31135a366a1c6f3d4872cb8af66c14dea3e0eb66 - address: /dns/sjc-00.mainnet.sui.io/udp/8084 peer-id: 6f0b25087cd6b2fd2e4329bcf308ac95a37c49277dd7286b72470c124809db5b - address: /dns/sjc-01.mainnet.sui.io/udp/8084 peer-id: af1d5d8468b3612ac2b6ff3ca91e99a71390dbe5b83dea9f6ae2da708d689227 - address: /dns/lhr-00.mainnet.sui.io/udp/8084 peer-id: c619a5e0f8f36eac45118c1f8bda28f0f508e2839042781f1d4a9818043f732c - address: /dns/lhr-01.mainnet.sui.io/udp/8084 peer-id: 53dcedf250f73b1ec83250614498947db00d17c0181020fcdb7b6db12afbc175
https://github.com/testnet-pride/Node-manuals/blob/main/Testnets/Sui/mainnet.md
@timurgum thanks for flagging this. I expect that this has been fixed since the launch, so I will close it. If you still encounter problems with this, please file a new issue.
