Error parsing HTTP 404 response body: invalid character 'S' looking for beginning of value

Product support
1

When doing balena push -m <fleet> I get the following error:

[Success]        Successfully uploaded images
[Error]          Some services failed to build:
[Error]            Service: audio
[Error]              Error: (HTTP code 500) server error - error parsing HTTP 404 response body: invalid character 'S' looking for beginning of value: "Sorry, page not found." 
[Info]           Built on x64_01
[Error]          Not deploying release.
Remote build failed

It happens all the way at the end (even after the message Successfully uploaded images.

What is wrong suddenly ? This did not happen two days ago…

My audio service in docker-compose.yml looks like this:

volumes:
    xserver-volume:
    resin-data:
audio:
    image: <bh.cr/my-block/audio>
    privileged: true
    ports:
        - 4317:4317 # Only required if using PA over TCP socket
    labels:
        io.balena.features.dbus: "1"
        io.balena.features.kernel-modules: "1"
    volume
        - xserver-volume:/tmp/.X11-uni
    environment:
        - DBUS_SYSTEM_BUS_ADDRESS=unix:path=/host/run/dbus/system_bus_socket
        - AUDIO_OUTPUT=alsa_output.hda-intel.hdmi-stereo
        - DISPLAY=:0
xserver:
    image: balenablocks/xserver
    restart: always
    privileged: true
    labels:
        io.balena.features.dbus: "1"
    volumes:
        - xserver-volume:/tmp/.X11-unix

I’m on FROM balenalib/%%BALENA_MACHINE_NAME%%-node:16-run

My device type = Generic_x86_64 (GPT)

Any idea what to do ?

2

Hey there @skuenstler the first thing that stands out to me is the < and > around the image name on your audio service. It looks like the build can’t find the image for the audio service and is returning a 404 error, which then causes the 500 error when it’s being parsed. Could you confirm that’s the correct image URL?

3

ah I added a pseudo-name (indicating with <...> that I fill something different there.

In my real version I have the correct audio image defined.

It says something like: bh.cr/<my_name>/<my_image_reference>

I am pretty sure this must work since it did so 2 days ago.

6

@skuenstler ah gotcha! one of my colleagues saw my reply and let me know about an issue we’re currently having with bh.cr. In the meantime as a workaround you should be able to use bhcr.io instead of bh.cr and get your build working again :+1:

7

No, bhcr.io does not work. Same error

I replaced bh.cr/<my_name>/<my_image_reference> by bhcr.io/<my_name>/<my_image_reference>

8

Hey @skuenstler ,
Our team has marked the issue as resolved, if this is still affecting you please let us know.
Thank you for you time and reporting this issue to us.
-Thomas

9

Thank you - it works again.

10

Thanks for the confirmation @skuenstler

Let us know if we can help you more!