Re: [systemd-devel] networkd failing sporadically failing to bring up network device
On Tue, Apr 7, 2015 at 5:46 PM, Richard Maw richard@codethink.co.uk wrote: On Sat, Apr 04, 2015 at 12:08:04PM +0100, Sitsofe Wheeler wrote: Hi, I've noticed that networkd occasionally fails to bring up one of two network interfaces on boot (this happens about once every 70 or so boots). The machine in question is a VMware ESXi 5.5 guest with two VMXNET3 network adaptors. When this issue occurs the message rtnl: received address for a nonexistent link (1), ignoring is present in the journal. Does anyone know if this is a known issue in systemd 216 (I'm using Fedora 21)? I've attached a journal log below: There's been a few post-217 changes related to parsing messages in rtnl, one of which was related to accidentally interpreting change notifications as responses under rare circumstances, so there are some known bugs in 216, but I haven't encountered yours before. Re-testing with the latest systemd snapshot would let us know if it's one of the bugs fixed post 217. If it comes to debugging what netlink is doing, one option is to use the nlmon interface, capture it with tcpdump as described in http://seclists.org/tcpdump/2014/q4/32 and then use wireshark to parse the dump. Seems I missed parts of this thread (I cannot find the original email in my archive), so in case I missed something important: could this be reproduced with current git, or is this seemingly resolved now? Cheers, Tom ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] networkd failing sporadically failing to bring up network device
On Sat, Apr 04, 2015 at 12:08:04PM +0100, Sitsofe Wheeler wrote: Hi, I've noticed that networkd occasionally fails to bring up one of two network interfaces on boot (this happens about once every 70 or so boots). The machine in question is a VMware ESXi 5.5 guest with two VMXNET3 network adaptors. When this issue occurs the message rtnl: received address for a nonexistent link (1), ignoring is present in the journal. Does anyone know if this is a known issue in systemd 216 (I'm using Fedora 21)? I've attached a journal log below: There's been a few post-217 changes related to parsing messages in rtnl, one of which was related to accidentally interpreting change notifications as responses under rare circumstances, so there are some known bugs in 216, but I haven't encountered yours before. Re-testing with the latest systemd snapshot would let us know if it's one of the bugs fixed post 217. If it comes to debugging what netlink is doing, one option is to use the nlmon interface, capture it with tcpdump as described in http://seclists.org/tcpdump/2014/q4/32 and then use wireshark to parse the dump. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] networkd failing sporadically failing to bring up network device
Hi, I've noticed that networkd occasionally fails to bring up one of two network interfaces on boot (this happens about once every 70 or so boots). The machine in question is a VMware ESXi 5.5 guest with two VMXNET3 network adaptors. When this issue occurs the message rtnl: received address for a nonexistent link (1), ignoring is present in the journal. Does anyone know if this is a known issue in systemd 216 (I'm using Fedora 21)? I've attached a journal log below: (systemd-216-20.fc21.x86_64) Apr 03 11:15:47 h systemd[1]: Starting Login Service... Apr 03 11:15:47 h systemd[1]: Starting D-Bus System Message Bus... Apr 03 11:15:47 h systemd[1]: Started D-Bus System Message Bus. Apr 03 11:15:48 h chronyd[397]: chronyd version 1.31 starting Apr 03 11:15:48 h kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Apr 03 11:15:48 h kernel: [drm] Initialized drm 1.1.0 20060810 Apr 03 11:15:48 h kernel: piix4_smbus :00:07.3: SMBus Host Controller not enabled! Apr 03 11:15:48 h kernel: parport_pc 00:05: reported by Plug and Play ACPI Apr 03 11:15:48 h kernel: parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] Apr 03 11:15:48 h kernel: vmw_vmci :00:07.7: Found VMCI PCI device at 0x11080, irq 16 Apr 03 11:15:48 h kernel: vmw_vmci :00:07.7: Using capabilities 0xc Apr 03 11:15:48 h chronyd[397]: Frequency -2.442 +/- 94.425 ppm read from /var/lib/chrony/drift Apr 03 11:15:48 h kernel: vmw_vmci :00:07.7: irq 57 for MSI/MSI-X Apr 03 11:15:48 h kernel: vmw_vmci :00:07.7: irq 58 for MSI/MSI-X Apr 03 11:15:48 h kernel: Guest personality initialized and is active Apr 03 11:15:48 h kernel: VMCI host device registered (name=vmci, major=10, minor=58) Apr 03 11:15:48 h kernel: Initialized host personality Apr 03 11:15:48 h systemd-vconsole-setup[405]: /usr/bin/setfont failed with error code 1. Apr 03 11:15:48 h systemd-vconsole-setup[405]: /usr/bin/loadkeys failed with error code 1. Apr 03 11:15:48 h systemd[1]: Starting Network Service... Apr 03 11:15:48 h systemd[1]: Started NTP client/server. Apr 03 11:15:48 h systemd[1]: Found device /dev/ttyS0. Apr 03 11:15:48 h systemd-logind[387]: Watching system buttons on /dev/input/event0 (Power Button) Apr 03 11:15:48 h systemd-logind[387]: New seat seat0. Apr 03 11:15:48 h systemd[1]: Started Login Service. Apr 03 11:15:48 h kernel: alg: No test for crc32 (crc32-pclmul) Apr 03 11:15:48 h kernel: VMware vmxnet3 virtual NIC driver - version 1.2.1.0-k-NAPI Apr 03 11:15:48 h kernel: vmxnet3 :0b:00.0: # of Tx queues : 1, # of Rx queues : 1 Apr 03 11:15:48 h kernel: vmxnet3 :0b:00.0: irq 59 for MSI/MSI-X Apr 03 11:15:48 h kernel: vmxnet3 :0b:00.0: irq 60 for MSI/MSI-X Apr 03 11:15:48 h kernel: vmxnet3 :0b:00.0 eth0: NIC Link is Up 1 Mbps Apr 03 11:15:48 h kernel: ppdev: user-space parallel port driver Apr 03 11:15:48 h kernel: vmxnet3 :13:00.0: # of Tx queues : 1, # of Rx queues : 1 Apr 03 11:15:48 h systemd-networkd[422]: timestamp of '/etc/systemd/network' changed Apr 03 11:15:48 h kernel: vmxnet3 :13:00.0: irq 61 for MSI/MSI-X Apr 03 11:15:48 h kernel: vmxnet3 :13:00.0: irq 62 for MSI/MSI-X Apr 03 11:15:48 h kernel: vmxnet3 :13:00.0 eth1: NIC Link is Up 1 Mbps Apr 03 11:15:48 h kernel: [drm] DMA map mode: Using physical TTM page addresses. Apr 03 11:15:48 h kernel: [drm] Capabilities: Apr 03 11:15:48 h kernel: [drm] Rect copy. Apr 03 11:15:48 h kernel: [drm] Cursor. Apr 03 11:15:48 h kernel: [drm] Cursor bypass. Apr 03 11:15:48 h kernel: [drm] Cursor bypass 2. Apr 03 11:15:48 h kernel: [drm] 8bit emulation. Apr 03 11:15:48 h kernel: [drm] Alpha cursor. Apr 03 11:15:48 h kernel: [drm] Extended Fifo. Apr 03 11:15:48 h kernel: [drm] Multimon. Apr 03 11:15:48 h kernel: [drm] Pitchlock. Apr 03 11:15:48 h kernel: [drm] Irq mask. Apr 03 11:15:48 h kernel: [drm] Display Topology. Apr 03 11:15:48 h kernel: [drm] GMR. Apr 03 11:15:48 h kernel: [drm] Traces. Apr 03 11:15:48 h kernel: [drm] GMR2. Apr 03 11:15:48 h kernel: [drm] Screen Object 2. Apr 03 11:15:48 h kernel: [drm] Command Buffers. Apr 03 11:15:48 h kernel: [drm] Max GMR ids is 64 Apr 03 11:15:48 h kernel: [drm] Max number of GMR pages is 65536 Apr 03 11:15:48 h kernel: [drm] Max dedicated hypervisor surface memory is 163840 kiB Apr 03 11:15:48 h kernel: [drm] Maximum display memory size is 8192 kiB Apr 03 11:15:48 h kernel: [drm] VRAM at 0xec00 size is 8192 kiB Apr 03 11:15:48 h kernel: [drm] MMIO at 0xfe00 size is 256 kiB Apr 03 11:15:48 h kernel: [drm] global init. Apr 03 11:15:48 h kernel: [TTM] Zone kernel: Available graphics memory: 508754 kiB Apr 03 11:15:48 h kernel: [TTM] Initializing pool allocator Apr 03 11:15:48 h kernel: [TTM] Initializing DMA pool allocator Apr 03 11:15:48 h kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Apr 03 11:15:48 h kernel: [drm] No driver support for vblank timestamp query. Apr 03 11:15:48 h kernel: [drm] Screen objects system initialized Apr
