|
> > > > Hi Lennart, > > > > > > > > After modify journald.conf, got systemd log when the issue > > > > reproduced. Please find it in attachment. > > > > > > Looking at the logs there seems to be a lot missing, in particular all > > > the debug output of PID 1 is eventually going away. > > > > > > My educated guess: you are runnning "systemctl reboot" from user > > > context? i.e. some script you run as part of your user sesion? If so, > > > when the system goes down your user session of course will be > > > terminated. Thus it's a race: either your session (and its associated > > > services) are terminated via SIGTERM first, including the systemctl > > > command you issued, or the systemctl is quicker and exits before it > > > gets killed. > > > > > > > Here is where our code calls “/sbin/telinit 6” to reboot Linux. > > https://nam04.safelinks.protection.outlook.com/?url=""> > > This code is executed when systemd vmtoolsd.service starts, attached the > > vmtoolsd.service file. > > Not seeing this issue before /sbin/telinit becomes a softlink to > > systemctl. > > vmtoolsd.service is probably asked to shutdown because of the system > shutdown, and the forked off /sbin/telinit is part of that service, so > it gets terminated too? Yes, this could be the reason. The issue is system does NOT always reboot after “uncaught signal 15” happens, while sometimes it does reboot during my local testing. Is there a way/command to make sure system get rebooted? |
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
