Golem-Workers troubleshooting
How to find the logs
Problem
Sometimes, especially when something goes wrong, you may need to inspect the logs (or share them with us). While it's straightforward with a manual installation - the logs appear in the consoles where you started golem-node
and golem-workers
- it can be less obvious with a Docker installation.
Solution
You can inspect the logs using the docker compose logs
command. To continuously view new logs as they are generated, use the -f
or --follow
flag.
docker compose logs golem-node -f
docker compose logs web -f
Was this helpful?
'NoneType' is not iterable
stacktrace on create-node
Problem
The create-node
endpoint may occasionally fail. When this happens, it can be helpful to check the Uvicorn logs (docker compose logs web
command). You might encounter a stacktrace that mentions 'NoneType' object is not iterable.
Solution
This error can have multiple causes, but if you're using examples from this documentation, it might indicate that you defined the use of Golem Reputation in the create-cluster
step but forgot to initialize it before starting the service.
To resolve this, refer to the Reputation Section of the Getting Started Guide and ensure that you add GLOBAL_CONTEXT
to your .env
file. Then, restart the golem-workers
service.
Was this helpful?
Getting testnet funds failus
Problem
Sometimes docker compose exec golem-node yagna payment fund
command fails.
Solution
Verify if getting the funds was successful with:
docker compose exec golem-node yagna payment status
The output should show a non-zero amount of tGLM and tETH in the total amount
and gas
columns. Rerun the fund
command if it doesn't.
Was this helpful?
Was this helpful?