Upgraded to 6.4.0 from 6.3.10 and having problems booting

votdev · 31. Mai 2023

Zitat von chente

It is possible that I am not looking at it correctly..., but systemd-resolved I think it is not here but it is in bullseye-backports, although only in the suggests category https://packages.debian.org/bullseye-backports/systemd

Oh yes, seems Debian has outsourced the binary into a separate package. This is maybe a problem that can not be solved by openmediavault because backports are not supported because of reasons like that. Thus it is not possible to add a package to the dependency list which does not exist in stable. Backports differ from stable and introduce new and unexpected things.

votdev · 31. Mai 2023

But libnss-resolve is added to the openmediavault dependency list. In backports, systemd-resolved is a dependency of libnss-resolve as well, so if someone has activated (irrelgulary) backports, the package is installed automatically when libnss-resolve is installed.

chente · 31. Mai 2023

Zitat von votdev

Oh yes, seems Debian has outsourced the binary into a separate package. This is maybe a problem that can not be solved by openmediavault because backports are not supported because of reasons like that. Thus it is not possible to add a package to the dependency list which does not exist in stable. Backports differ from stable and introduce new and unexpected things.

So, if a similar case occurs again in the forum, should I recommend activating backports to solve it? Regardless of the fact that once resolved it can be deactivated again.

donh · 31. Mai 2023

I had no problem with the update. I have modified it to work with active directory so not stock. Here is what I have installed for nss.

dpkg -l |grep nss

ii libnss-mdns:amd64 0.14.1-2 amd64 NSS module for Multicast DNS name resolution

ii libnss-myhostname:amd64 247.3-7+deb11u2 amd64 nss module providing fallback resolution for the current hostname

ii libnss-resolve:amd64 247.3-7+deb11u2 amd64 nss module to resolve names via systemd-resolved

ii libnss-sss:amd64 2.4.1-2 amd64 Nss library for the System Security Services Daemon

ii libnss-systemd:amd64 247.3-7+deb11u2 amd64 nss module providing dynamic user and group name resolution

ii libnss-winbind:amd64 2:4.13.13+dfsg-1~deb11u5 amd64 Samba nameservice integration plugins

ii libsss-nss-idmap0 2.4.1-2 amd64 SID based lookups library for SSSD

Don't remember if backports is used or not.

FYI

pplucky · 4. Juni 2023

Zitat von notdisclosed

I have tried solving the issue by following your steps. For me this did not work. Systemd-networkd still crashes.

Looking at the comments at https://github.com/systemd/systemd/issues/27854:
I noticed that the oldest related bugreport is from 2021, so the issue has been there already for a long time. Why does this issue only surface just now? Is it the latest Debian that got updated recently?
In later versions of systemd, not yet in stable debian, the issue seems resolved.
Based on the steps of chente combined with the bugreport from votdev I was able to find a workaround for the issue:
Enable backports using omv-extras
run apt update to be sure
run apt install -t bullseye-backports systemd and when prompted keep the current non existent version of /etc/systemd/logind.conf.distrib
apply the configuration changes using the webinterface
Disable backports using omv-extras (to be sure no other backports are installed down the line)
This works for me.

I can confirm that the above steps have also worked for me. notdisclosed Thanks for your sharing.

notdisclosed · 5. Juni 2023

pplucky and others following my workaround. Please have a look at the following blog item: https://www.openmediavault.org/?p=3492 . This item mentions that the issue is revolving around systemd in combination with DHCP.

I had my system configured with DHCP for the IP address, forcing an IP using my router. As I had made snapshots of the system I could roll back and try the mentioned option of setting a fixed IP address. This also solved my problem without updating to a backport version.

Too bad that that solution did not get mentioned in this thread.

chente · 5. Juni 2023

Zitat von notdisclosed

I had my system configured with DHCP for the IP address, forcing an IP using my router. As I had made snapshots of the system I could roll back and try the mentioned option of setting a fixed IP address. This also solved my problem without updating to a backport version.

I always use fixed IP. So I guess in my case what worked was the small modification I made to one of the DNS to force the reconfiguration in the GUI.

pplucky · 7. Juni 2023

Zitat von notdisclosed

pplucky and others following my workaround. Please have a look at the following blog item: https://www.openmediavault.org/?p=3492 . This item mentions that the issue is revolving around systemd in combination with DHCP.

I had my system configured with DHCP for the IP address, forcing an IP using my router. As I had made snapshots of the system I could roll back and try the mentioned option of setting a fixed IP address. This also solved my problem without updating to a backport version.

Too bad that that solution did not get mentioned in this thread.

Thanks for getting back on this. I also had DHCP on OMV and fixed IP on router, but I also did that to avoid possible future issues.

Upgraded to 6.4.0 from 6.3.10 and having problems booting

Jetzt mitmachen!

Tags