Skip to main content

Troubleshooting

Resolve common issues with the Walrus CLI, configuration, and network connectivity.

Use the latest binary​

Before undertaking any other steps, make sure you have the latest walrus binary. If you have multiple versions in different locations, find the binary that is actually used with which walrus.

Check for old hardware or incompatible VMs​

The standard Ubuntu binary causes problems on certain old hardware and in certain virtualized environments. If you experience errors like Illegal instruction (core dumped), install the ubuntu-x86_64-generic version instead, which is compiled to be compatible with almost all physical and virtual x86-64 CPUs.

Verify 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 the correct Sui network (Mainnet or Testnet) and you use the latest configuration.

Update to latest Walrus configuration​

Walrus Testnet is wiped periodically and requires 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. Update your configuration file with the latest configuration and make sure the CLI uses the intended configuration.

tip

When you set RUST_LOG=info, the walrusclient binary prints information about the configuration it uses when starting execution, including the path to the Walrus configuration file and the Sui wallet.

Enable debug logging​

You can enable debug logging for Walrus by setting the environment variable RUST_LOG=walrus=debug. The debug and trace levels provide a more detailed understanding of what a command does or how it fails.

$ RUST_LOG=walrus=debug walrus store file.txt --epochs 5