Bookworm -> Daedalus migration nscd network-manager failed

paculino · 2023-12-26 01:09:57

Today I started to migrate my Debian bookworm installation (using stable, updates, security, and one package from backports) to daedalus. In preparation, I fully cloned it and booted into both the original and the clone using the grub installed in my old KDE Neon install (which I am now using). After seeing that both worked, I followed the migration guide. Initially, after the apt upgrade, I noticed that a few packages were upgradable but not upgraded (dbus-bin, dbus-daemon, dbus-x11, dbus, libdbs-1-3, and init... also octave*). However, looking ahead I saw -f install, rebooting, purging, and autocleaning, so thought that maybe this was as intended. I suspect this is where I made a mistake. Installing eudev and sysvinit-core did force init to install without me manually doing that. Rebooting after the -f install I had a headless install, as expected (I use mate), but it said at the top

startpar: services returned failure: nscd network-manager . . . failed

* octave is upgradable but not upgraded since I edited the .deb from the debian repo to remove the gui since I use geany for it and have no qt except on the neon install; I highly doubt this has any effect but am telling out of precaution

Now, what would be the safest way to continue? I chrooted into it to get that list of upgradable and not upgraded packages (I'm lazy and didn't write it down), and could install that way, similar to installing enough packages to set up wifi on a debootstrap-install. Alternatively, I could download the remaining packages and install them when truly booted into that install (well, efibootmgr will say I'm booted into neon since I'm using this grub to avoid ambiguities for the time being, but I assume it is okay since grub gets me in the correct one). I do not like the other options of using the clone or cloning the clone over this attempt, because I want to keep at least one working debian/devuan install at all times and cloning takes a day and a half. Is it safe to continue the migration from a chroot (since I already rebooted), at least enough to get wifi working? This is my preferred method as it is easiest.

delgado · 2023-12-27 00:09:52

Continuing the migration in a chroot should work. I would do so too.

Network-manager most likely needs updated configuration after migration (see below).

--
Remembering the migration of my notebook to chimaera:
One thing that happens during migration is: The network-device's name changes (from forgotten) to "wlan0" in case of wifi.
The network-manager's config files were still pointing to the prior device name. This was the reason for "no network connection".
The alternative to reconfigure network-manager was to restore the prior network device names:

# echo 'GRUB_CMDLINE_LINUX="net.ifnames=1"' >>/etc/default/grub
# update-grub
# reboot

Using update-grub may or may not be a bad idea in your multi-boot case.

paculino · 2023-12-27 00:19:20

Thank you! Should I continue where I left off, or do I need to force upgrade the packages that did not upgrade and then reboot again?

Last edited by paculino (2023-12-27 00:21:12)

delgado · 2023-12-27 11:21:03

I would check that sysvinit is installed (and running if booted):

apt list --installed | grep sysvinit-core
apt list --installed | grep systemd

Obviously, there should be sysvinit-core and no systemd. Then:

apt update
apt -s upgrade
apt upgrade
apt -s dist-upgrade
apt dist-upgrade

usually did it (without forcing or expicit de-installs).
The apt -s lines are optional. They do a simulation to spot problems. It might be tricky to solve dependencies in an interrupted migration.

Some programs will be de-installed during migration, so there is stuff to re-install.
And optional clean-up at the end: apt clean and/or apt autoremove

--
PS: Booted installtion with sysvinit:

$ ps ax | head -2
  PID TTY      STAT   TIME COMMAND
    1 ?        Ss     0:00 init [2]

In case of systemd: PID 1 is "/sbin/init"

paculino · 2023-12-28 02:42:10

Alright, I've had it fixed for a day, but I just now fixed the DE and halfway fixed the internet. Thank you everyone.

I misunderstood the sticky on systemd mentioning libsystemd0 being used sometimes to determine if systemd was running, and thought that this package was necessary, so I tried to use the dummy-elogind, but this would not allow some packages that were part of task-mate-desktop, so I had a partial de install and dummy-elogind. Fortunately, I figured it out when I looked into what would break when I removed libsystemd0. My wifi applet does not work (that is okay; I don't necessarily need a gui for it as long as it works), but I followed the excellent guide by quickfir and got it working (the only difference was I had to use apt-file to locate iwconfig and ifup... now they work). If I have time next semester, I may try to edit the applet to get a gui method for this workaround.

Last edited by paculino (2023-12-28 02:50:47)

golinux · 2023-12-28 02:56:34

This this forum post titled Why are systemd files present in Devuan? will help you understand that those files that are bothering you are harmless and necessary. Note that I posted that statement but did not write it. Take care . . .

paculino · 2023-12-28 05:16:07

Yes, that is the one I read; task-mate-desktop kept removing libsystemd0. Now, when I try to install libsystemd0, it wants to remove task-mate-desktop, mate-desktop-environment, mate-desktop-environment-core, caja, gvfs-backends, mate-applets, gvfs, gvfs-daemons, gvfs-fuse, udisks2, network-manager-gnome, network-manager, libpam-elogind, and libelogind-compat
I am currently booted without libsystemd0 because it apparently conflicts, either directly or indirectly, with these packages. I do not think libsystemd0 is harmful, but I seem to be unable to have it, as holding it when installed would not allow installing these packages (well, dummy-elogind allowed some of them, but not all).

golinux · 2023-12-28 15:30:43

paculino wrote:

I do not think libsystemd0 is harmful

Yes, it is just an annoyance but removing it would be wasted effort for no benefit. That's why it may still present in Devuan.

paculino wrote:

but I seem to be unable to have it, as holding it when installed would not allow installing these packages (well, dummy-elogind allowed some of them, but not all).

Unless something has changed, there is no need to have libsystemd0 present in Devuan.

paculino · 2023-12-28 20:07:13

Oh, sorry, I misunderstood twice that it was required. First in the sticky, then in here.

The officially official Devuan Forum!

#1 2023-12-26 01:09:57

Bookworm -> Daedalus migration nscd network-manager failed

#2 2023-12-27 00:09:52

Re: Bookworm -> Daedalus migration nscd network-manager failed

#3 2023-12-27 00:19:20

Re: Bookworm -> Daedalus migration nscd network-manager failed

#4 2023-12-27 11:21:03

Re: Bookworm -> Daedalus migration nscd network-manager failed

#5 2023-12-28 02:42:10

Re: Bookworm -> Daedalus migration nscd network-manager failed

#6 2023-12-28 02:56:34

Re: Bookworm -> Daedalus migration nscd network-manager failed

#7 2023-12-28 05:16:07

Re: Bookworm -> Daedalus migration nscd network-manager failed

#8 2023-12-28 15:30:43

Re: Bookworm -> Daedalus migration nscd network-manager failed

#9 2023-12-28 20:07:13

Re: Bookworm -> Daedalus migration nscd network-manager failed

Board footer