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 <
[email protected]> wrote:
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 <[email protected]> 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 <
[email protected]> wrote:
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 - [email protected]
`. `' Freie Universitaet Berlin - [email protected]
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
<div dir="ltr"><div>Thanks!</div><div>Switching apt source to <a href="
http://snapshot.debian.org/archive/debian-ports/20220119T020551Z/">http://snapshot.debian.org/archive/debian-ports/20220119T020551Z/</a> saved me.<br></div></div><br><div class="gmail_
quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 1, 2022 at 4:15 PM Cameron MacPherson <<a href="mailto:
[email protected]">
[email protected]</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"><div dir="auto">i got the ppc64 version 250.3-1 of libnss-systemd libpam-systemd libsystemd0 systemd-timesync and systemd from <a href="
http://snapshot.debian.org" target="_blank">snapshot.
debian.org</a> and installed them with dpkg -i and the system boots again<div dir="auto"><br></div><div dir="auto">after apt upgrade to 250.3-2 on reboot the machine halts before it restarts</div><div dir="auto">systemd[1]: Caught <ABRT>, dumped
core as pid 1293.</div><div dir="auto">systemd [1]: Freezing execution.</div><div dir="auto"><br></div><div dir="auto">after reboot same failure except with core dump failed</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue,
Feb 1, 2022, 3:27 PM H <<a href="mailto:
[email protected]" target="_blank">
[email protected]</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"><div dir="ltr">
<div>Hi John,</div><div><br></div><div>FWIW, A little bit information that might be helpful:</div><div><br></div><div>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><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><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:[email protected]" rel="noreferrer" target=
"_blank">
[email protected]</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>
> Namely, systemd-journald and systemd-logind and some other less important<br>
> stuff. And, due to the fact that systemd-journald is unable to start,<br> > journalctl -xn $service is empty for any services.<br>
It's a bit difficult to say what's wrong without any error messages. The cause<br>
might be unrelated to systemd and it's just the part of the system where the<br>
problem shows.<br>
Maybe problems with the filesystem or hardware?<br>
I have not observed any systemd issues on my PowerPC machines yet, but I will<br>
run a test installation tomorrow.<br>
Adrian<br>
-- <br>
.''`. John Paul Adrian Glaubitz<br>
: :' : Debian Developer - <a href="mailto:
[email protected]" rel="noreferrer" target="_blank">
[email protected]</a><br>
`. `' Freie Universitaet Berlin - <a href="mailto:
[email protected]" rel="noreferrer" target="_blank">
[email protected]</a><br>
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913<br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)