-
Notifications
You must be signed in to change notification settings - Fork 85
Troubleshooting
Like other cryptocurrencies, newly mined coins are time locked, so mined coins can’t be spent immediately. The lock time, a.k.a. COINBASE_MATURITY, is set to 1000 blocks on testnet1.
This is your wallet base URL, something like http://1.2.3.4:13415 NOTE: Run `grin wallet -e listen` to make your wallet reachable from outside.
Possible workaround is rm -rf .grin/peers/* then restart.
Yes, this still happens quite often. You’ll need to babysit grin. Very welcome any solutions to give grin a “watchdog” solution that can restart grin in case of trouble.
You might want to remove any previous rust installations to avoid conflicts. Use `rustup` to [reinstall rust and cargo as described](build.md).
NOTE: If you install rust or cargo with your package manager (most Linuxes anno 2017) you’ll get too old versions. On Debian, you might have to manually compile cmake or get it from non-detault repositories.
Run `cargo update` to fix this
Chech `rustc –version` and note that bitflags requires rust 1.21 or newer. Install via `rustup` and recommended you also remove any rust/cargo installed via your package manager.
If librocksdb-sys fails to build, try symlinking stddef.h and stdarg.h from the gcc5 include directory. So probably from /usr/lib to /usr/include
On Ubuntu install the zlib development headers: `apt install zlib1g-dev`.
On Ubuntu install the ncurses development headers: `apt install libncursesw5-dev`.
Run `CUDA_HOST_COMPILER=gcc-6 cargo build` instead of `cargo build`.
Build error: The `src/cuckoo_sys/plugins/cuckoo` directory is empty. Did you forget to pull the submodules?
Try `git submodule update –init –recursive`
./grin-doctor.sh
echo “API is $GRIN_API”
GRIN_API="localhost:13413"
echo “Asking API for chain status…”
curl "http://$GRIN_API/v1/chain"
echo “Asking grin for client status”
grin client status
echo “Asking API for connected peers”
curl "http://$GRIN_API/v1/peers/connected"
echo “Asking wallet for info”
grin wallet info
Basics
- Getting Started
- User Documentation
- MimbleWimble
- FAQ
- Planned releases (Roadmap)
- Code of Conduct
Contributing
- Contributing Guide
- Code Structure
- Code coverage and metrics
- Code Reviews and Audits
- Adding repos to /mimblewimble
Development
Mining
Infrastructure
Exchange integrations
R&D
Grin Community
Grin Governance
Risk Management
Grin Internals
- Block Header Data Structure
- Detailed validation logic
- P2P Protocol
Misc