Hi,
We try to reproduce this internally but the docker launch works well in our environment.
Do you have a standard XavierNX board?
Could you help to do the same on the standard board to see if this issue is related to the custom board?
Thanks.
Hey,
Unfortunately I don’t have a standard Nvidia NX board…
therefore I cannot test it on another environment, that’s why i offered you to connect with SSH to the Jetson…
I don’t care about the data inside it, I can restore the backup I just need it to work and cannot achieve the solution by my own that’s why i came to you
Hope you can help me fix the issue…
Thanks a lot!
Found the problem
This service looking to get ethernet connection in order to load “systemd-networkd-wait-online.service”, when it keeps looking for connection, it stops all the other services the depend in each other (after the “systemd-networkd-wait-online.service” starts the service “network-online.target” and after this one starts the “docker.service”
which means, if you mask or disable or doing both to the service “systemd-networkd-wait-online.service” the docker starts right after the boot with no delay.
I didnt want to disable or mask this service so I add a “TimeoutStartSec” for 15 seconds and it stops trying to search for ethernet connection and crashing, after that the docker service starts right on time
The big question is, Is it ok to mask or disable or do both to this service? you might have another solution for this?
Hi,
Let us check this internally.
But just want to confirm that will your device connect to the network afterward or it will already be offline?
Thanks.
Hi,
Could you check /usr/lib/systemd/system/systemd-networkd-wait-online.service file.
And add the TimeoutStartSec=[t] under [Service] to see if this helps.
...
[Service]
Type=oneshot
ExecStart=/lib/systemd/systemd-networkd-wait-online
RemainAfterExit=yes
TimeoutStartSec=30
...
Setting it into a short delay time so other services can be started quickly.
Thanks.
That’s what I did and it worked
I’m going to connect my device to Ethernet cable but sometimes when we test the device it just failing so I had so find the solution for this
My question about it is if I adding the timeout to the service and this service crashing when I see it’s status it’s on “failed status”
Is that ok?
I just want to make sure it’s ok.
Usually I’m not editing kernel files no I just want to make sure this change have not affect on the system and it’s ok the service failing because of the timeout added to the service.
When you answer me about this that’s going to be the solution.
Thank you!
Hi,
We don’t customize the service so its behavior should be close to the x86 Ubuntu system.
Since the systemd-networkd-wait-online.service eventually timeout, shortening the testing time should not change the behavior of the system.
Thanks.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.