On Thu, 2019-05-30 at 12:23 +0200, Thomas Haller via networkmanager- list wrote: > On Wed, 2019-05-29 at 12:23 -0400, Brian J. Murrell wrote: > > On Wed, 2019-05-29 at 09:28 +0200, Thomas Haller via > > networkmanager- > > list wrote: > > > If this is happening, when you kill NetworkManager with SIGKILL, > > > it > > > would not give NetworkManager to cleanup... > > > > > > sudo killall -SIGKILL NetworkManager > > > > > > (and veryify that NetworkManager is indeed not running. Maybe > > > first > > > `systemctl mask NetworkManager`, so that systemd won't restart > > > it). > > > > Are you suggesting that I kill NM with SIGKILL as a debugging step > > to > > see if the RSes still stop when stopping NM? > > Yes. > > > If so, that was an interesting experiment: > > > > # killall -SIGKILL NetworkManager > > # ps -ef | grep Network > > root 15001 1 0 12:02 ? 00:00:00 > > /usr/sbin/NetworkManager --no-daemon > > > > So clearly systemd restarted it, but it's not flooding RSes after > > the > > restart. > > Ah ok. That's what I meant with first masking NetworkManager.
# systemctl mask NetworkManager Created symlink from /etc/systemd/system/NetworkManager.service to /dev/null. # killall -SIGKILL NetworkManager # systemctl status NetworkManager ● NetworkManager.service Loaded: masked (/dev/null; bad) Active: failed (Result: signal) since Sat 2019-06-01 06:53:23 EDT; 39s ago Main PID: 4286 (code=killed, signal=KILL) May 31 22:04:18 server.example.com NetworkManager[4286]: <info> [1559354658.5223] manager: NetworkManager state is now CONNECTED_SITE May 31 22:04:18 server.example.com NetworkManager[4286]: <info> [1559354658.5274] policy: set 'enp2s0' (enp2s0) as default for IPv6 routing and DNS May 31 22:04:18 server.example.com NetworkManager[4286]: <info> [1559354658.5670] device (enp2s0): Activation: successful, device activated. May 31 22:04:18 server.example.com NetworkManager[4286]: <info> [1559354658.5807] manager: NetworkManager state is now CONNECTED_GLOBAL May 31 22:04:18 server.example.com NetworkManager[4286]: <info> [1559354658.5934] manager: startup complete May 31 22:04:33 server.example.com NetworkManager[4286]: <info> [1559354673.1941] policy: set 'enp2s0' (enp2s0) as default for IPv4 routing and DNS Jun 01 06:53:09 server.example.com systemd[1]: Current command vanished from the unit file, execution of the command list won't be resumed. Jun 01 06:53:23 server.example.com systemd[1]: NetworkManager.service: main process exited, code=killed, status=9/KILL Jun 01 06:53:23 server.example.com systemd[1]: Unit NetworkManager.service entered failed state. Jun 01 06:53:23 server.example.com systemd[1]: NetworkManager.service failed. Before killing NM, it was flooding out RSes and after killing it it stopped. > If you kill NetworkManager with SIGKILL (without letting > NetworkManager > restart), it would not give NetworkManager time to do anything. > If that stops the flodding, then the messages were sent by > NetworkManager -- otherwise not. Indeed. > Thanks. It would be most interesting to see them at the moment when > the > flodding happen.s Damn. I should have gathered these before killing NM because now that I have and have restarted it, it's not flooding again. I will update here the sysctl content when I see it flooding again. Cheers, b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
