I have 2 fleets configured in the balena cloud. These 2 fleets are in different places.
For Fleet MedF, balena cloud can receive the heartbeat and for fleet Demo, balena cloud
cannot receive the heartbeat.
Focusing on the comparison between the fleet DEMO (Heartbeat Problem) and
fleet MEDF (Heartbeat OK) fleets with the same supervisor and balenaOS versions:
SUPERVISOR VERSION
16.4.1
HOST OS VERSION
balenaOS 5.3.21
I performed the following tests on each Fleet:
root@607d2d8:~# nslookup api.balena-cloud.com
root@607d2d8:~# ping 2606:4700::6812:c66
root@607d2d8:~# curl -v https://api.balena-cloud.com/ping
root@607d2d8:~# systemctl status balena-supervisor
root@607d2d8:~# journalctl -u balena-supervisor
root@607d2d8:~# ip route
root@607d2d8:~# ip link show
root@607d2d8:~# dmesg | grep -i error
Of these tests, the only one that showed different results was the following:
Fleet MEDF (Heartbeat OK):
root@1c8b29b:~# ping 2606:4700::6812:c66
PING 2606:4700::6812:c66 (2606:4700::6812:c66): 56 data bytes
64 bytes from 2606:4700::6812:c66: seq=0 ttl=60 time=3.395 ms
64 bytes from 2606:4700::6812:c66: seq=1 ttl=60 time=2.371 ms
64 bytes from 2606:4700::6812:c66: seq=2 ttl=60 time=1.669 ms
…
Fleet DEMO (Heartbet not received : Balena Cloud)
root@607d2d8:~# ping 2606:4700::6812:c66
PING 2606:4700::6812:c66 (2606:4700::6812:c66): 56 data bytes
^C
— 2606:4700::6812:c66 ping statistics —
491 packets transmitted, 0 packets received, 100% packet loss
root@607d2d8:~#
Is it possible to say that the fact of not being able to perform this
ping explains the fact that balena clouud is not able to receive the heartbeat
to fleet Demo?