Re: Antw: [EXT] Re: Odd status after core dump

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Mo, 03.08.20 08:32, Ulrich Windl (Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx) wrote:

> OK, some additional notes (maybe these issues are fixed in a newer version
> already):
> Looking in my /var/log/messages, I see higher resolution of time stamps, and
> specifically I see the original core-dump message:

Use "journalctl -o short-precise" to get µs granularity.

> 2020-07-31T11:31:57.404198+02:00 v04 systemd[1]: iotwatch@NFS1.service: Main
> process exited, code=dumped, status=6/ABRT
> 2020-07-31T11:31:57.421639+02:00 v04 systemd[1]: Stopped iotwatch I/O
> performance monitor instance "NFS1".
>
> (Using "journalctl I see lower-resolution timestamps as output)
> Jul 31 11:31:57 v04 systemd[1]: iotwatch@NFS1.service: Main process exited,
> code=dumped, status=6/ABRT
> Jul 31 11:31:57 v04 systemd[1]: Stopped iotwatch I/O performance monitor
> instance "NFS1".
> Jul 31 11:31:57 v04 systemd[1]: iotwatch@NFS1.service: Unit entered failed
> state.
> Jul 31 11:31:57 v04 systemd[1]: iotwatch@NFS1.service: Failed with result
> 'core-dump'.
>
> So why is the "core dump complete" included in the status of "starting" the
> service when the core dump happened when stopping the service, and why isn't
> the original core dump message included as well?

I cannot parse this, and I cannot tell you how you configured your
syslog and why it shows less data.

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel