Common Problems
На этой ст ранице описаны известные ошибки и предупреждения, с которыми вы можете столкнуться при работе с программным обеспечением Autonomys. Каждая проблема включает в себя уровень серьезности, объяснение и шаги по решению, чтобы помочь вам быстро определить и устранить проблемы.
Быстрая навигация
- Уровни серьезности - понимание показателей серьезности ошибок
- Проблемы программы - Ошибки и предупреждения, связанные с конкретными компонентами (узел, фермер, фермерский кластер)
- Неожиданное поведение - общие проблемы, не связанные с конкретными компонентами
Мы регулярно обновляем это руководство на основе отзывов сообщества и новых релизов.
Проблемы программы
Эти ошибки и предупреждения связаны с конкретными компонентами. В этом разделе мы выделим известные проблемы, предложим доступные шаги по их устранению и укажем уровни их серьезности.
- Node
- Farmer
- Farming Cluster
WARN Consensus: telemetry: ❌ Error while dialing
This error is specifically related to the telemetry server. It may occur occasionally, but it has no impact on farming operations and can be safely ignored.
Error message:
WARN Consensus: telemetry: ❌ Error while dialing /dns/telemetry.subspace.foundation/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Timeout }WARN Consensus: Proof of time chain reorg
This situation arises when two or more valid blocks are created at the same height in the blockchain. Initially, network nodes may disagree on which block to add to the chain, resulting in multiple temporary forks. Once this disagreement is resolved, the blocks from the discarded fork become orphaned, and the chain reorganizes to incorporate the blocks from the winning fork.
Resolution:
This should resolve on its own.
Error message:
WARN Consensus: sc_proof_of_time::source: Proof of time chain reorg happened from_next_slot=<block> to_next_slot=<block>WARN Consensus: Proof of time chain extended
This warning message should not affect your rewards or the operation of your node. It's just a log message indicating the normal operation of the network.
Error message:
WARN Consensus: sc_proof_of_time::source: Proof of time chain was extended from block import from_next_slot=<block> to_next_slot=<block>WARN Consensus: Error when syncing blocks from DSN
When a new node is stood up with the default (snap) syncing method, it will attempt to download segments from the network. If the node is unable to download enough pieces to reconstruct a segment, it will try again.
Error message:
WARN Consensus: subspace_service::sync_from_dsn: Error when syncing blocks from DSN, stopping DSN sync until the next notification error=Other: Failed to download segment pieces during block import: Not enough (127/128) pieces for segment <segment>ERROR: Failed to store piece in cache, no space
This indicates that there is not enough space in the cache to store a new piece of data.
Resolution:
- The drive where you are storing your farm is out of space
- Reduce the farm size and restart the farmer
- Ensure that you are saving the farm to the correct drive and that it is properly mounted
Error message:
ERROR subspace_farmer::farmer_cache: Failed to store piece in cache, there was no space piece_index=<piece>WARN: Failed to plot sector, retrying
This is a known issue that is actively being investigated.
Mitigation:
To help mitigate these errors, run your NATS component on the same system as your Controller, Cache, and Plotter components.
Error message:
WARN {farm_index=3}:{sector_index=1036}: subspace_farmer::single_disk_farm::plotting: Failed to plot sector, retrying in 1s error=Low-level plotting error: Received only <sector> sector bytes out of <bytes> expected bytesНепредвиденное поведение
Эти неожиданные действия не связаны с конкретными компонентами. В этом разделе мы рассмотрим общие вопросы и рассмотрим все имеющиеся меры по их устранению.
No Output and Missing Error Codes (Windows)
If you encounter a situation in Windows where the node produces no output and does not display any error code, it is likely that you simply need to install the latest version of the Visual C++ Redistributable package.
Farmer stuck on plotting
Try restarting your node or farmer. We've observed that when creating larger farms, the process may sometimes seem stalled, but it typically resumes automatically after a while.
No rewards after several days
If you haven't earned any rewards after several days of farming, try these steps:
- Ensure you are using the latest release of either Space Acres Recommended or the CLI
- Confirm that your farmer is active and on the highest block by checking our telemetry server
- Check your balance using Subscan Block Explorer or the Polkadot Explorer
If your problem isn't listed above or the suggested solutions didn't work, reach out to our community:
- Search existing discussions on our Forum
- Get real-time help in our Discord #support channel