On 9/10/20 11:28 AM, Lennart Poettering wrote:
On Do, 10.09.20 10:48, qmail (qmail@xxxxxxxxxxxx) wrote:can someone tell me why systemd send a signal to NetworkManager to shutdown on an init 5 issued from a level 3?Hence, if NM goes away if you swtch from 3 to 5, this means your graphical.target for some reason doesn't lst NM as dep. (That said, there could also be a Conflicts= dep towards NM on some unit to be started on graphical.target). Consider providing more than 9 lines of logs around where this happens, it should show you what's going on in particular if you issue "systemd-analyze log-level debug" first, to request debug output. Lennart -- Lennart Poettering, Berlin
So I tried
[Mail@omen-gatworks ~]$ su
Password: [root@omen-gatworks Mail]# systemd-analyze log-level debug [root@omen-gatworks Mail]# man systemd-analyze [root@omen-gatworks Mail]# [root@omen-gatworks Mail]# [root@omen-gatworks Mail]# [root@omen-gatworks Mail]# systemd-analyze log-level debug [root@omen-gatworks Mail]# ???????????there is a bunch of ***** delimiting what I THINK is the error at about line 132. there is about 3000 lines in the file. Without knowing any better - error?
Sep 10 08:38:41 omen-gatworks systemd[1]: Got message type=error sender=org.freedesktop.DBus destination=:1.1 path=n/a interface=n/a member=n/a cookie=4294967295 reply_cookie=27 signature=s error-name=org.freedesktop.DBus.Error.NameHasNoOwner error-message=The name does not have an owner
ANYWAY, does this mean anything: If so, where is the restart setting?
========> Sep 10 08:38:41 omen-gatworks systemd[1]: NetworkManager.service: Service will not restart (restart setting) <========ep 10 08:38:41 omen-gatworks systemd[1]: NetworkManager.service: Main process exited, code=exited, status=0/SUCCESS Sep 10 08:38:41 omen-gatworks systemd[1]: NetworkManager.service: Succeeded. Sep 10 08:38:41 omen-gatworks audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 10 08:38:41 omen-gatworks systemd[1]: NetworkManager.service: Changed stop-sigterm -> dead Sep 10 08:38:41 omen-gatworks systemd[1]: NetworkManager.service: Consumed 287ms CPU time.
"/etc/systemd/system/multi-user.target.wants/NetworkManager.service"
[Service] Type=dbus BusName=org.freedesktop.NetworkManager ExecReload=/usr/bin/busctl call org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager Reload u 0 #ExecReload=/bin/kill -HUP $MAINPID ExecStart=/usr/sbin/NetworkManager --no-daemon
Restart=on-failure <============= This seems to be wrong for init transitions on-success maybe better?
# NM doesn't want systemd to kill its children for it KillMode=process
I have a Fedora 32, that was upgraded from 31 automagically via DNF
Attachment:
journalctl.log.gz
Description: application/gzip
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
