Hello,
Do you understand what is going on with this extract of journalctl:
+++++++++++++++++++++++++++++++++++++++++++++ Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9960] manager: NetworkManager state is now CONNECTED_LOCAL Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9990] manager: NetworkManager state is now CONNECTED_SITE Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9991] policy: set 'eno1' (eno1) as default for IPv4 routing and DNS Feb 25 18:26:27 homere NetworkManager[1273]: <info> [1551115587.0027] device (eno1): Activation: successful, device activated. Feb 25 18:26:27 homere NetworkManager[1273]: <info> [1551115587.0032] manager: startup complete Feb 25 18:26:27 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Feb 25 18:26:36 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Feb 25 18:26:56 homere NetworkManager[1273]: <info> [1551115616.9518] connectivity: (eno1) timed out ++++++++++++++++++++++++++++++++++++++++ We have: CONNECTED_LOCAL CONNECTED_SITE then with move in timeout because of a SERVICE_STOP !!!! Why ? +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Feb 25 18:26:56 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0") Feb 25 18:26:56 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Feb 25 18:27:06 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Feb 25 18:31:52 homere NetworkManager[1273]: <info> [1551115912.9518] connectivity: (eno1) timed out ++++++++++++++++++++++++++++ again timeout because SERVICE_STOP? then suddenly, 5 mn later! +++++++++++++++++++++++++++++++++++++++++ Feb 25 18:36:23 homere NetworkManager[1273]: <info> [1551116183.3831] manager: NetworkManager state is now CONNECTED_GLOBAL Feb 25 18:36:23 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0") Feb 25 18:36:23 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' +++++++++++++++++++++++++++++++++++++++++++++ providing CONNECTED_GLOBAL
We should have:
Feb 26 19:03:34 Teucidide NetworkManager[1362]: <info> [1551204214.4744] manager: NetworkManager state is now CONNECTED_LOCAL Feb 26 19:03:34 Teucidide NetworkManager[1362]: <info> [1551204214.4768] manager: NetworkManager state is now CONNECTED_SITE Feb 26 19:03:34 Teucidide NetworkManager[1362]: <info> [1551204214.4769] policy: set 'enp2s0' (enp2s0) as default for IPv4 routing and DNS Feb 26 19:03:34 Teucidide NetworkManager[1362]: <info> [1551204214.4797] device (enp2s0): Activation: successful, device activated. Feb 26 19:03:34 Teucidide NetworkManager[1362]: <info> [1551204214.4801] manager: startup complete Feb 26 19:03:34 Teucidide audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Feb 26 19:03:34 Teucidide NetworkManager[1362]: <info> [1551204214.7522] manager: NetworkManager state is now CONNECTED_GLOBAL
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 ===========================================================================
On 2/26/19 11:39 AM, Patrick Dupre wrote:
Do you understand what is going on with this extract of journalctl:
Feb 25 18:26:36 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Feb 25 18:26:56 homere NetworkManager[1273]: <info> [1551115616.9518] connectivity: (eno1) timed out ++++++++++++++++++++++++++++++++++++++++ We have: CONNECTED_LOCAL CONNECTED_SITE then with move in timeout because of a SERVICE_STOP !!!!
I think those are related, but not in the way you think. There's a check for being able to connect to the internet and that's probably being called by the dispatched. The "connectivity" check times out and quits, so the dispatcher that ran it is finished and stops.
I suspect you are grepping the log for "NetworkManager", so you're missing the log messages from the dispatcher. Those would probably be useful.
then suddenly, 5 mn later! +++++++++++++++++++++++++++++++++++++++++ Feb 25 18:36:23 homere NetworkManager[1273]: <info> [1551116183.3831] manager: NetworkManager state is now CONNECTED_GLOBAL Feb 25 18:36:23 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0") Feb 25 18:36:23 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' +++++++++++++++++++++++++++++++++++++++++++++ providing CONNECTED_GLOBAL
At this point, the connectivity script succeeds, so the connection is flagged as GLOBAL.
During this time, can you connect outside or is it really blocked somehow? If it's blocked, it's unlikely to be a NetworkManager problem because there are no connection changes in the logs.