[systemd-devel] systemctl reboot get terminated by signal 15

[Lennart Poettering]

On Fr, 30.04.21 02:00, Pengpeng Sun (pengpengs at vmware.com) wrote:

> > > Here is where our code calls “/sbin/telinit 6” to reboot Linux.
> > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvmware%2Fopen-vm-tools%2Fblob%2Fmaster%2Fopen-vm-tools%2FlibDeployPkg%2FlinuxDeployment.c%23L1466&data=04%7C01%7Cpengpengs%40vmware.com%7C703b24bd11584d4d033d08d90b4a1ad9%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637553235200829094%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DWWAKyPLV6dqnbJ37%2FFVqpAYapYvVC57reiYTSflFH4%3D&reserved=0
> > > 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?

Check the logs?

https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1

Lennart

--
Lennart Poettering, Berlin