【🔥疑难问题】Khala挖矿疑难问题收集

这个应该能解决问题

刚开始 是pherry 退出 HeaderHashMismatch，按照教程删除khala的数据从新同步之后出现新的报错 Request timeout 要怎么处理呢
[2021-10-03T06:02:00Z INFO pherry] get_block: Got block Some(9027070) hash 0xfff1…4c37
[2021-10-03T06:02:00Z INFO pherry] get_block: Got block Some(9027071) hash 0xad4d…94a5
[2021-10-03T06:02:00Z INFO pherry] get_block: Got block Some(9027072) hash 0x7a75…ff27
[2021-10-03T06:02:00Z INFO pherry] get_block: Got block Some(9027073) hash 0x16e5…fa01
[2021-10-03T06:02:01Z INFO pherry] sending a batch of 511 headers (last: 9027072, change: None)
[2021-10-03T06:02:01Z INFO phactory_api::pruntime_client] Response: 200 OK
[2021-10-03T06:02:01Z INFO pherry] …sync_header: SyncedTo { synced_to: 9027072 }
[2021-10-03T06:03:01Z INFO pherry] bridge() exited with result: Err(parachain id not found)
[2021-10-03T06:03:02Z WARN substrate_subxt] The following types do not have registered type segmenters: {“ParaInclusion::CandidateTimedOut::CandidateReceipt<T::Hash>”, “Gilt::BidRetracted::BalanceOf”, “ParaInclusion::CandidateIncluded::HeadData”, “Ump::ExecutedUpward::MessageId”, “ParaInclusion::CandidateBacked::HeadData”, “Hrmp::OpenChannelAccepted::ParaId”, “ParaInclusion::CandidateIncluded::GroupIndex”, “Paras::CurrentHeadUpdated::ParaId”, “Crowdloan::Created::ParaId”, “Slots::Leased::LeasePeriod”, “Paras::NewHeadNoted::ParaId”, “Registrar::Deregistered::ParaId”, “Registrar::Reserved::ParaId”, “ParaInclusion::CandidateBacked::GroupIndex”, “Slots::Leased::ParaId”, “Ump::WeightExhausted::MessageId”, “Hrmp::ChannelClosed::HrmpChannelId”, “ParaInclusion::CandidateBacked::CandidateReceipt<T::Hash>”, “Ump::UpwardMessagesReceived::ParaId”, “Gilt::GiltThawed::ActiveIndex”, “Crowdloan::AddedToNewRaise::ParaId”, “Crowdloan::MemoUpdated::ParaId”, “Hrmp::OpenChannelRequested::ParaId”, “ParaInclusion::CandidateIncluded::CandidateReceipt<T::Hash>”, “Crowdloan::Dissolved::ParaId”, “Gilt::BidPlaced::BalanceOf”, “Gilt::GiltIssued::ActiveIndex”, “Ump::ExecutedUpward::Outcome”, “Ump::InvalidFormat::MessageId”, “Registrar::ParaId”, “Auctions::AuctionStarted::AuctionIndex”, “ParaInclusion::CandidateTimedOut::CoreIndex”, “ParaInclusion::CandidateIncluded::CoreIndex”, “Crowdloan::Edited::ParaId”, “Ump::WeightExhausted::Weight”, “ParaInclusion::CandidateTimedOut::HeadData”, “Auctions::AuctionStarted::LeasePeriod”, “Slots::NewLeasePeriod::LeasePeriod”, “Auctions::AuctionClosed::AuctionIndex”, “Auctions::WinningOffset::AuctionIndex”, “Claims::Claimed::EthereumAddress”, “XcmPallet::Sent::MultiLocation”, “XcmPallet::Sent::Xcm<()>”, “ParaInclusion::CandidateBacked::CoreIndex”, “Crowdloan::AllRefunded::ParaId”, “XcmPallet::Attempted::xcm::v0::Outcome”, “Paras::CodeUpgradeScheduled::ParaId”, “Paras::ActionQueued::ParaId”, “Gilt::GiltIssued::BalanceOf”, “Hrmp::ChannelClosed::ParaId”, “Crowdloan::HandleBidResult::ParaId”, “Auctions::BidAccepted::LeasePeriod”, “Gilt::GiltThawed::BalanceOf”, “Auctions::BidAccepted::ParaId”, “Ump::UnsupportedVersion::MessageId”, “Auctions::ReserveConfiscated::ParaId”, “Crowdloan::Withdrew::ParaId”, “Crowdloan::Contributed::ParaId”, “Crowdloan::PartiallyRefunded::ParaId”, “Gilt::GiltIssued::T::BlockNumber”, “Paras::CurrentCodeUpdated::ParaId”} 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-10-03T06:03:02Z INFO pherry] Connected to substrate at: ws://phala-node:9945
[2021-10-03T06:04:02Z INFO pherry] bridge() exited with result: Err(Rpc error: Request timeout

矿机stop了，然后矿机remove，又重新addworker到之前池子，质押9天了一直未释放，还是Releasing Stake状态，怎么处理？看大家的问题十多天了也没有释放，官方bug吗？

凑合看下英文版

感觉是节点没连上

[2021-12-01T14:53:28Z INFO pherry] sending a batch of 512 headers (last: 9866431, change: None)
[2021-12-01T14:53:29Z INFO phactory_api::pruntime_client] Response: 400 Bad Request
[2021-12-01T14:53:29Z INFO pherry] bridge() exited with error: DecodeError(DecodeError { description: “Could not decode GenericHeaderToSync::header:\n\tCould not decode Header::digest:\n\t\tCould not decode Digest::logs:\n\t\t\tCould not decode DigestItemType, variant doesn’t exist\n”, stack: [] })
这是什么情况，升级几遍了，还是在这里卡住，各种方法都尝试了

捕获1203×700 29.5 KB

捕获1666×457 22.2 KB

2021年 12月2日 天气晴
正常在跑的2台 凌晨半夜 被停止和移除worker 自己未操作移除和停止，这是链上bug还是可能我助记词泄露。
还是哪只傻狗 捣乱

查看下是不是pool有了withdraw，没有足够的free，会被系统stop

都是自己质押的， 没有撤退，好不容易多攒了2000+V值

应该是pruntime的版本过低，你看看能不能升级一下pruntime的docker image

浏览器里面出现的操作是你自己做的么？如果不是的话，就可能是私钥泄漏了

需要升级pherry

浏览器不是自己操作的。跑了3个月，吃席了

gg了，有钱赶紧往外转吧

之前卡在613660 执行了rm -rf /var/khala-dev-node/chains/khala/
现在卡在962355上了。
这是为啥~！怎么解决？
难道再删一次？

重启区块同步的容器