On Fr, 30.04.21 02:00, Pengpeng Sun (pengpe...@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%2Flinux
> > > > 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.
> > >
> > > M
On Do, 29.04.21 16:55, Pengpeng Sun (pengpe...@vmware.com) wrote:
> > > 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 ou
> > 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 "
On So, 25.04.21 07:09, Pengpeng Sun (pengpe...@vmware.com) wrote:
> 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 eventuall
It seems the attachment is bigger than 500KB, so it has been cancelled.
So I copied the logs from 2021-04-25T04:58:50 to 2021-04-25T04:58:51 to a
smaller attachment again.
--
Best regards,
Pengpeng
On 2021/4/25, 3:12 PM, "Pengpeng Sun" wrote:
Forgot to mention: Here I called '/sbin/teli
Forgot to mention: Here I called '/sbin/telinit 6' to reboot, '/sbin/telinit'
is a softlink to '/bin/systemctl' in RHEL8.0. And the issue also reproduced if
I call '/bin/systemctl reboot' directly.
--
Best regards,
Pengpeng
On 2021/4/25, 3:09 PM, "Pengpeng Sun" wrote:
Hi Lennart,
On Fr, 23.04.21 14:15, Pengpeng Sun (pengpe...@vmware.com) wrote:
> Hi Lennart,
>
> The issue reproduced at 2021-04-22T15:45:30.230Z, I ran 'sudo journalctl
> -b', the log began at Apr 22 15:45:48 which is later than the issue
> reproduced.
> How can I get more early and detailed systemd log?
Hi Lennart,
The issue reproduced at 2021-04-22T15:45:30.230Z, I ran 'sudo journalctl -b',
the log began at Apr 22 15:45:48 which is later than the issue reproduced.
How can I get more early and detailed systemd log?
--
Best regards,
Pengpeng
On 2021/4/23, 4:01 PM, "Lennart Poettering" wrote
On Di, 20.04.21 16:48, Pengpeng Sun (pengpe...@vmware.com) wrote:
> Thanks Lennart!
> I reproduced the issue after set "systemd-analyze log-level debug". It turns
> out 'systemctl reboot' triggered before all the steps logged in 'journalctl
> -a'. But I did get the stderr of 'systemctl reboot',
Hi Lennart,
After installed a signal handler for SIGTERM and reproduced the issue, got
si_pid is 1 which is systemd.
Also paste the stderr here:
stderr: 'Bus n/a: changing state UNSET → OPENING
Bus n/a: changing state OPENING → AUTHENTICATING
Executing dbus call org.freedesktop.systemd1.Manager
Thanks Lennart!
I reproduced the issue after set "systemd-analyze log-level debug". It turns
out 'systemctl reboot' triggered before all the steps logged in 'journalctl
-a'. But I did get the stderr of 'systemctl reboot', paste it as below, please
check if it helps to locate the root cause.
And
On Mo, 19.04.21 14:29, Pengpeng Sun (pengpe...@vmware.com) wrote:
> Hi there,
>
> Our program executes 'systemctl reboot' in a child process to reboot
> Linux right after its booted, Sometimes there is no error, but
> sometimes the child process terminated due to received uncaught
> signal 15, the
13 matches
Mail list logo
