Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
Hi Wolfgang, On Thursday, May 17, 2018, Wolfgang Schweer wrote: > On Thu, May 17, 2018 at 10:42:13AM +, Mike Gabriel wrote: > > On Di 15 Mai 2018 22:14:22 CEST, Wolfgang Schweer wrote: > > > > > It works for me too (virtual network, no real world deployment > > > available), if all entries except the loopback ones are commented. > > > > > > > So, you are saying that all network entries except loopback are commented > > out by defaut on workstation installations on buster? Also on stretch? I > > don't fully get what you mean by the last mail. > > Maybe some sort of misunderstanding. > What I meant is: I tried with the loopback entries as only ones and can > confirm that it works as well. So the mostly empty interface file could > (should) be the default… > > > Note: this is not about NIC names, but about the NIC being commented out or > > not. On stretch, I have seen auto eth0 and inet eth0 ... being active and > > thus being ignored by the NetworkManager-wait-online.service. > > Same for Buster. > > Wolfgang > I somehow feel, this is worth a stretch-pu... Mike -- Sent from my Fairphone (powered by SailfishOS)
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
On Thu, May 17, 2018 at 10:42:13AM +, Mike Gabriel wrote: > On Di 15 Mai 2018 22:14:22 CEST, Wolfgang Schweer wrote: > > > It works for me too (virtual network, no real world deployment > > available), if all entries except the loopback ones are commented. > > > > So, you are saying that all network entries except loopback are commented > out by defaut on workstation installations on buster? Also on stretch? I > don't fully get what you mean by the last mail. Maybe some sort of misunderstanding. What I meant is: I tried with the loopback entries as only ones and can confirm that it works as well. So the mostly empty interface file could (should) be the default… > Note: this is not about NIC names, but about the NIC being commented out or > not. On stretch, I have seen auto eth0 and inet eth0 ... being active and > thus being ignored by the NetworkManager-wait-online.service. Same for Buster. Wolfgang signature.asc Description: PGP signature
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
On Di 15 Mai 2018 22:14:22 CEST, Wolfgang Schweer wrote: It works for me too (virtual network, no real world deployment available), if all entries except the loopback ones are commented. So, you are saying that all network entries except loopback are commented out by defaut on workstation installations on buster? Also on stretch? I don't fully get what you mean by the last mail. Note: this is not about NIC names, but about the NIC being commented out or not. On stretch, I have seen auto eth0 and inet eth0 ... being active and thus being ignored by the NetworkManager-wait-online.service. The proper approach is having /etc/network/interfaces empty except for the loopback device. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgppGqp8OJzRh.pgp Description: Digitale PGP-Signatur
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
On Tue, May 15, 2018 at 07:58:30AM +, Mike Gabriel wrote: > The point is that /etc/network/interfaces has an entry for eth0 (or what the > first NIC is called). > > This is true for stretch, at least. Could you check, if your buster systems > manage eth0 via ifupdown? If so, NetworkManager ignores that interface and > the wait-online service has no effect on that device. Hi Mike. AFAIK this is the case since ages (forced to be ethX instead of a predictable interface name via kernel command line param 'net.ifnames=0' setting in grub.conf since Stretch). It works for me too (virtual network, no real world deployment available), if all entries except the loopback ones are commented. > This is true for stretch, at least. Could you check, if your buster > systems manage eth0 via ifupdown? If so, NetworkManager ignores that > interface and the wait-online service has no effect on that device. IIRC, the NetworkManager configuration isn't touched at all by d-e-config, i.e. it's the one shipped w/ package 'network-manager': [main] plugins=ifupdown,keyfile [ifupdown] managed=false Wolfgang signature.asc Description: PGP signature
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
Hi Wolfgang, On Mo 22 Jan 2018 01:17:54 CET, Wolfgang Schweer wrote: On Sun, Jan 21, 2018 at 02:56:17PM +0100, Wolfgang Schweer wrote: On Sun, Jan 21, 2018 at 01:41:53PM +, Mike Gabriel wrote: > we install with desktop=mate. Also on those? My experience with various > stretch workstations is different. We will double check tomorrow / Tuesday. Tested: mate on Buster, xfce on Stretch (others not available atm). Other DEs as well: gnome, kde, mate (Stretch). NetworkManager-wait-online.service is always enabled. Also, from network-magager changelog: -- network-manager (1.2.2-2) unstable; urgency=medium * Let NetworkManager.service pull in network.target. This will provide a proper ordering on shutdown. * Enable NetworkManager-wait-online.service. This ensures thatmounting of network file systems works properly and SysV init scripts depending on $network will be delayed until network is available (or a timeout is reached). * Make sure NetworkManager-wait-online.service is enabled on upgrades. We need to purge the old state, otherwise i-s-h won't enable the service on upgrades. -- Michael Biebl Thu, 02 Jun 2016 19:00:45 +0200 --- AFAICT d-e-c does nothing to change this default behaviour. Wolfgang Some weeks ago, we move forward with this issue. The point is not that NetworkManager.wait-online.service is not enabled. The point is that /etc/network/interfaces has an entry for eth0 (or what the first NIC is called). This is true for stretch, at least. Could you check, if your buster systems manage eth0 via ifupdown? If so, NetworkManager ignores that interface and the wait-online service has no effect on that device. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpc5QlQ5e_AZ.pgp Description: Digitale PGP-Signatur
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
control: notfound -1 1.929 thanks On Mon, Jan 22, 2018 at 01:17:54AM +0100, Wolfgang Schweer wrote: > > Tested: mate on Buster, xfce on Stretch (others not available atm). > Other DEs as well: gnome, kde, mate (Stretch). > NetworkManager-wait-online.service is always enabled. adjusting the meta data accordingly again. -- cheers, Holger signature.asc Description: PGP signature
Processed: Re: Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
Processing control commands: > notfound -1 1.929 Bug #887861 [debian-edu-config] Enable NetworkManager.wait-online.service on diskful workstations No longer marked as found in versions debian-edu-config/1.929. -- 887861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
On Sun, Jan 21, 2018 at 02:56:17PM +0100, Wolfgang Schweer wrote: > On Sun, Jan 21, 2018 at 01:41:53PM +, Mike Gabriel wrote: > > we install with desktop=mate. Also on those? My experience with various > > stretch workstations is different. We will double check tomorrow / Tuesday. > > Tested: mate on Buster, xfce on Stretch (others not available atm). Other DEs as well: gnome, kde, mate (Stretch). NetworkManager-wait-online.service is always enabled. Also, from network-magager changelog: -- network-manager (1.2.2-2) unstable; urgency=medium * Let NetworkManager.service pull in network.target. This will provide a proper ordering on shutdown. * Enable NetworkManager-wait-online.service. This ensures thatmounting of network file systems works properly and SysV init scripts depending on $network will be delayed until network is available (or a timeout is reached). * Make sure NetworkManager-wait-online.service is enabled on upgrades. We need to purge the old state, otherwise i-s-h won't enable the service on upgrades. -- Michael Biebl Thu, 02 Jun 2016 19:00:45 +0200 --- AFAICT d-e-c does nothing to change this default behaviour. Wolfgang signature.asc Description: PGP signature
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
control: notfound -1 1.945 control: found -1 1.818+deb8u2 control: found -1 1.929 thanks On Sun, Jan 21, 2018 at 10:17:18AM +, Mike Gabriel wrote: > > Are you talking about Jessie? Stretch?. IIRC this issue disappeared with > > Stretch. (Virtual machines only, no real hardware available.) > I am talking about jessie and stretch. The issue occurs less often in > stretch. fixing the metadata accordingly. -- cheers, Holger signature.asc Description: PGP signature
Processed: Re: Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
Processing control commands: > notfound -1 1.945 Bug #887861 [debian-edu-config] Enable NetworkManager.wait-online.service on diskful workstations Ignoring request to alter found versions of bug #887861 to the same values previously set > found -1 1.818+deb8u2 Bug #887861 [debian-edu-config] Enable NetworkManager.wait-online.service on diskful workstations Marked as found in versions debian-edu-config/1.818+deb8u2. > found -1 1.929 Bug #887861 [debian-edu-config] Enable NetworkManager.wait-online.service on diskful workstations Marked as found in versions debian-edu-config/1.929. -- 887861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
On Sun, Jan 21, 2018 at 01:41:53PM +, Mike Gabriel wrote: > we install with desktop=mate. Also on those? My experience with various > stretch workstations is different. We will double check tomorrow / Tuesday. Tested: mate on Buster, xfce on Stretch (others not available atm). Wolfgang signature.asc Description: PGP signature
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
Hi Wolfgang, On So 21 Jan 2018 14:38:16 CET, Wolfgang Schweer wrote: On Sun, Jan 21, 2018 at 10:17:18AM +, Mike Gabriel wrote: > > The history of getting the issue solved is long. Our recent fix, however, > > seems to be sustainable: > > > > systemctl enable NetworkManager-wait-online.service > > > > Once that unit is enabled, systems boot and logon to the system with an LDAP > > / NFS user is always possible. No failures seen so far. On different > > hardware variants. On stock workstations (new installations, both Stretch and Buster), 'systemctl status NetworkManager-wait-online.service' tells me that the service is enabled… Wolfgang we install with desktop=mate. Also on those? My experience with various stretch workstations is different. We will double check tomorrow / Tuesday. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpS_q8XZISQX.pgp Description: Digitale PGP-Signatur
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
On Sun, Jan 21, 2018 at 10:17:18AM +, Mike Gabriel wrote: > > > The history of getting the issue solved is long. Our recent fix, however, > > > seems to be sustainable: > > > > > > systemctl enable NetworkManager-wait-online.service > > > > > > Once that unit is enabled, systems boot and logon to the system with an > > > LDAP > > > / NFS user is always possible. No failures seen so far. On different > > > hardware variants. On stock workstations (new installations, both Stretch and Buster), 'systemctl status NetworkManager-wait-online.service' tells me that the service is enabled… Wolfgang signature.asc Description: PGP signature
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
Hi Wolfgang, On So 21 Jan 2018 11:02:42 CET, Wolfgang Schweer wrote: Hi Mike, On Sun, Jan 21, 2018 at 12:19:54AM +, Mike Gabriel wrote: for the last couple of years, we have always been struggling with a race condition during boot up of diskful Skolelinux Workstations. The race was between network coming up and autofs launching. We thought we had fixed it several times since squeeze. But when hardware changed (mostly when the hardware became faster during boot), the issue turned back on. Are you talking about Jessie? Stretch?. IIRC this issue disappeared with Stretch. (Virtual machines only, no real hardware available.) I am talking about jessie and stretch. The issue occurs less often in stretch. I have stuffed 12 new SSD in 12 old notebooks. With slow hard drives the issues seemed to be gone. With the crazily fast new SSDs, 3-4 out of 12 had not autofs homes after reboot. The issue occurs nearly up to a 100% probability when the workstations connect to the network over WiFi with a system wide configured WPA2 WiFi connection. With the NetworkManager-wait-online service enabled, the systems take a while to come up, but login over WiFi works always then. No failures seen so far. The history of getting the issue solved is long. Our recent fix, however, seems to be sustainable: systemctl enable NetworkManager-wait-online.service Once that unit is enabled, systems boot and logon to the system with an LDAP / NFS user is always possible. No failures seen so far. On different hardware variants. @Wolfgang: Where would be the best place to put the above line during system installation of diskful normal workstations? cf/cf.homes (Stretch) cf3/cf.homes (Buster) Ack. As an example, see how autofs is disabled conditionally (main server installation). Ack. Will propose a patch soonish... Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpE1di7nX_B2.pgp Description: Digitale PGP-Signatur
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
Hi Mike, On Sun, Jan 21, 2018 at 12:19:54AM +, Mike Gabriel wrote: > for the last couple of years, we have always been struggling with a race > condition during boot up of diskful Skolelinux Workstations. The race was > between network coming up and autofs launching. > > We thought we had fixed it several times since squeeze. But when hardware > changed (mostly when the hardware became faster during boot), the issue > turned back on. Are you talking about Jessie? Stretch?. IIRC this issue disappeared with Stretch. (Virtual machines only, no real hardware available.) > The history of getting the issue solved is long. Our recent fix, however, > seems to be sustainable: > > systemctl enable NetworkManager-wait-online.service > > Once that unit is enabled, systems boot and logon to the system with an LDAP > / NFS user is always possible. No failures seen so far. On different > hardware variants. > > @Wolfgang: Where would be the best place to put the above line during system > installation of diskful normal workstations? cf/cf.homes (Stretch) cf3/cf.homes (Buster) As an example, see how autofs is disabled conditionally (main server installation). Wolfgang signature.asc Description: PGP signature
Bug#887861: Enable NetworkManager.wait-online.service on diskful workstations
Package: debian-edu-config Severity: important Hi, for the last couple of years, we have always been struggling with a race condition during boot up of diskful Skolelinux Workstations. The race was between network coming up and autofs launching. We thought we had fixed it several times since squeeze. But when hardware changed (mostly when the hardware became faster during boot), the issue turned back on. The history of getting the issue solved is long. Our recent fix, however, seems to be sustainable: systemctl enable NetworkManager-wait-online.service Once that unit is enabled, systems boot and logon to the system with an LDAP / NFS user is always possible. No failures seen so far. On different hardware variants. @Wolfgang: Where would be the best place to put the above line during system installation of diskful normal workstations? Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpn4htlMkACJ.pgp Description: Digitale PGP-Signatur
