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 -fdocker compose logs web -f
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. You might encounter a stacktrace that mentions NoneType 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.