-
Notifications
You must be signed in to change notification settings - Fork 85
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: basic troubleshooting page (#111)
- Loading branch information
Showing
3 changed files
with
30 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
# Troubleshooting | ||
|
||
```admonish tip title="Debug logging" | ||
You can enable debug logging for Walrus by setting the environment variable `RUST_LOG=walrus=debug`. | ||
``` | ||
|
||
## Latest binary | ||
|
||
Before undertaking any other steps, make sure you have the [latest `walrus` | ||
binary](./setup.md#installation). If you have multiple versions in different locations, find the | ||
the binary that will actually be used with `which walrus`. | ||
|
||
## Latest Walrus configuration | ||
|
||
The Walrus Devnet and Testnet are wiped periodically and require updating to the latest binary and | ||
configuration. If you get an error like "could not retrieve enough confirmations to certify the | ||
blob", you are probably using an outdated configuration pointing to an inactive Walrus system. In | ||
this case, update your configuration file with the latest [configuration](./setup.md#configuration) | ||
and make sure the CLI uses the intended configuration. | ||
|
||
```admonish tip | ||
The `walrus` client binary prints information about the used configuration when starting execution, | ||
including the path to the Walrus configuration file and the Sui wallet. | ||
``` | ||
|
||
## Correct Sui network configuration | ||
|
||
If you get an error like "the specified Walrus system object does not exist", make sure your wallet | ||
is set up for Sui **Testnet** and you use the latest [configuration](./setup.md#configuration). |