Platform: NVidia NX w/ L4T 32.4.4 w/ custom Ubuntu 18.04 server based rootfs
I was hoping to get some clarification on why NetworkManager-wait-online.service is disabled in the nv_tools/scripts/nv_customize_rootfs.sh
script (in L4T 32.4.4)? It mentions (I assume an internal) bug number 200290321.
We have an interest in using the NetworkManager-wait-online.service to gate the network-online.target on system boot.
We are also seeing weird behavior with the following kernel messages appearing several minutes after boot:
Mar 10 15:59:37 ws-nxcore kernel: random: crng init done
Mar 10 15:59:37 ws-nxcore kernel: random: 7 urandom warning(s) missed due to ratelimiting
and don’t know if it is somehow related.
The reason I am drawing the relation is because of the following behavior:
With NetworkManager-wait-online.service
enabled the pollinate
service times out after 5 minutes during system boot, blocking ssh
from starting.
- The reason this occurs is because the
pollinate
service waits fornetwork-online.target
. - With the
NetworkManager-wait-online.service
enabled, thepollinate
service starts after there is a confirmed network online because thenetwork-online.target
isn’t triggered until theNetworkManager-wait-online.service
confirms there is an online network - For some reason the
pollinate
service takes ~5 minutes to run and eventually times out (being unsuccessful), allowing thessh
service to start. (thepollinate
service puts a restriction that it must run beforessh
) - Around this time (but I believe unrelated) the above mentioned
crng init done
logs appear.
With NetworkManager-wait-online.service
disabled the pollinate
service runs when there is no online network, exits quickly (with error I believe), allowing ssh
to start quickly.
- Since the
network-online.target
is not gated by anything it finishes right away (before the network is confirmed to be online) - Therefore
pollinate
runs right away (when there is no network) and exits right away as the //entropy.ubuntu.com/ is not reachable -
ssh
is also unblocked becausepollinate
finished quickly (again, with error). - Several minutes later the above mentioned
crng init done
logs appear
Neither of the above 2 scenarios is ideal.
Is the above mentioned bug (200290321) related to the late arriving crng init done
message? Is there a way for me to resolve my issue to have NetworkManager-wait-online.service
enabled and the pollinate
service not hang?
Thanks,
Joe