Re: [systemd-devel] Bug or misconfiguration for systemd-networkd and VXLAN?
On 14.11.2022 15:49, Lukas Wolf wrote: Hi all and thanks a lot for all your work on systemd! I'm trying to setup a VXLAN configuration with multicast with systemd-networkd but struggle to make it work. What I'm trying to replicate is the following (working command): ip link add vxlan100 type vxlan id 100 dstport 4789 local 10.100.200.4 group 224.4.0.144 dev lo ttl 5 (this command fails without specifying 'dev lo') My config file, vxlan100.netdev: [NetDev] Name=vxlan100 Kind=vxlan [VXLAN] VNI=100 TTL=5 DestinationPort=4789 Group=224.0.0.144 Local=10.100.200.4 Independent=true If you want Group you need device and so cannot use Independent ... As seen in the last line of the log, it throws an invalid argument error and no VXLAN device is created. This does not happen if I remove the "Group=" part in the configuration. As mentioned above, the "ip add link" command needs a "dev=" argument to work but I have not found a way to specify a device in the netdev config file... I have also tried it without Independent=true and having a network file instead with VXLAN=vxlan100, Wat do you mean "instead"? You need network file for base interface that refers to vxlan and netdev file for vxlan. but then it just silently fails without log output. Works for me (at least, to the extent that vxlan100 is created) bor@bor-Latitude-E5450:~$ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eno1: mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether 34:e6:d7:85:0b:1c brd ff:ff:ff:ff:ff:ff altname enp0s25 3: wlp2s0: mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000 link/ether 5c:e0:c5:27:c7:70 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 6a:7b:d1:2a:ce:9d brd ff:ff:ff:ff:ff:ff 5: tap0: mtu 1500 qdisc fq_codel master br0 state DOWN mode DEFAULT group default qlen 1000 link/ether 2a:7d:ac:33:fd:47 brd ff:ff:ff:ff:ff:ff bor@bor-Latitude-E5450:~$ sudo systemctl start systemd-networkd.service bor@bor-Latitude-E5450:~$ ip l ... 13: vxlan100: mtu 1450 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether b6:1d:97:9f:e6:eb brd ff:ff:ff:ff:ff:ff bor@bor-Latitude-E5450:~$ cat /etc/systemd/network/eno1.network [Match] Name=eno1 [Link] ActivationPolicy=always-up [Network] ConfigureWithoutCarrier=true Address=10.10.10.10/24 VXLAN=vxlan100 bor@bor-Latitude-E5450:~$ cat /etc/systemd/network/vxlan100.netdev [NetDev] Name=vxlan100 Kind=vxlan [VXLAN] VNI=100 TTL=5 DestinationPort=4789 Group=224.0.0.144 Local=10.10.10.10 bor@bor-Latitude-E5450:~$
Re: [systemd-devel] Antw: [EXT] [systemd???devel] starting networking from within single user mode?
On Mon, Nov 14, 2022 at 07:57:21AM +0100, Ulrich Windl wrote: > Unless you used the options to ignore dependencies, that would mean that > either the dependencies were not correct in the RPM packages, or some unistall > scripts were not. Both would be bugs. My organization is running some weird upgrade process that does more than zypper does. I'm certain the bugginess is in our weird process. We are honoring dependencies, but clearly something else is awry. Characterizing the effects of the bugginess is hard, which is what spurred my original question. > However: When you used SUSE's standard installation using BtrFS, you should > have been able to boot a recent snapshot. The codebase I inherited does not employ BtrFS. I have a large pile of frustration about how we do things, but that's our mess, and not related to systemd. I do appreciate your feedback on the matter, nonetheless. -- Brian Reichert BSD admin/developer at large
Re: [systemd-devel] Antw: [EXT] [systemd???devel] starting networking from within single user mode?
On Mo, 14.11.22 15:06, Michael Biebl (mbi...@gmail.com) wrote: > Yeah, can we please block this Ulrich Windl guy. > He's been more of a nuisance than a benefit to this community. I have put him on moderation now. Lennart -- Lennart Poettering, Berlin
Re: [systemd-devel] Antw: [EXT] [systemd???devel] starting networking from within single user mode?
Yeah, can we please block this Ulrich Windl guy. He's been more of a nuisance than a benefit to this community. Am Mo., 14. Nov. 2022 um 09:17 Uhr schrieb Mantas Mikulėnas : > > On Mon, Nov 14, 2022 at 9:00 AM Ulrich Windl > wrote: >> >> >>> Mantas Mikulenas schrieb am 11.11.2022 um 15:49 in >> Nachricht >> : >> > On Fri, Nov 11, 2022 at 4:19 PM Brian Reichert >> > wrote: >> > >> >> On Fri, Nov 11, 2022 at 08:02:00AM +0100, Ulrich Windl wrote: >> >> > >>> Brian Reichert schrieb am 10.11.2022 um >> >> 23:04 in >> >> > Nachricht <20221110220426.ga17...@numachi.com>: >> >> > > I've managed to hose a SLES12 SP5 host; it starts to boot, then hangs. >> >> > >> >> > And what did you do to mess it up? And what do the boot messages say? >> >> >> >> A good question, and not specific to systemd, so I don't want to >> >> pollute the list archives too much on this matter. >> >> >> >> 'All' I did was remove many RPMs that I arbitrarily deemed >> >> unnecessary. >> >> >> >> I came up with a heavily trimmed-down list of SLES RPM for my SLES12 >> >> Sp5 environment. >> >> >> >> I successfully installed a server using just that trimmed-down list; >> >> yay me! >> >> >> >> I then explored 'upgrading' a running (slight older) SP5 box, using >> >> this trimmed-down list. A purposeful side effect was to uninstall >> >> RPMs not in that trimmed-down list. >> >> >> >> This latter box begins to boot, and gets at least as far as loading >> >> the initrd image, before hanging. >> >> >> > >> > Boot with "systemd.debug-shell" and use tty9 to investigate from the >> > inside. >> >> Wow! never heard of that option. Is that a kind of target, or what is the >> mechanism? >> Which of the 196 (man -k systemd | wc -l) systemd-related manual pages would >> describe it? ;-) > > > The more I read your smartass sarcastic comments here, the less I feel like > staying on this list and helping *other* people with finding stuff in those > 196 systemd-related manual pages. But I suppose that's what you want to > achieve, so that you can snark even more about how "systemd is so complex > that nobody's bothering to reply to the list anymore"? > > For those who have *actually* never heard of that option, it is documented in > systemd-debug-generator(8). > > -- > Mantas Mikulėnas
[systemd-devel] Bug or misconfiguration for systemd-networkd and VXLAN?
Hi all and thanks a lot for all your work on systemd! I'm trying to setup a VXLAN configuration with multicast with systemd-networkd but struggle to make it work. What I'm trying to replicate is the following (working command): ip link add vxlan100 type vxlan id 100 dstport 4789 local 10.100.200.4 group 224.4.0.144 dev lo ttl 5 (this command fails without specifying 'dev lo') My config file, vxlan100.netdev: [NetDev] Name=vxlan100 Kind=vxlan [VXLAN] VNI=100 TTL=5 DestinationPort=4789 Group=224.0.0.144 Local=10.100.200.4 Independent=true journalctl -u systemd-networkd (debug log enabled): systemd-networkd[1520509]: vxlan100: loaded vxlan systemd-networkd[1520509]: vxlan100: Using MAC address: [snip XYZ] systemd-networkd[1520509]: vxlan100: Creating systemd-networkd[1520509]: Failed to read $container of PID 1, ignoring: Permission denied systemd-networkd[1520509]: Found cgroup on /sys/fs/cgroup/systemd, legacy hierarchy systemd-networkd[1520509]: Found container virtualization none. systemd-networkd[1520509]: No virtualization found in DMI vendor table. systemd-networkd[1520509]: Unable to read /sys/firmware/dmi/entries/0-0/raw, using the virtualization information found in DMI vendor table, ignoring: Permission d> systemd-networkd[1520509]: UML virtualization not found in /proc/cpuinfo. systemd-networkd[1520509]: Virtualization XEN not found, /proc/xen does not exist systemd-networkd[1520509]: No virtualization found in CPUID systemd-networkd[1520509]: This platform does not support /proc/device-tree systemd-networkd[1520509]: This platform does not support /proc/sysinfo systemd-networkd[1520509]: Found VM virtualization none systemd-networkd[1520509]: /usr/lib/systemd/network/80-container-host0.network: Conditions in the file do not match the system environment, skipping. [snip] systemd-networkd[1520509]: vxlan100: netdev could not be created: Invalid argument As seen in the last line of the log, it throws an invalid argument error and no VXLAN device is created. This does not happen if I remove the "Group=" part in the configuration. As mentioned above, the "ip add link" command needs a "dev=" argument to work but I have not found a way to specify a device in the netdev config file... I have also tried it without Independent=true and having a network file instead with VXLAN=vxlan100, but then it just silently fails without log output. What am I doing wrong or is it a bug? My system: Linux 4.18.0-372.32.1.el8_6.x86_64 #1 SMP Tue Oct 25 05:53:57 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux AlmaLinux release 8.7 (Stone Smilodon) systemd: systemd 239 (239-68.el8) +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy Thanks a lot for your help and kind regards, Lukas Wolf
[systemd-devel] Antw: Re: Re: Antw: [EXT] [systemd???devel] starting networking from within single user mode?
>>> Mantas Mikulenas schrieb am 14.11.2022 um 09:17 in Nachricht : > On Mon, Nov 14, 2022 at 9:00 AM Ulrich Windl < > ulrich.wi...@rz.uni-regensburg.de> wrote: > >> >>> Mantas Mikulenas schrieb am 11.11.2022 um 15:49 in >> Nachricht >> : >> > On Fri, Nov 11, 2022 at 4:19 PM Brian Reichert >> wrote: >> > >> >> On Fri, Nov 11, 2022 at 08:02:00AM +0100, Ulrich Windl wrote: >> >> > >>> Brian Reichert schrieb am 10.11.2022 um >> >> 23:04 in >> >> > Nachricht <20221110220426.ga17...@numachi.com>: >> >> > > I've managed to hose a SLES12 SP5 host; it starts to boot, then >> hangs. >> >> > >> >> > And what did you do to mess it up? And what do the boot messages say? >> >> >> >> A good question, and not specific to systemd, so I don't want to >> >> pollute the list archives too much on this matter. >> >> >> >> 'All' I did was remove many RPMs that I arbitrarily deemed >> >> unnecessary. >> >> >> >> I came up with a heavily trimmed-down list of SLES RPM for my SLES12 >> >> Sp5 environment. >> >> >> >> I successfully installed a server using just that trimmed-down list; >> >> yay me! >> >> >> >> I then explored 'upgrading' a running (slight older) SP5 box, using >> >> this trimmed-down list. A purposeful side effect was to uninstall >> >> RPMs not in that trimmed-down list. >> >> >> >> This latter box begins to boot, and gets at least as far as loading >> >> the initrd image, before hanging. >> >> >> > >> > Boot with "systemd.debug-shell" and use tty9 to investigate from the >> inside. >> >> Wow! never heard of that option. Is that a kind of target, or what is the >> mechanism? >> Which of the 196 (man -k systemd | wc -l) systemd-related manual pages >> would describe it? ;-) >> > > The more I read your smartass sarcastic comments here, the less I feel like > staying on this list and helping *other* people with finding stuff in those > 196 systemd-related manual pages. But I suppose that's what you want to > achieve, so that you can snark even more about how "systemd is so complex > that nobody's bothering to reply to the list anymore"? > > For those who have *actually* never heard of that option, it is documented > in systemd-debug-generator(8). Thank your for the nice words (people like you seem to like). After Michaels message I was able to locate the documentation. Please save your nice words for other people seeking for help here. Regards, Ulrich
[systemd-devel] Antw: Re: [systemd‑devel] Antw: Re: Antw: [EXT] [systemd???devel] starting networking from within single user mode?
>>> Michael Chapman schrieb am 14.11.2022 um 09:03 in Nachricht <2888d487-984a-b071-fa79-b18f662ef...@very.puzzling.org>: > On Mon, 14 Nov 2022, Ulrich Windl wrote: > [...] >> > Boot with "systemd.debug‑shell" and use tty9 to investigate from the inside. >> >> Wow! never heard of that option. Is that a kind of target, or what is the > mechanism? >> Which of the 196 (man ‑k systemd | wc ‑l) systemd‑related manual pages would > describe it? ;‑) > > All of systemd's kernel command‑line options are documented under "KERNEL > COMMAND LINE" in the systemd(1) man page. OK, that explains it: In my version of the manual page (systemd-249.12) that parameter does not exist. No surprise that I've never heard of it. However when reading systemd.directives(7), it says the command is explained in kernel-command-line(7). Looking there it refers to systemd-debug-generator(8). The latter refers to debug-shell.service. > > When you're in doubt where something might be documented, look at > systemd.directives(7). You'll find them there too. OK! Thanks! Regards, Ulrich
Re: [systemd-devel] Antw: Re: Antw: [EXT] [systemd???devel] starting networking from within single user mode?
On Mon, Nov 14, 2022 at 10:19 AM Michael Chapman wrote: > On Mon, 14 Nov 2022, Ulrich Windl wrote: > [...] > > Wow! never heard of that option. Is that a kind of target, or what is > the mechanism? > > Which of the 196 (man -k systemd | wc -l) systemd-related manual pages > would describe it? ;-) > > A small correction to my previous email: this particular boot parameter is > actually documented in kernel-command-line(7). It's not implemented by > PID 1 itself. > > And it should actually be "systemd.debug_shell" with an underscore, not a > hyphen. > proc_cmdline_key_streq() treats - and _ as identical (behaving like kernel options, I believe). -- Mantas Mikulėnas
Re: [systemd-devel] Antw: Re: Antw: [EXT] [systemd???devel] starting networking from within single user mode?
On Mon, 14 Nov 2022, Ulrich Windl wrote: [...] > Wow! never heard of that option. Is that a kind of target, or what is the > mechanism? > Which of the 196 (man -k systemd | wc -l) systemd-related manual pages would > describe it? ;-) A small correction to my previous email: this particular boot parameter is actually documented in kernel-command-line(7). It's not implemented by PID 1 itself. And it should actually be "systemd.debug_shell" with an underscore, not a hyphen.
Re: [systemd-devel] Antw: [EXT] [systemd???devel] starting networking from within single user mode?
On Mon, Nov 14, 2022 at 9:00 AM Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: > >>> Mantas Mikulenas schrieb am 11.11.2022 um 15:49 in > Nachricht > : > > On Fri, Nov 11, 2022 at 4:19 PM Brian Reichert > wrote: > > > >> On Fri, Nov 11, 2022 at 08:02:00AM +0100, Ulrich Windl wrote: > >> > >>> Brian Reichert schrieb am 10.11.2022 um > >> 23:04 in > >> > Nachricht <20221110220426.ga17...@numachi.com>: > >> > > I've managed to hose a SLES12 SP5 host; it starts to boot, then > hangs. > >> > > >> > And what did you do to mess it up? And what do the boot messages say? > >> > >> A good question, and not specific to systemd, so I don't want to > >> pollute the list archives too much on this matter. > >> > >> 'All' I did was remove many RPMs that I arbitrarily deemed > >> unnecessary. > >> > >> I came up with a heavily trimmed-down list of SLES RPM for my SLES12 > >> Sp5 environment. > >> > >> I successfully installed a server using just that trimmed-down list; > >> yay me! > >> > >> I then explored 'upgrading' a running (slight older) SP5 box, using > >> this trimmed-down list. A purposeful side effect was to uninstall > >> RPMs not in that trimmed-down list. > >> > >> This latter box begins to boot, and gets at least as far as loading > >> the initrd image, before hanging. > >> > > > > Boot with "systemd.debug-shell" and use tty9 to investigate from the > inside. > > Wow! never heard of that option. Is that a kind of target, or what is the > mechanism? > Which of the 196 (man -k systemd | wc -l) systemd-related manual pages > would describe it? ;-) > The more I read your smartass sarcastic comments here, the less I feel like staying on this list and helping *other* people with finding stuff in those 196 systemd-related manual pages. But I suppose that's what you want to achieve, so that you can snark even more about how "systemd is so complex that nobody's bothering to reply to the list anymore"? For those who have *actually* never heard of that option, it is documented in systemd-debug-generator(8). -- Mantas Mikulėnas
Re: [systemd-devel] Antw: Re: Antw: [EXT] [systemd???devel] starting networking from within single user mode?
On Mon, 14 Nov 2022, Ulrich Windl wrote: [...] > > Boot with "systemd.debug-shell" and use tty9 to investigate from the inside. > > Wow! never heard of that option. Is that a kind of target, or what is the > mechanism? > Which of the 196 (man -k systemd | wc -l) systemd-related manual pages would > describe it? ;-) All of systemd's kernel command-line options are documented under "KERNEL COMMAND LINE" in the systemd(1) man page. When you're in doubt where something might be documented, look at systemd.directives(7). You'll find them there too.
