Cannot Download Image HTTP 500 Error server misbehaving

I am trying to download the image to my Intel NUC. Production Image. This never happend before. But 2 days now:
Download progress going to 10%, sometimes 20%, 30% then falls back to 0%. Trying to get the image the last 24h not working for me. Tried this 100x!

27.11.18 12:24:48 (+0100) Failed to download image '' due to '(HTTP code 500) server error - Get dial tcp: lookup on server misbehaving '

Anyone know why?

Hi there @rquant!

That error message appears to come from a process that is caching DNS results, rather than the balenaCloud server. Port 53 is used for DNS and that address ( refers to localhost, where dnsmasq is listening.

Are you able to run systemctl status -l dnsmasq.service from the hostOS on that device?

Thank you!

root@0eb7d20:~# systemctl status -l dnsmasq.service
● dnsmasq.service - DNS forwarder and DHCP server
   Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/dnsmasq.service.d
   Active: active (running) since Wed 2018-11-28 08:08:49 UTC; 1min 20s ago
  Process: 666 ExecStartPre=/usr/bin/dnsmasq --test (code=exited, status=0/SUCCESS)
 Main PID: 671 (dnsmasq)
    Tasks: 1 (limit: 4527)
   CGroup: /system.slice/dnsmasq.service
           └─671 /usr/bin/dnsmasq -x /run/ -a, -7 /etc>

Nov 28 08:08:49 0eb7d20 dnsmasq[666]: dnsmasq: syntax check OK.

28.11.18 09:08:55 (+0100) Downloading image ''
28.11.18 09:25:15 (+0100) Downloading image '

ping -c 120
--- ping statistics ---
120 packets transmitted, 120 packets received, 0% packetloss
round-trip min/avg/max = 24.332/48.373/103.859 ms

Trying this morning again. Gets to like about 37% then falls back to 0%. Infinite Loop

balenaOS 2.26.0+rev1, 8.0.0 Supervisor, Intel NUC

Thanks for the additional information @rquant! We would like to take a closer look at the device as this issue is not something we have seen before. I am sending you an email to get the device information, please let us know if you do not receive it (be sure to check in spam, just in case).


Your device container is now running fine after we applied a supervisor update.


Thanks! I have seen updated to a new version 8.3.5. If I add a device with the newest image, will it also have the newest supervisor or 8.0.0?


The latest image at the moment v2.26.0 will still have the old supervisor.

But we are preparing a new OS release: v2.27.0 that contains supervisor v8.3.5.

The commits are there but we need to run the tests before releasing.

So in short time v2.27.0 will be released.


I’m now having this exact issue, Any idea on how to fix?

Hi there! What’s your BalenaOS and Supervisor version? I sent you an email to get the device information for some further inspection, please let us know if you do not receive it (be sure to check in spam, just in case).