Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang.
This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.
--- Begin Message ---Thanks Thomas RE: * This is an error because during the installation no dbus is * running (inside the chroot). But I'm pretty sure it does not matter for the running system later. On the simple installation which finishes with a congratulations, after booting it and logging on I find: root@localhost:~# ls -l /run/dbus/system_bus_socket ls: cannot access '/run/dbus/system_bus_socket': No such file or directory root@localhost:~# systemctl status dbus Unit dbus.service could not be found. root@localhost:~# root@localhost:~# shutdown -h now Failed to connect to bus: No such file or directory root@localhost:~# The dbus packages are not present, after I apt install them and start dbus it stops grumbling. Is something going wrong here or it is something I need to add to the steps? Best regards, Stu ________________________________ From: linux-fai <linux-fai-boun...@uni-koeln.de> on behalf of Thomas Lange <la...@cs.uni-koeln.de> Sent: 23 January 2025 15:51 To: fully automatic installation for Linux <linux-fai@uni-koeln.de> Subject: Re: New to FAI, having some issues building [You don't often get email from la...@cs.uni-koeln.de. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] CAUTION: This email came from outside of the University. To keep your account safe, only click on links and open attachments if you know the person who sent the email, or you expected to receive this communication. >>>>> On Thu, 23 Jan 2025 15:23:54 +0000, Stuart Green via linux-fai >>>>> <linux-fai@uni-koeln.de> said: > The bootable autodiscover iso finds the server no problem and if I select the Simple install which does headless Debian it runs through without > error. However if I try Ubuntu then it consistently finishes with ERROR but it does boot to a usable desktop after rebooting. > fai.log:ESC[0;1;31mFailed to disable unit, unit friendly-recovery.service does not exist.ESC[0m > fai.log:ls: cannot access '/etc/NetworkManager/system-connections': No such file or directory > fai.log:info: The home dir /var/lib/usbmux you specified can't be accessed: No such file or directory > fai.log:/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape sequence '\#' > fai.log:/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape sequence '\/' > fai.log:/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape sequence '\*' > fai.log:/usr/share/hplip/fax/ledmfax.py:46: SyntaxWarning: invalid escape sequence '\d' You can ignore those warnings and also the other ones. These errors come from packages not FAI itself. > I've also tried building via fai-diskimage on my previous installs and persistently got > fai.log:start-stop-daemon: unable to stat /usr/libexec/polkitd (No such file or directory) > fai.log:Failed to open connection to "system" message bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory This is an error because during the installation no dbus is running (inside the chroot). But I'm pretty sure it does not matter for the running system later. > As I suggested in my opening words, is this going to be down to the environment? No, it's not related to your Proxmox environment. -- best regards Thomas
--- End Message ---
