BrewBlox install issue

The service is logging a lot of errors that it fails to parse messages from the Spark. Did you flash the BrewBlox firmware?

The error doesn’t show the exact message though. I’ll add that to today’s release.

I did perform that step but will go back and try again today.

I just tried to flash it again and here’s what I get from my SSH session.

pi@rasbrewpi:~/brewblox $ brewblox-ctl flash
Please press ENTER when your Spark is connected over USB
The following shell commands will be used:

     docker-compose down
     docker pull brewblox/firmware-flasher:rpi-edge
     docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge trigger-dfu
     docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge flash

Press ENTER to continue, Ctrl+C to cancel

Running command:
docker-compose down

Removing network brewblox_default
WARNING: Network brewblox_default not found.

Running command:
docker pull brewblox/firmware-flasher:rpi-edge

Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Traceback (most recent call last):
File “/usr/local/bin/brewblox-ctl”, line 11, in
sys.exit(main())
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/main.py”, line 81, in main
cli()
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 764, in call
return self.main(*args, **kwargs)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 717, in main
rv = self.invoke(ctx)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 555, in invoke
return callback(*args, **kwargs)
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/commands.py”, line 147, in flash
utils.run_all(shell_commands)
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/utils.py”, line 130, in run_all
return [run(cmd) for cmd in shell_cmds]
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/utils.py”, line 130, in
return [run(cmd) for cmd in shell_cmds]
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/utils.py”, line 124, in run
return check_call(shell_cmd, shell=True, stderr=STDOUT)
File “/usr/lib/python3.5/subprocess.py”, line 271, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘docker pull brewblox/firmware-flasher:rpi-edge’ returned non-zero exit status 1

From what I can find, this seems to be the same issue that popped up earlier. https://github.com/docker/for-linux/issues/625#issuecomment-473349910 suggests to change your Pi DNS settings (something you’ve done already, but in your router).
https://pimylifeup.com/raspberry-pi-dns-settings/ describes how to verify whether DNS is now working as intended.

The problem may also be caused by a proxy. Are you using one? If so, you could try the solution described in https://askubuntu.com/questions/1098849/docker-image-build-command-fails-with-client-timeout-exceeded-while-awaiting-h

To check whether the problem is Docker, or just this specific image, you can try running the Docker hello world image:

docker run --rm hello-world

I changed the DNS settings to use OpenDNS and all is good. Thanks for all of the help.

Michael

2 Likes

I recently updated the firmware and was restarting the services and now it seems to be in a loop with the docker info - see picture

Constantly connecting and disconnecting is a bit weird, yes.

You could try:

  • Run brewblox-ctl down
  • Run docker ps and check if all containers are offline
  • Unplug the Spark
  • Wait half a minute
  • Plug the Spark back in
  • Run brewblox-ctl up

ok that seems to have fixed it for this part - I still have more work to get done before I can ask for test / configuration assistance.

I’m still having some install issues- the temperature went really high on an IPA that I brewed on Saturday, and I tried to fix the problem with no luck through SSH at work. The issue turned out to be a blown fuse on the power side to my relays instead of a software issue, but I did a new install that I’m having a few issues with. https://termbin.com/olm2ex

That link gives me a 404. Is it missing a character?

I’ll run it again when I’m back home as I wiped out my remot3.it install when I formatted the SD card and started over. Not really sure what’s going on as the freezer appeared to be operating normally even with the issues but it was hot again this morning.

I ran log again and here’s the link- https://www.termbin.com/fzo9

If I do a new install, everything seems to go OK until I get to the bootloader flash, where I get this error message.

pi@raspberrypi:~/brewblox $ brewblox-ctl bootloader
Please press ENTER when your Spark is connected over USB
The following shell commands will be used:

     docker-compose down
     docker pull brewblox/firmware-flasher:rpi-edge
     docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge flash-bootloader

Press ENTER to continue, Ctrl+C to cancel

Running command:
docker-compose down

Removing network brewblox_default
WARNING: Network brewblox_default not found.

Running command:
docker pull brewblox/firmware-flasher:rpi-edge

rpi-edge: Pulling from brewblox/firmware-flasher
Digest: sha256:1f72340c62c50c1792396fad34f1dbbb13c3e804bce6b8ce4bf1dd66440df0d5
Status: Image is up to date for brewblox/firmware-flasher:rpi-edge
docker.io/brewblox/firmware-flasher:rpi-edge

Running command:
docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge flash-bootloader

Triggering listening mode
Flashing P1 bootloader…
! PROTIP: Hold the SETUP button on your device until it blinks blue!
? Press ENTER when your device is blinking BLUE

Error writing firmware: Timed out waiting for initial response from device
Traceback (most recent call last):
File “/usr/local/bin/brewblox-ctl”, line 11, in
sys.exit(main())
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/main.py”, line 81, in main
cli(standalone_mode=False)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 764, in call
return self.main(*args, **kwargs)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 717, in main
rv = self.invoke(ctx)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 555, in invoke
return callback(*args, **kwargs)
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/commands.py”, line 175, in bootloader
utils.run_all(shell_commands)
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/utils.py”, line 130, in run_all
return [run(cmd) for cmd in shell_cmds]
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/utils.py”, line 130, in
return [run(cmd) for cmd in shell_cmds]
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/utils.py”, line 124, in run
return check_call(shell_cmd, shell=True, stderr=STDOUT)
File “/usr/lib/python3.5/subprocess.py”, line 271, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge flash-bootloader’ returned non-zero exit status 1

Is you brewpi now unresponsive?

It’s a brick with a pretty display at this point. It’s unresponsive in the web interface and gives a lot of error messages. I don’t have high hopes for the IPA that was fermenting as it got so hot, but luckily I have a second fermentation freezer controlled by a BrewPi Legacy Remix setup that is totally reliable and moved it over to that.

That’s really not good. I’m afraid you’ll have to mail us your Spark so we can reset it.

Meanwhile, I did figure out the issue with your first link, so was able to read that (two characters too many).

The log is showing multiple reboots due to the reset pin. Was that triggered by you?

During the bootloader flash, did you press any buttons on the Spark itself?

I’ll go and try to reproduce the error with one of our Sparks. If both you and uk_brewer have the same problem, then it’s much less likely to be a hardware issue. I’ll go test one of the Sparks in the office, to try and reproduce the problem.

He said it is a brick with a pretty display, so please clarify whether it is bricked. If it is showing something on the screen it is clearly working.

No, I didn’t press any buttons during the bootloader flash. I was using SSH from my desktop computer and the Spark is two rooms away from that one. The display is still working but I can’t get the Spark to do anything from the web interface as I try to set up a fermentation freezer from the wizard and it gets to the part just before it sets it up and stalls, then I get error messages. If I try to reinstall BrewBlox, I get to the bootloader flash step and that fails to flash every time.

It’s something we’ll look at, but if you’re reinstalling BrewBlox, you don’t need to flash the bootloader.

If you run lsusb, what does it show?

I actually recommend setting up WiFi and skipping usb. If the spark had WiFi it can update the bootloader from the cloud itself.