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 components that is broken so it is a struggle to get any logs at all.
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.
Hello!
On 2/1/22 22:47, H wrote:
If you apt update && apt upgrade, or worse, try to install debian with aNETINST
image, by default you will be left in a broken system, complaining aboutsome
systemd service being unable to start. To make it worse,systemd-journald is one
of the components that is broken so it is a struggle to get any logs atall.
Which service is it that is failing? Normally you will be dropped to an emergency
shell where you can type:
# journalctl -xn $service
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
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. The cause
might be unrelated to systemd and it's just the part of the system where
the
problem shows.
Maybe problems with the filesystem or hardware?
I have not observed any systemd issues on my PowerPC machines yet, but I
will
run a test installation tomorrow.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
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. The cause
might be unrelated to systemd and it's just the part of the system where
the
problem shows.
Maybe problems with the filesystem or hardware?
I have not observed any systemd issues on my PowerPC machines yet, but I
will
run a test installation tomorrow.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
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 /var/log/syslog.
When I try to start logind, /var/log/syslog captures the following error message:
/lib/systemd/systemd-logind: error while loading shared libraries: libsystemd-shared-250.so: failed to map segment from shared object.
The file exists, clearly this is a broken binary from the port.
The filesystem is ext4.
Thanks,
Hao
On Tue, Feb 1, 2022 at 2:17 PM John Paul Adrian Glaubitz < glaubitz@physik.fu-berlin.de> wrote:
On 2/1/22 23:11, H wrote:
Namely, systemd-journald and systemd-logind and some other lessimportant
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. The
cause
might be unrelated to systemd and it's just the part of the system where
the
problem shows.
Maybe problems with the filesystem or hardware?
I have not observed any systemd issues on my PowerPC machines yet, but I
will
run a test installation tomorrow.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
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).</div><div>But the journald seemed started logging to /var/log/syslog.<br></div><div>When I try to start logind, /var/log/syslog captures the following error message:</div><div>/lib/systemd/systemd-logind: error while loading shared libraries: libsystemd-shared-250.so: failed to map segment from shared object.</
<div><br></div><div>The file exists, clearly this is a broken binary from the port.<br></div><div></div><div>The filesystem is ext4.</div><div><br></div><div>Thanks,</div><div>Hao<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 1, 2022 at 2:17 PM John Paul Adrian Glaubitz <<a href="mailto:glaubitz@physik.fu-berlin.de" target="_blank" rel="noreferrer">glaubitz@physik.fu-berlin.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px
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 <ABRT>, dumped core as pid 1293.
systemd [1]: Freezing execution.
after reboot same failure except with core dump failed
On Tue, Feb 1, 2022, 3:27 PM H <snullp@gmail.com> wrote:
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 /var/log/syslog.
When I try to start logind, /var/log/syslog captures the following error
message:
/lib/systemd/systemd-logind: error while loading shared libraries:
libsystemd-shared-250.so: failed to map segment from shared object.
The file exists, clearly this is a broken binary from the port.
The filesystem is ext4.
Thanks,
Hao
On Tue, Feb 1, 2022 at 2:17 PM John Paul Adrian Glaubitz <
glaubitz@physik.fu-berlin.de> wrote:
On 2/1/22 23:11, H wrote:
Namely, systemd-journald and systemd-logind and some other lessimportant
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. The >>> cause
might be unrelated to systemd and it's just the part of the system where >>> the
problem shows.
Maybe problems with the filesystem or hardware?
I have not observed any systemd issues on my PowerPC machines yet, but I >>> will
run a test installation tomorrow.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
<div><br></div><div>Thanks,</div><div>Hao<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 1, 2022 at 2:17 PM John Paul Adrian Glaubitz <<a href="mailto:glaubitz@physik.fu-berlin.de" rel="noreferrer" target="_blank">glaubitz@physik.fu-berlin.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2/1/22 23:11, H wrote:<br>
on my system i get
systemd[1]: Caught <ABRT>, 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.
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 /var/log/syslog.
When I try to start logind, /var/log/syslog captures the following error message:
/lib/systemd/systemd-logind: error while loading shared libraries: libsystemd-shared-250.so: failed to map segment from shared object.
The file exists, clearly this is a broken binary from the port.
The filesystem is ext4.
[1] https://buildd.debian.org/status/fetch.php?pkg=systemd&arch=ppc64&ver=250.3-2&stamp=1643244459&raw=0
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004272
Thank you Adrian!
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 errormessage
to stdout and stderr, nor journalctl output. Actually journalctl stilldoes not
work (empty for all services).
But the journald seemed started logging to /var/log/syslog.message:
When I try to start logind, /var/log/syslog captures the following error
/lib/systemd/systemd-logind: error while loading shared libraries:libsystemd-shared-250.so: failed to map segment from shared object.
The file exists, clearly this is a broken binary from the port.
The filesystem is ext4.
systemd_250.3-2 was built on ppc64 with the broken binutils_2.37.50.20220121-1 [1] which
is affected by a serious bug that results in broken binaries [2].
I have triggered a rebuild of the systemd package on ppc64 so it gets
rebuild with the
fixed version of binutils. The issue should be fixed by tomorrow once the package has
been rebuilt and synced onto all mirrors.
Adrian
[1]https://buildd.debian.org/status/fetch.php?pkg=systemd&arch=ppc64&ver=250.3-2&stamp=1643244459&raw=0
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004272
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
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 - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 88:37:32 |
| Calls: | 6,658 |
| Files: | 12,203 |
| Messages: | 5,333,956 |