Hi team,
I’m unable to see any logs on the Balena dashboard for the last few days - it’s just displaying “No Logs yet.” This is unusual since everything was working properly when I checked on Friday.
I’ve already verified the Balena status page (https://status.balena.io/), which indicates all systems are operational.
Has anyone else noticed this issue with the logs, or is it only affecting me?
Hi @terry-cpi , we haven’t had any other reports of this yet, so it might be something local to your device. Does this behaviour persist over reboots? Also if you start a terminal session into the hostOS and list your containers with balena ps
and then run balena logs <YOUR_CONTAINER_ID>
do you see the device writing logs?
Finally, it would also be good to look at the supervisor logs for any errors, this can be done by running journalctl -u balena-supervisor --no-pager
. It could be that for some reason the supervisor can’t connect to the logging backend because of a DNS issue or something similar.
Hey @shaunmulligan1, when I pushed a new release, I initially saw logs appearing on the dashboard. However, after a few hours, they stopped displaying. Despite this issue, I can still view logs using the command balena logs <YOUR_CONTAINER_ID>
via CLI.
root@6d0c0d0:~# journalctl -u balena-supervisor --no-pager
May 21 07:23:23 6d0c0d0 balena-supervisor[6855]: [api] GET /v1/healthy 200 - 3.303 ms
May 21 07:23:35 6d0c0d0 balena-supervisor[6855]: [info] Reported current state to the cloud
May 21 07:28:24 6d0c0d0 balena-supervisor[6855]: [api] GET /v1/healthy 200 - 3.756 ms
May 21 07:28:36 6d0c0d0 balena-supervisor[6855]: [info] Reported current state to the cloud
May 21 07:33:24 6d0c0d0 balena-supervisor[6855]: [api] GET /v1/healthy 200 - 7.517 ms
May 21 07:34:08 6d0c0d0 balena-supervisor[6855]: [info] Reported current state to the cloud
root@6d0c0d0:~#
Hi @terry-cpi, to me it seems that the issue you’re experiencing may be caused by a few different factors, such as an ad blocker or a network rule blocking streaming requests. Ad blockers like uBlock and Adblock often block streaming endpoints, especially those that include query parameters like stream=1
, which we use for real-time logs.
A few steps you could take to troubleshoot:
- try a different browser to check if a browser extension (such as an ad blocker) is interfering with the request.
- try a different network, such as mobile tethering, which typically has fewer restrictions. This can help rule out the possibility of a firewall blocking the request to
https://api.balena-cloud.com/device/v2/<DEVICE_UUID>/logs?count=100&stream=1
- If you’re using an ad blocker, please add an exception to allow all requests to
api.balena-cloud.com
to ensure the logs can stream without interference.
Let us know how it goes after trying these steps
1 Like