<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Exchange Server"> <style></style> </head> <body> <style>  </style> <div lang="FR" link="blue" vlink="#954F72"> <div class="x_WordSection1"> No It failed : ulimit -S -c dbus-daemon -bash: ulimit: dbus-daemon: invalid number Provenance : <a href="https://go.microsoft.com/fwlink/?LinkId=550986"> Courrier</a> pour Windows 10 </div> <hr tabindex="-1" style="display:inline-block; width:98%"> <div id="x_divRplyFwdMsg" dir="ltr">De : Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Envoyé : Wednesday, May 22, 2019 3:17:32 PM À : Dorian ROSSE; Lennart Poettering Cc : systemd-devel@lists.freedesktop.org Objet : RE: Antw: Re: [systemd-devel] dbus-daemon keep shown as zombie process why ? <div> </div> </div> </div> <div class="PlainText">Could it be that dbus dies (unexpectedly), and systemd needs dbus to work? Maybe enabling coredumps could help finding out why dbus quits. Regards, Ulrich >>> Dorian ROSSE <dorianbrice@hotmail.fr> schrieb am 22.05.2019 um 14:03 in Nachricht <AM0PR08MB49966EB7E12E3C11F3528D27DA000@AM0PR08MB4996.eurprd08.prod.outlook.com> > I have agains dbus‑daemon shown as zombie as Following : > > ps aux |grep "defunct" > root 13349 0.0 0.0 0 0 ? Zs 12:00 0:00 > [dbus‑daemon] <defunct> > > Regards. > > > Dorian ROSSE. > > Provenance : Courrier<<a href="https://go.microsoft.com/fwlink/?LinkId=550986">https://go.microsoft.com/fwlink/?LinkId=550986</a>> pour > Windows 10 > > ________________________________ > De : Dorian ROSSE > Envoyé : Wednesday, May 22, 2019 12:58:15 PM > À : Ulrich Windl; Lennart Poettering > Cc : systemd‑devel@lists.freedesktop.org > Objet : RE: Antw: Re: [systemd‑devel] dbus‑daemon keep shown as zombie process > why ? > > > 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<<a href="https://go.microsoft.com/fwlink/?LinkId=550986">https://go.microsoft.com/fwlink/?LinkId=550986</a>> pour > Windows 10 > > > > ________________________________ > De : Ulrich Windl <Ulrich.Windl@rz.uni‑regensburg.de> > Envoyé : Wednesday, May 22, 2019 11:01:37 AM > À : Dorian ROSSE; Lennart Poettering > Cc : systemd‑devel@lists.freedesktop.org > Objet : Antw: Re: [systemd‑devel] dbus‑daemon keep shown as zombie process why > ? > >>>> Lennart Poettering <lennart@poettering.net> schrieb am 22.05.2019 um 10:32 > in > Nachricht <20190522083211.GB30001@gardel‑login>: >> On Di, 21.05.19 17:41, Dorian ROSSE (dorianbrice@hotmail.fr) 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@lists.freedesktop.org >> <a href="https://lists.freedesktop.org/mailman/listinfo/systemd‑devel">https://lists.freedesktop.org/mailman/listinfo/systemd‑devel</a> </div> </body> </html>