Troubleshooting
If you encounter errors or your full node stops working, run the commands in the following section to resolve the issue.
Issues during setup
- Systemd
- Docker
Error: cannot find -lpq
If, during the compilation step, you receive a cannot find -lpq
error, you are missing the libpq
library.
Use sudo apt-get install libpq-dev
to install on Linux, or brew install libpq
on MacOS.
After you install on MacOS, create a Homebrew link using brew link --force libpq
.
For further context, reference the issue on Stack Overflow.
Error: Listener: Address already in use
If you receive the following error:
panicked at error binding to 0.0.0.0:9184: error creating server listener: Address already in use (os error 98)
Update the metrics address in your fullnode.yaml
file to use port 9180
.
metrics-address: "0.0.0.0:9180"
No known issues with the docker setup yet.
Inspecting the state of a running node
- Systemd
- Docker
Looking at the logs for specific errors:
journalctl -u iota-node -f
Looking at the logs for specific errors:
docker compose logs iota-node -f
Connecting to a shell inside the container:
docker exec -it $CONTAINER_ID /bin/bash
Inspecting the database:
ls -la iotadb/
Reinstalling the node from scratch
If you continue to see issues, do the following steps:
- Systemd
- Docker
To re-install your node from scratch, run the same script you used to install it:
NETWORK="testnet" bash -i <(curl -sSf https://raw.githubusercontent.com/iotaledger/iota/refs/heads/develop/setups/fullnode/systemd/setup.sh)
Re-use the same network (testnet
, mainnet
, devnet
) your node is already running on.
Stop the full node
docker compose down
Delete the data folder Make sure to first make a backup of your config files
rm -Rf data/
Pull the latest version of the container
docker compose pull
Run the prepare script again
./prepare.sh
Start the container again
docker compose up
Local RPC Connectivity Issues
Update the json-rpc-address
in the full node config to listen on all addresses:
sed -i 's/127.0.0.1/0.0.0.0/' fullnode.yaml
-json-rpc-address: "127.0.0.1:9000"
+json-rpc-address: "0.0.0.0:9000"