pherry这个错误如何解决
各位大佬节点node这个报错是什么意思呢,矿机mining中,俩天了收益为O
021-09-20 04:40:43 [Parachain] Error while dialing /dns/telemetry.polkadot.io/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Timeout }
2021-09-20 04:40:44 [Parachain] Idle (20 peers), best: #427728 (0x1387…779d), finalized #427726 (0xfd9b…b187), 2.4kiB/s 5.6kiB/s
2021-09-20 04:40:44 [Relaychain] Idle (29 peers), best: #9303148 (0x5d3e…6d54), finalized #9303145 (0x721e…7f9e), 322.4kiB/s 559.2kiB/s
2021-09-20 04:40:48 [Parachain] Imported #427729 (0x9aba…13c3)
2021-09-20 04:40:48 [Relaychain] Imported #9303149 (0x0153…0333)
2021-09-20 04:40:49 [Parachain] Idle (20 peers), best: #427728 (0x1387…779d), finalized #427726 (0xfd9b…b187), 2.5kiB/s 12.5kiB/s
看看pruntime那边日志,卡住的时候最后几条日志有没有什么错误信息
统一回复,Mining没收益的问题正在看,这两天会出结论
仔细看1楼,写了这个问题的解决方案
exit看看每日问题总结帖
百度网盘不支持20G以上的文件 没办法了,可以试试迅雷
同步慢,解决方案是重新安装最新的脚本,应该每秒100个块左右
输入GAS账户的助记词提示余额不足,但实际账户中余额是足够的,麻烦看下什么原因?谢谢
更新本地node.js到v14
这怎么更新啊 具体命令是什么啊 不好意思 麻烦你了
我也碰到这个问题了 怎么解决的?
请问node总是死掉。报错是上面这个是什么问题。
2021-09-23 04:26:31 [Relaychain] Re-finalized block #0x0d0ca217ddc7f1aecf3b8dc9d4f0951486cef6888e5d7caf90e01e8b45a82523 (9346003) in the canonical chain, current best finalized is #9346003
2021-09-23 04:27:52 [Parachain] Error while dialing /dns/telemetry.polkadot.io/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Other(B(A(Tls(Io(Custom { kind: UnexpectedEof, error: “tls handshake eof” }))))) }
2021-09-23 04:29:46 [Parachain] Error while dialing /dns/telemetry.polkadot.io/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Other(B(A(Tls(Io(Custom { kind: UnexpectedEof, error: “tls handshake eof” }))))) }
2021-09-23 04:30:27 [Parachain] Error while dialing /dns/telemetry.polkadot.io/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Timeout }
./start_node.sh: line 66: 10 Killed $WORK_PATH/khala-node --chain $PARACHAIN --base-path $DATA_PATH --name $NODE_NAME --port 30333 --prometheus-port 9615 --rpc-port 9933 --ws-port 9944 --prometheus-external --ws-external --rpc-cors all $PARACHAIN_ROLE_ARGS $PARACHAIN_EXTRA_ARGS – --chain $RELAYCHAIN --port 30334 --prometheus-port 9616 --rpc-port 9934 --ws-port 9945 --prometheus-external --ws-external --rpc-cors all $RELAYCHAIN_ROLE_ARGS $RELAYCHAIN_EXTRA_ARGS
Starting Khala node as role ‘MINER’ with extra parachain args ‘–state-cache-size 671088640 --db-cache 2048 --max-runtime-instances 16’ extra relaychain args ‘–state-cache-size 671088640 --db-cache 2048 --max-runtime-instances 16’
每次都在差不多的高度死掉么?还是运行一段时间之后才死掉?另外可以关注一下电脑的内存和磁盘占用
这个错误显示的是连接链节点的时候超时
你是用solo挖矿脚本么?有没有修改过端口号之类的?
Khala,kusama都同步成功了,但Pherry一直为0,升级了脚本,也更新了docker image,但还是一直为0,请教大佬相助, 感激不尽!!
打印消息如下:
[2021-09-23T10:05:11Z INFO pherry] Connected to substrate at: ws://phala-node:9945
[2021-09-23T10:05:11Z WARN substrate_subxt] The following types do not have registered type segmenters: {“ParachainSystem::ValidationFunctionApplied::RelayChainBlockNumber”, “PhalaMining::MinerUnbound::WorkerPublicKey”, “PhalaRegistry::GatekeeperAdded::WorkerPublicKey”, “PhalaMining::InternalErrorMinerSettleFailed::WorkerPublicKey”, “PhalaStakePool::PoolWorkerAdded::WorkerPublicKey”, “PhalaStakePool::RewardDismissedNotInPool::WorkerPublicKey”, “ParachainSystem::ValidationFunctionStored::RelayChainBlockNumber”, “PhalaMining::MinerBound::WorkerPublicKey”, “CollatorSelection::NewInvulnerables::T::AccountId”, “ParachainSystem::DownwardMessagesProcessed::Weight”, “ParachainSystem::DownwardMessagesProcessed::relay_chain::Hash”} If any events containing these types are received, this can cause a TypeSizeUnavailable
error and prevent decoding the actual event being listened for.Use ClientBuilder::register_type_size
to register missing type sizes.
[2021-09-23T10:05:11Z INFO pherry] Connected to parachain node at: ws://phala-node:9944
[2021-09-23T10:05:11Z INFO pherry] Waiting for substrate to sync blocks…
[2021-09-23T10:05:11Z INFO pherry] Checking synced: current=9349423 highest=Some(9349423)
[2021-09-23T10:05:11Z INFO pherry] Checking synced: current=446023 highest=Some(446023)
[2021-09-23T10:05:11Z INFO pherry] Substrate sync blocks done
thread ‘main’ panicked at ‘Bad privkey derive path: InvalidPhrase’, standalone/pherry/src/main.rs:905:10
note: run with RUST_BACKTRACE=1
environment variable to display a backtrace
dell@dell-PowerEdge-R230:~$