cerc-io/lotus
16
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 27 Wiki Activity

documentation: makes it easier to search for troubleshooting errors in search

Browse Source
This commit is contained in:
@wwwjim 2019-12-18 11:10:24 -08:00
parent 76d01712d7
commit e12c32512c
4 changed files with 20 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
documentation/en/api-troubleshooting.md
View File

@ -1,11 +1,11 @@
# API Troubleshooting # API Troubleshooting
## params ## Types: params
`params` must be an array. If there are no `params` you should still pass an `params` must be an array. If there are no `params` you should still pass an
empty array. empty array.
## TipSet ## Types: TipSet
For methods such as `Filecoin.StateMinerPower`, where the method accepts the For methods such as `Filecoin.StateMinerPower`, where the method accepts the
argument of the type `TipSet`, you can pass `null` to use the current chain argument of the type `TipSet`, you can pass `null` to use the current chain
@ -18,7 +18,7 @@ curl -X POST \
'http://127.0.0.1:1234/rpc/v0' 'http://127.0.0.1:1234/rpc/v0'
``` ```
## Sending a CID ## Types: Sending a CID
If you do not serialize the CID as a If you do not serialize the CID as a
[JSON IPLD link](https://did-ipid.github.io/ipid-did-method/#txref), you will [JSON IPLD link](https://did-ipid.github.io/ipid-did-method/#txref), you will

12
documentation/en/mining-troubleshooting.md
View File

@ -1,6 +1,6 @@
# Mining Troubleshooting # Mining Troubleshooting
## Changing the Filecoin Proof Parameters directory ## Config: Filecoin Proof Parameters directory
If you want to put the **Filecoin Proof Parameters** in a different directory, If you want to put the **Filecoin Proof Parameters** in a different directory,
use the following environment variable: use the following environment variable:
@ -9,7 +9,7 @@ use the following environment variable:
FIL_PROOFS_PARAMETER_CACHE FIL_PROOFS_PARAMETER_CACHE
``` ```
## Bellman Lockfile ## Error: Can't acquire bellman.lock
The **Bellman** lockfile is created to lock a GPU for a process. This bug can The **Bellman** lockfile is created to lock a GPU for a process. This bug can
occur when this file isn't properly cleaned up: occur when this file isn't properly cleaned up:
@ -21,7 +21,7 @@ mining block failed: computing election proof: github.com/filecoin-project/lotus
This bug occurs when the storage miner can't acquire the `bellman.lock`. To fix This bug occurs when the storage miner can't acquire the `bellman.lock`. To fix
it you need to stop the `lotus-storage-miner` and remove `/tmp/bellman.lock`. it you need to stop the `lotus-storage-miner` and remove `/tmp/bellman.lock`.
## Your miner is not ready ## Error: Failed to get api endpoint
```sh ```sh
lotus-storage-miner info lotus-storage-miner info
@ -31,7 +31,7 @@ lotus-storage-miner info
If you see this, that means your **Lotus Storage Miner** isn't ready yet. You If you see this, that means your **Lotus Storage Miner** isn't ready yet. You
need to finish [syncing the chain](https://docs.lotu.sh/en+join-testnet). need to finish [syncing the chain](https://docs.lotu.sh/en+join-testnet).
## Your computer is too slow ## Error: Your computer may not be fast enough
```sh ```sh
CAUTION: block production took longer than the block delay. Your computer may not be fast enough to keep up CAUTION: block production took longer than the block delay. Your computer may not be fast enough to keep up
@ -40,7 +40,7 @@ CAUTION: block production took longer than the block delay. Your computer may no
If you see this, that means your computer is too slow and your blocks are not If you see this, that means your computer is too slow and your blocks are not
included in the chain, and you will not receive any rewards. included in the chain, and you will not receive any rewards.
## Running out of storage ## Error: No space left on device
```sh ```sh
lotus-storage-miner pledge-sector lotus-storage-miner pledge-sector
@ -52,7 +52,7 @@ which by default is the root partition (This is common for Linux setups).
Usually your root partition does not get the largest partition of storage so you Usually your root partition does not get the largest partition of storage so you
will need to change the environment variable to something else. will need to change the environment variable to something else.
## GPU not being used ## Error: GPU unused
If you suspect that your GPU is not being used, first make sure it is properly If you suspect that your GPU is not being used, first make sure it is properly
configured as described in the [testing configuration page](hardware-mining.md). configured as described in the [testing configuration page](hardware-mining.md).

6
documentation/en/setup-troubleshooting.md
View File

@ -1,5 +1,7 @@
# Setup Troubleshooting # Setup Troubleshooting
## Config: Clearing data
Here is a command that will delete your chain data, stored wallets, stored data Here is a command that will delete your chain data, stored wallets, stored data
and any miners you have set up: and any miners you have set up:
@ -11,7 +13,7 @@ This command usually resolves any issues with running `lotus` but it is not
always required for updates. We will share information about when resetting your always required for updates. We will share information about when resetting your
chain data and miners is required for an update in the future. chain data and miners is required for an update in the future.
## Lotus daemon problems ## Error: Failed to connect bootstrap peer
```sh ```sh
WARN peermgr peermgr/peermgr.go:131 failed to connect to bootstrap peer: failed to dial : all dials failed WARN peermgr peermgr/peermgr.go:131 failed to connect to bootstrap peer: failed to dial : all dials failed
@ -34,7 +36,7 @@ ERROR hello hello/hello.go:81 other peer has different genesis!
- You already have another lotus deamon running. - You already have another lotus deamon running.
## Failed messages ## Warning: get message get failed
Some errors will occur that do not prevent Lotus from working: Some errors will occur that do not prevent Lotus from working:

9
documentation/en/storing-data-troubleshooting.md
View File

@ -1,20 +1,25 @@
# Storage Troubleshooting # Storage Troubleshooting
## Error: Routing: not found
```sh ```sh
WARN main lotus/main.go:72 routing: not found WARN main lotus/main.go:72 routing: not found
``` ```
- This miner is offline. - This miner is offline.
## Error: Failed to start deal
```sh ```sh
WARN main lotus/main.go:72 failed to start deal: computing commP failed: generating CommP: Piece must be at least 127 bytes WARN main lotus/main.go:72 failed to start deal: computing commP failed: generating CommP: Piece must be at least 127 bytes
``` ```
- There is a minimum file size of 127 bytes. - There is a minimum file size of 127 bytes.
## Troubleshooting Sealing ## Error: 0kb file response during retrieval
Miners can check sealing progress with this command: In order to retrieve a file, it must be sealed. Miners can check sealing
progress with this command:
```sh ```sh
lotus-storage-miner sectors list lotus-storage-miner sectors list