Your message dated Mon, 13 Mar 2017 21:26:29 -0300
with message-id <[email protected]>
and subject line Re: Bug#856988: systemd: Timeout for
sys-subsystem-net-devices-multi-user.device with missing /etc/machine-id
has caused the Debian Bug report #856988,
regarding systemd: Timeout for sys-subsystem-net-devices-multi-user.device with
missing /etc/machine-id
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
856988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856988
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 232-18
Severity: normal
Situation: PXE boot with RO NFS and using OverlayFS for RW /.
So, I rm'ed /etc/machine-id and /var/lib/dbus/machine-id, thinking that it
would be generated at
boot and they do, but sys-subsystem-net-devices-multi-user.device timeouts
after 1m30s then.
The solution is to have an empty /etc/machine-id, but I wonder if SystemD could
be improved to
handle the situation better for another poor soul that tries to do the same as
me.
Searching I found this https://labs.riseup.net/code/issues/11970 and from there
https://labs.riseup.net/code/projects/tails/repository/revisions/0d5d4d42919818a63bfd604c62737ce337ac9d01/diff
Thanks!!!
-- Package-specific info:
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 4.9.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.11.0-2
ii libaudit1 1:2.6.7-1
ii libblkid1 2.29.1-1
ii libc6 2.24-9
ii libcap2 1:2.25-1
ii libcryptsetup4 2:1.7.3-3
ii libgcc1 1:6.3.0-6
ii libgcrypt20 1.7.6-1
ii libgpg-error0 1.26-2
ii libidn11 1.33-1
ii libip4tc0 1.6.0+snapshot20161117-5
ii libkmod2 23-2
ii liblz4-1 0.0~r131-2+b1
ii liblzma5 5.2.2-1.2+b1
ii libmount1 2.29.1-1
ii libpam0g 1.1.8-3.5
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.6-3
ii libsystemd0 232-18
ii mount 2.29.1-1
ii util-linux 2.29.1-1
Versions of packages systemd recommends:
ii dbus 1.10.16-1
ii libpam-systemd 232-18
Versions of packages systemd suggests:
ii policykit-1 0.105-17
pn systemd-container <none>
ii systemd-ui 3-4
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.127
ii udev 232-18
-- Configuration Files:
/etc/systemd/system.conf changed [not included]
/etc/systemd/timesyncd.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello, sorry for the delay!
El 06/03/17 a las 19:36, Felipe Sateler escribió:
Control: tags -1 moreinfo
On Mon, Mar 6, 2017 at 7:14 PM, Ivan Baldo <[email protected]> wrote:
Package: systemd
Version: 232-18
Severity: normal
Situation: PXE boot with RO NFS and using OverlayFS for RW /.
Out of curiosity, why do you want read-write root? I figure you could
just mount /var and /home as rw...
At the moment I could do with /etc, /var and /home as rw, yes (I
need /etc because of some specific things for some terminals, like
printers, X server woes or something else that needs to be different).
But why not having all rw? Seems simpler and used in live images.
BTW /home is a normal NFS share, not overlayfs.
So, I rm'ed /etc/machine-id and /var/lib/dbus/machine-id, thinking that it
would be generated at
boot and they do, but sys-subsystem-net-devices-multi-user.device timeouts
after 1m30s then.
Where does this multi-user.device come from? Maybe the problem is in
the component responsible of bringing up this net device.
Maybe, it needs further investigation, but its strange that the
behavior is changed simply by having an empty machine-id instead of just
a deleted one.
Anyway, I grabbed
http://cdimage.debian.org/cdimage/stretch_di_rc2/amd64/iso-cd/debian-stretch-DI-rc2-amd64-netinst.iso
and installed the standard desktop in a VM, deleted the machine-id and
everything was fine, boot was fast, etc.
So, it must be something specific to my environment.
Since not so many people will stumble upon this, I think it is
better to just close it.
I hope Google indexes this and if someone has the same problem, it
would know how to workaround it by simply having an empty machine-id.
The solution is to have an empty /etc/machine-id, but I wonder if SystemD could
be improved to
handle the situation better for another poor soul that tries to do the same as
me.
Searching I found this https://labs.riseup.net/code/issues/11970 and from there
https://labs.riseup.net/code/projects/tails/repository/revisions/0d5d4d42919818a63bfd604c62737ce337ac9d01/diff
Thanks!!!
Overlayfs root is likely to be problematic as the semantics are
different from other filesystems.
Well, its working with live distributions and seems to work fine if
I have an empty machine-id in the lower FS; its used only for the OS,
userfiles are in NFS /home.
A debug log of a failed boot would be useful too.
I don't know if we should invest more time in this problem, seems
very specific to this "strange" environment.
Thanks a lot for you thoughts and your time!!!
Keep rocking!
--
Ivan Baldo - [email protected] - http://ibaldo.codigolibre.net/
Freelance C++/PHP programmer and GNU/Linux systems administrator.
The sky is not the limit!
--- End Message ---
