Thank you very much, it works well now.
Regards,
Kristoffer
--
Wysłane za pomocą Tutanota, bezpiecznej i wolnej od reklam skrzynki pocztowej.
i got the +b1 version of systemd this afternoon and its fixed
On Wed, Feb 2, 2022 at 10:15 AM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hello!
>
> On 2/2/22 18:55, H wrote:
> > Thank you Adrian!
>
> Try upgrading your machines, it should be fixed now.
>
> Adrian
>
> --
>
Hello!
On 2/2/22 18:55, H wrote:
> Thank you Adrian!
Try upgrading your machines, it should be fixed now.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956
Thank you Adrian!
On Wed, Feb 2, 2022 at 1:00 AM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hello!
>
> On 2/2/22 00:11, H wrote:
> > FWIW, A little bit information that might be helpful:
> >
> > I started journald manually via /lib/systemd/systemd-journald, no error
> mess
Hello!
On 2/2/22 00:11, H wrote:
> FWIW, A little bit information that might be helpful:
>
> I started journald manually via /lib/systemd/systemd-journald, no error
> message
> to stdout and stderr, nor journalctl output. Actually journalctl still does
> not
> work (empty for all services).
>
>
Hello!
On 2/1/22 23:59, Cameron MacPherson wrote:
> on my system i get
> systemd[1]: Caught , core dump failed (child 210, code=killed,
> status=6/ABRT)
>
> prior to rebooting there were messages about journald not starting. i will
> see if
> i can go back to an older version of systemd.
That
Thanks!
Switching apt source to
http://snapshot.debian.org/archive/debian-ports/20220119T020551Z/ saved me.
On Tue, Feb 1, 2022 at 4:15 PM Cameron MacPherson <
cameron.macpher...@gmail.com> wrote:
> i got the ppc64 version 250.3-1 of libnss-systemd libpam-systemd
> libsystemd0 systemd-timesync an
i got the ppc64 version 250.3-1 of libnss-systemd libpam-systemd
libsystemd0 systemd-timesync and systemd from snapshot.debian.org and
installed them with dpkg -i and the system boots again
after apt upgrade to 250.3-2 on reboot the machine halts before it restarts
systemd[1]: Caught , dumped core
Hi John,
FWIW, A little bit information that might be helpful:
I started journald manually via /lib/systemd/systemd-journald, no error
message to stdout and stderr, nor journalctl output. Actually journalctl
still does not work (empty for all services).
But the journald seemed started logging to
hi,
on my system i get
systemd[1]: Caught , core dump failed (child 210, code=killed,
status=6/ABRT)
prior to rebooting there were messages about journald not starting. i will
see if i can go back to an older version of systemd.
On Tue, Feb 1, 2022 at 2:33 PM John Paul Adrian Glaubitz <
glaub..
On 2/1/22 23:11, H wrote:
> Namely, systemd-journald and systemd-logind and some other less important
> stuff. And, due to the fact that systemd-journald is unable to start,
> journalctl -xn $service is empty for any services.
It's a bit difficult to say what's wrong without any error messages. Th
Namely, systemd-journald and systemd-logind and some other less important
stuff.
And, due to the fact that systemd-journald is unable to start, journalctl
-xn $service is empty for any services.
On Tue, Feb 1, 2022 at 2:09 PM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hell
Hello!
On 2/1/22 22:47, H wrote:
> If you apt update && apt upgrade, or worse, try to install debian with a
> NETINST
> image, by default you will be left in a broken system, complaining about some
> systemd service being unable to start. To make it worse, systemd-journald is
> one
> of the comp
13 matches
Mail list logo
