fe52c47570
This: * Re-organizes the docs into sections that align with what docs.filecoin.io becoming: * An installation section * A "getting started" section (lotus client focused) * A "storing" section (lotus client focused) * A "mining" section (miner focused) * A "build" section (developer focused) * An legacy "architecture" section is left in the last place. A few high-value documentation pages have been reviewed and updated with the latest recommendations: * Installation section and lotus setup * Miner setup * etc. ... Other pages have been correctly merged into the new relevant sections. Some pages have not been touched. The filesystem layout of the documentation has been changed into folders corresponding to the sections (as requested by @cw). Some pages that were not linked at all and/or where hidden, have been moved to "unclassified". This should make the porting of the Lotus documentation to docs.filecoin.io much easier, while ensuring it is more up to date than it was before. For the moment, this breaks most links as link-aliasing is not supported in lotus-docs.
58 lines
2.0 KiB
Markdown
58 lines
2.0 KiB
Markdown
# Setup Troubleshooting
|
|
|
|
|
|
## Error: initializing node error: cbor input had wrong number of fields
|
|
|
|
This happens when you are starting Lotus which has been compiled for one network, but it encounters data in the Lotus data folder which is for a different network, or for an older incompatible version.
|
|
|
|
The solution is to clear the data folder (see below).
|
|
|
|
## Config: Clearing data
|
|
|
|
Here is a command that will delete your chain data, stored wallets, stored data and any miners you have set up:
|
|
|
|
```sh
|
|
rm -rf ~/.lotus ~/.lotusminer
|
|
```
|
|
|
|
Note you do not always need to clear your data for [updating](en+update).
|
|
|
|
## Error: Failed to connect bootstrap peer
|
|
|
|
```sh
|
|
WARN peermgr peermgr/peermgr.go:131 failed to connect to bootstrap peer: failed to dial : all dials failed
|
|
* [/ip4/147.75.80.17/tcp/1347] failed to negotiate security protocol: connected to wrong peer
|
|
```
|
|
|
|
- Try running the build steps again and make sure that you have the latest code from GitHub.
|
|
|
|
```sh
|
|
ERROR hello hello/hello.go:81 other peer has different genesis!
|
|
```
|
|
|
|
- Try deleting your file system's `~/.lotus` directory. Check that it exists with `ls ~/.lotus`.
|
|
|
|
```sh
|
|
- repo is already locked
|
|
```
|
|
|
|
- You already have another lotus daemon running.
|
|
|
|
## Config: Open files limit
|
|
|
|
Lotus will attempt to set up the file descriptor (FD) limit automatically. If that does not work, you can still configure your system to allow higher than the default values.
|
|
|
|
On most systems you can check the open files limit with:
|
|
|
|
```sh
|
|
ulimit -n
|
|
```
|
|
|
|
You can also modify this number by using the `ulimit` command. It gives you the ability to control the resources available for the shell or process started by it. If the number is below 10000, you can change it with the following command prior to starting the Lotus daemon:
|
|
|
|
```sh
|
|
ulimit -n 10000
|
|
```
|
|
|
|
Note that this is not persisted and that systemd manages its own FD limits for services. Please use your favourite search engine to find instructions on how to persist and configure FD limits for your system.
|