[Bug 1928733] Re: Starting systemd Network Service fails with "Invalid argument"
Hi Dan, Thank you for that. The server is bare metal, not in a container. If I understand correctly the fix will go in the latest Bionic packages? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928733 Title: Starting systemd Network Service fails with "Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1928733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928733] Re: Starting systemd Network Service fails with "Invalid argument"
Would there be any update on this please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928733 Title: Starting systemd Network Service fails with "Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928733] Re: Starting systemd Network Service fails with "Invalid argument"
Hi Dan, thanks for that. Interestingly it was much harder to reproduce the problem with debugging enabled, but we got it on about the 15th try. The log is attached. ** Attachment added: "systemd-networkd-1.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928733/+attachment/5498612/+files/systemd-networkd-1.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928733 Title: Starting systemd Network Service fails with "Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928733] [NEW] Starting systemd Network Service fails with "Invalid argument"
Public bug reported: This server has a new install of Ubuntu 18.04 server. Sometimes (around 50% of the time) when it boots systemd-networkd.service initially fails to start with an error as below. It then tries again and succeeds, however other services which depend on systemd-networkd have already failed on the dependency by then. >From the output of "journalctl -u systemd-networkd": -- Reboot -- May 17 19:44:28 server1 systemd[1]: Starting Network Service... May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed to set up mount namespacing: Invalid argument May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-networkd: Invalid argument May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=226/NAMESPACE May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. May 17 19:44:30 server1 systemd[1]: Failed to start Network Service. May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1. May 17 19:44:30 server1 systemd[1]: Stopped Network Service. May 17 19:44:30 server1 systemd[1]: Starting Network Service... May 17 19:44:30 server1 systemd-networkd[2321]: Enumeration completed May 17 19:44:30 server1 systemd[1]: Started Network Service. May 17 19:44:30 server1 systemd-networkd[2321]: eno2: IPv6 successfully enabled May 17 19:44:30 server1 systemd-networkd[2321]: eno1: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: eno1: IPv6 successfully enabled May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not managed by us May 17 19:44:31 server1 systemd-networkd[2321]: eno2: Link UP May 17 19:44:31 server1 systemd-networkd[2321]: eno1: Link UP May 17 19:44:34 server1 systemd-networkd[2321]: eno2: Gained carrier May 17 19:44:34 server1 systemd-networkd[2321]: eno1: Gained carrier May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Gained IPv6LL May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Configured May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Gained IPv6LL May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Configured ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.46 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Mon May 17 19:53:11 2021 InstallationDate: Installed on 2021-03-18 (60 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1604:10c0 Tascam Bus 001 Device 003: ID 1604:10c0 Tascam Bus 001 Device 002: ID 1604:10c0 Tascam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=/dev/mapper/vg1-lv_root ro processor.max_cstate=1 intel_idle.max_cstate=0 transparent_hugepage=never SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.3 dmi.board.name: 04JN2K dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.3:bd09/23/2020:svnDellInc.:pnPowerEdgeR440:pvr:rvnDellInc.:rn04JN2K:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R440 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928733 Title: Starting systemd Network Service fails with "Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev
I see, thank you. It's a shame that MySQL would make such a change within a major version. We have worked as follows, though it's a bit of a nasty solution: apt install libmysqlclient-dev # will install libssl-dev as a dependency apt download libssl1.0-dev # download required package manually dpkg -r --force-depends libssl-dev # remove libssl-dev without removing libmysqlclient-dev dpkg -i libssl1.0-dev_1.0.2n-1ubuntu5.3_amd64.deb # install libssl1.0-dev manually -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861304 Title: libmysqlclient-dev will not install with libssl1.0-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1861304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev
Asterisk 11 will not compile against libssl-dev. What seems strange is I believe we previously had both libssl1.0-dev and libmysqlclient-dev installed on an Ubuntu 18 server. Was the conflict introduced in an update to Ubuntu 18? If so then changing such things within a version doesn't seem ideal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861304 Title: libmysqlclient-dev will not install with libssl1.0-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1861304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev
When was this conflict between libmysqlclient-dev and libssl1.0-dev introduced? It's causing us big problems because when compiling Asterisk 11 from source it requires both. Does anyone know of a solution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861304 Title: libmysqlclient-dev will not install with libssl1.0-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1861304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 609365] Re: [i845] GPU lockup 0c457667 (PGTBL_ER: 0x00000049)
Hello, i am aware of these graphics problems. I have 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01) I have found a VERY INTERESTING DEVELOPMENT that would be great if Upstream would take a look and confirm for me. I have used Workaround C from https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes with good results. What I have noticed is that I still have crashes sometimes, TO ME, it seems to not be the Intel driver, My gpu hangs when I use the USB. ex, hands with my Sansa mp3 player plugged in. Also upon pluggin in the player sometimes I am booted of my wireless, which is also on USB. I have 3 USB controllers, one has the SAME IRQ as my GPU chipset. SO, Im thinking my front USB is IRQ 16 with my GPU, such would explain why my Wifi(back USB) does not hang the GPU. Could someone look into this please. 00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 01) Subsystem: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Region 0: Memory at f000 (32-bit, prefetchable) [size=64M] Capabilities: access denied Kernel driver in use: agpgart-intel Kernel modules: intel-agp 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01) Subsystem: Gateway 2000 Device 2000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at e800 (32-bit, prefetchable) [size=128M] Region 1: Memory at feb8 (32-bit, non-prefetchable) [size=512K] Capabilities: access denied Kernel driver in use: i915 Kernel modules: i915 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) Subsystem: Gateway 2000 Device 2000 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 4: I/O ports at e800 [size=32] Kernel driver in use: uhci_hcd 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) Subsystem: Gateway 2000 Device 2000 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 19 Region 4: I/O ports at e880 [size=32] Kernel driver in use: uhci_hcd 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) Subsystem: Gateway 2000 Device 2000 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin C routed to IRQ 18 Region 4: I/O ports at ec00 [size=32] Kernel driver in use: uhci_hcd 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01) (prog-if 20) Subsystem: Gateway 2000 Device 2000 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin D routed to IRQ 23 Region 0: Memory at feb7fc00 (32-bit, non-prefetchable) [size=1K] Capabilities: access denied Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR+ INTx- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: d000-dfff Memory behind bridge: f650-fe9f Prefetchable memory behind bridge: de30-de3f Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR-
[Bug 656126] Re: usb boot, moved mouse to unblank screen, upowerd assert failure: *** glibc detected *** /usr/lib/upower/upowerd: double free or corruption (out): 0x00a92ec0 ***
*** This bug is a duplicate of bug 648414 *** https://bugs.launchpad.net/bugs/648414 ** Attachment added: CoreDump.gz https://bugs.launchpad.net/bugs/656126/+attachment/1676369/+files/CoreDump.gz ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/656126/+attachment/1676370/+files/Dependencies.txt ** Attachment added: Disassembly.txt https://bugs.launchpad.net/bugs/656126/+attachment/1676371/+files/Disassembly.txt ** Attachment added: ProcMaps.txt https://bugs.launchpad.net/bugs/656126/+attachment/1676372/+files/ProcMaps.txt ** Attachment added: ProcStatus.txt https://bugs.launchpad.net/bugs/656126/+attachment/1676373/+files/ProcStatus.txt ** Attachment added: Registers.txt https://bugs.launchpad.net/bugs/656126/+attachment/1676374/+files/Registers.txt ** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/656126/+attachment/1676375/+files/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/656126/+attachment/1676376/+files/ThreadStacktrace.txt ** Visibility changed to: Public -- usb boot,moved mouse to unblank screen, upowerd assert failure: *** glibc detected *** /usr/lib/upower/upowerd: double free or corruption (out): 0x00a92ec0 *** https://bugs.launchpad.net/bugs/656126 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
