I launch the command line adviced strace -p 1
strace -p 1
strace: Process 1 attached
ppoll([{fd=22, events=POLLIN}], 1, {tv_sec=53, tv_nsec=119912101}, NULL, 8
Why I should search a coredump ?
What I must do now ?
Now I have my system frozen for update and upgrade :’( ,
Thank you for your time bring for me,
Thank you in advance to help me again,
Regards.
Dorian ROSSE.
Provenance : Courrier pour Windows 10
De : Ulrich Windl <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
Envoyé : Wednesday, May 22, 2019 11:01:37 AM
À : Dorian ROSSE; Lennart Poettering
Cc : systemd-devel@xxxxxxxxxxxxxxxxxxxxx
Objet : Antw: Re: dbus-daemon keep shown as zombie process why ?
Envoyé : Wednesday, May 22, 2019 11:01:37 AM
À : Dorian ROSSE; Lennart Poettering
Cc : systemd-devel@xxxxxxxxxxxxxxxxxxxxx
Objet : Antw: Re: dbus-daemon keep shown as zombie process why ?
>>> Lennart Poettering <lennart@xxxxxxxxxxxxxx> schrieb am 22.05.2019 um 10:32
in
Nachricht <20190522083211.GB30001@gardel-login>:
> On Di, 21.05.19 17:41, Dorian ROSSE (dorianbrice@xxxxxxxxxx) wrote:
>
>> Hello everybody,
>>
>>
>> I know this isn’t a bug or a systemd problems but It keeps the
>> system in thought of dbus-daemon should be a zombie process but my
>> web page about zombie process say I should kill the parent but the
>> parent is systemd lol
>>
>> If somebody know Something about this feeling of dbus-daemon zombie
>> process,
>
> That suggests your system is in a very borked state and PID 1 is frozen
> and doesn't rip zombies anymore. Look for coredumps in the logs.
An "strace -p 1" might also show what's going on. Or examine /proc/1; SIGCHLD
might be blocked or ignored.
>
> Lennart
>
> --
> Lennart Poettering, Berlin
> _______________________________________________
> systemd-devel mailing list
> systemd-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
in
Nachricht <20190522083211.GB30001@gardel-login>:
> On Di, 21.05.19 17:41, Dorian ROSSE (dorianbrice@xxxxxxxxxx) wrote:
>
>> Hello everybody,
>>
>>
>> I know this isn’t a bug or a systemd problems but It keeps the
>> system in thought of dbus-daemon should be a zombie process but my
>> web page about zombie process say I should kill the parent but the
>> parent is systemd lol
>>
>> If somebody know Something about this feeling of dbus-daemon zombie
>> process,
>
> That suggests your system is in a very borked state and PID 1 is frozen
> and doesn't rip zombies anymore. Look for coredumps in the logs.
An "strace -p 1" might also show what's going on. Or examine /proc/1; SIGCHLD
might be blocked or ignored.
>
> Lennart
>
> --
> Lennart Poettering, Berlin
> _______________________________________________
> systemd-devel mailing list
> systemd-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
