"waiting for datastore" until I restart service

Troubleshooting
1

I recently did a fresh install of Raspberry Pi OS on my pi and then installed brewblox.

I believe everything installed correctly but when I boot the pi and then go to the UI it just says “waiting for datastore”. If I run the commands “brewblox-ctl up” or “brewblox-ctl restart” the UI then loads correctly but the fix isn’t sustained after restarting the pi.

I should note that before I did all this, the UI loaded no problem without manually starting/restarting the services.

Any idea how to go about fixing this?

Thanks!

David

2

Could you please run brewblox-ctl log?

3

Yes I supposed I should’ve done that to begin with:

Not sure if it matters but this log was written while the “waiting for datastore” problem was still occurring on this particular pi boot:

https://termbin.com/3j6o

The log command itself also threw this error:

INFO Log file: /home/pi/brewblox/brewblox.log
INFO Writing Brewblox .env values…
INFO Writing service logs…
INFO Writing docker-compose configuration…
INFO Writing Spark blocks…
HTTPSConnectionPool(host=‘localhost’, port=443): Max retries exceeded with url: /spark-one/blocks/all/read (Caused by NewConnectionError(’<urllib3.connection.VerifiedHTTPSConnection object at 0xb5c44d50>: Failed to establish a new connection: [Errno 111] Connection refused’))
INFO Writing dmesg output…
INFO Uploading brewblox.log to termbin.com…

This one was written after all the services were restarted and the UI was loaded:

https://termbin.com/x2td

There were no errors writing the log after the services were restarted.

4

If I understand correctly, the datastore issue is now gone?

5

Restarting the services fixes the issue but it comes back every time I restart the pi.

6

After restarting the Pi, what is the output of docker ps?

7

Your log contains warnings about undervoltage detected. Your pi is not getting enough power.

8

Right after boot:

image
image2492×228 66.7 KB

After “brewblox-ctl up”:

image
image2556×430 86.7 KB

9

Yeah I took it out of the enclosure and powered it from my computer USB to try to debug it, the problem existed before as well.

10

It looks like a flag is missing in the traefik service.

Edit: we had a few other changes, so decided to release a small update now. The fix to the traefik service is included here.
If you already updated your docker-compose.yml file, you can remove the restart: unless-stopped flag there.

11

just updated and is working perfectly, thanks a ton!