Comment 1 for bug 1758342

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :

It turns out that this is a race condition that happens when the wifi-ap management service starts before NetworkManager. In that case, when wifi-ap tries to set the wifi interface as "unmanaged" in NM by using nmcli, NM is not yet there. In the moment NM starts, it takes control of the wifi interface and hostapd dies. See attached log. Interesting traces:

Mar 23 16:18:21 1234567 wifi-ap.management-service[3461]: Error: NetworkManager is not running.
Mar 23 16:18:22 1234567 NetworkManager[3455]: <info> [1521821902.6045] NetworkManager (version 1.2.2) is starting...