Mageia forum

Booting "mageia-prepare-upgrade" fails on "Starting var-tmp.mount". The message is: "Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: No such file or directory"
Looking at the filesystem it seems like it already moved the /bin /lib and /sbin
Any hint?

Hmmm, we haven't seen anything like that in the tests. Can you open a bug report with the details of what you did and your config? Thanks!

I've restored the / partition from backup and I've retried: the messages from dracut shows that the move is done cleanly, sysctl still gives error when trying to start /var/tmp
Dependency failed. Aborted start of Setup links in /... running kernel [ABORT]
Dependency failed. Aborted start of Mark the need to...el after reboot [ABORT]
Dependency failed. Aborted start of Relabel all file...s, if necessary [ABORT]

$ systemctl status var-tmp.mount:
Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: No such file or directory

$ ls -la /run shows the existence of only one directory inside: /run/udev/

dmesg shows multiple lines containing:
systemd-cgroups-agent[PID]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused

same message after rebooting with the standard kernel
starting dbus-launcher by hand, followed by /bin/systemd creates the directory /run/systemd, but there is no socket inside, just 2 empty subdirs "ask-password" and "system"

Why, oh why, I get the impression that I'm going towards a fresh installation of Mageia 3?

Edit: preparing my bugreport...

neXt wrote:Later edit: I wold post a bugreport, if only my ID will work. Trying the username/password from identity.mageia.org does not work on bugzilla, definitely it is not my best day today

The account from identity.mageia.org works on every Mageia site, if you provide the correct credentials
Check the wiki page maybe: https://wiki.mageia.org/en/Mageia.org_user_account

thanks doktor5000, I've figured it (it's the uid, not the email)
As indicated in https://bugs.mageia.org/show_bug.cgi?id=10182 the existence of a tmps on /var/tmp was the cause of the problem. If anyone uses this kind of setup, he/she should comment the line referencing /var/tmp in the /etc/fstab.