hi,
sorry about the wrong tag. I’m using a verdin imx8m-mini with custom carrier board.
the modules are connected to the internet with a modem, my first thought was bad connectivity , but I get this error also on devices that use the fast cat M1 network and where I can easily connect with ssh , so it doesn’t appear to be a connectivity issue.
the problem is present on 8-10% of all devices deployed on the field and I can see the error also on some devices on our test bench in the lab
on other devices I’m getting another error : net/http: request canceled (Client.Timeout exceeded while awaiting headers)
looking online it seems that both errors are related to the way the dns are resolved. I have checked my /etc/resolv.conf file and I can see two namervers:
nameserver 10.80.4.10
nameserver 10.80.5.10
I have tried to add manually the google dns servers to resolv.conf file but, as reported online, it’s not enough because that file is managed dynamically by the OS (TorizonCore in my case) through the networkManager.
hi @gclaudino.tx ,
I was just doing some tests in the morning.
our modem interface is not managed by NetworkManager nor ModemManager, because it needs to be controlled by our docker application, but I managed to add the cloudflare dns server (1.1.1.1) and google dns server (8.8.8.8) with resolvconf command. Despite I have seen the same error once, eventually I managed to update 3 out of 5 devices, I have lost communication with the other two during the process.
so even it might not be the definitive solution to the problem, adding those nameserver to the modem interface improves the situation.
do you know where these current nameserver in /etc/resolv.conf come from?
nameserver 10.80.4.10
nameserver 10.80.5.10
I can’t find them anywhere in my project, so I guess they are coming from the TorizonCore image
Thanks for the update. I don’t know exactly where these two configurations come from. We tested on a module with a fresh TorizonCore image and the file looked like this:
nameserver 1.1.1.1
nameserver 8.8.8.8
nameserver 1.0.0.1
# Too many DNS servers configured, the following entries may be ignored.
nameserver 8.8.4.4
I couldn’t find a reason for the DNS names you saw. Do you have any news on that topic? Do you have any other news from your side regarding this topic?
hi @gclaudino.tx ,
next week I will deploy on all our fleets the new firmware release including the possible fix for this issue. I will let you know if I still have problems
@RoccoBr for what it’s worth, the resolv.conf file is usually populated by the DHCP server. I wonder if those DNS addresses were populated when you generated your image and just have not been modified. Are you using torizoncore-builder to generate your image?
Regarding the fix for the TLS issues, can you share details?
Hello,
I have verified that my changes are effective against this issue.
I have update the firmware of our fleets via OTA and the error is basically gone, just few retries on a small number of device due to loss of connectivity.
my solution consists in a modification of the configuration file for docker deamon /usr/lib/docker/daemon.json with the following settings:
change to maximum number of concurrent download to 1 (basically no concurrent downloads, just 1 layer at the time
increase the number of attempt
set the DNS servers
these changes seem to guarantee a better stability even in case of poor connectivity
