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 < glaub...@physik.fu-berlin.de> 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 - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > >
