[Pkg-utopia-maintainers] Bug#992048: Bug#992048: NetworkManager-wait-online.service: fails to start correctly

Michael Biebl biebl at debian.org
Tue Aug 10 00:05:40 BST 2021


Control: severity -1 normal

Am 10.08.21 um 00:18 schrieb Brian May:
> $ /usr/bin/nm-online -s
> Connecting...............    0s [startup-pending]
> $ echo $?
> 1

Have you read the nm-online man page regarding "-s"?


>        -s | --wait-for-startup
>            Wait for NetworkManager startup to complete, rather than waiting for network connectivity specifically. Startup is
>            considered complete once NetworkManager has activated (or attempted to activate) every auto-activate connection which
>            is available given the current network state. This corresponds to the moment when NetworkManager logs "startup
>            complete". This mode is generally only useful at boot time. After startup has completed, nm-online -s will just return
>            immediately, regardless of the current network state.
> 
>            There are various ways to affect when startup complete is reached. For example, by setting a connection profile to
>            autoconnect, such a profile possibly will activate during startup and thus delay startup complete being reached. Also,
>            a profile is considered ready when it fully reached the logical connected state in NetworkManager. That means,
>            properties like ipv4.may-fail and ipv6.may-fail affect whether a certain address family is required. Also, the
>            connection property connection.wait-device-timeout affects whether to wait for the driver to detect a certain device.
>            Generally, a failure of NetworkManager-wait-online.service indicates a configuration error, where NetworkManager won't
>            be able to reach the desired connectivity state during startup. An example for that are bridge or bond master
>            profiles, that get autoconnected but without activating any slaves. Such master devices hang in activating state
>            indefinitely, and cause NetworkManager-wait-online.service to fail.

Has your NetworkManager log a "startup complete" message?
What kind of network connections have you marked as autoconnect?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-utopia-maintainers/attachments/20210810/9cf42ec9/attachment.sig>


More information about the Pkg-utopia-maintainers mailing list