[Bug 1972893] [NEW] installer failed
Public bug reported: Jammy installer failed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 Date: Tue May 10 13:51:25 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.15 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972893 Title: installer failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1972893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960658] [NEW] "The screen locker is broken and unlocking is not possible"
Public bug reported: [83212.756483] kscreenlocker_g[81781]: segfault at 44 ip 7f1091c48fe5 sp 7ffcbfebb860 error 6 in libQt5Core.so.5.15.2[7f10919ef000+30e000] [83212.756500] Code: 28 00 00 00 0f 85 bd 05 00 00 0f b6 44 24 43 48 81 c4 88 00 00 00 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 48 89 44 24 60 83 40 04 01 8b 54 24 44 48 83 c0 08 c6 44 24 43 00 48 89 44 24 [87628.204380] kscreenlocker_g[85194]: segfault at 8b18b4df ip 7ff05003ef86 sp 7ffc8b4e2de0 error 4 in libQt5Core.so.5.15.2[7ff04fde5000+30e000] [87628.204391] Code: ba 01 00 00 00 48 83 e1 f8 48 01 c8 48 89 44 24 08 48 89 c6 31 c0 f0 48 0f b1 16 0f 85 f6 05 00 00 48 8b 44 24 30 48 8b 40 08 <48> 8b 40 40 48 89 44 24 38 48 85 c0 75 4c 48 8b 7c 24 08 48 89 c6 Seems a time dependent crash. If unlocking happens shortly after locking it seems to work, however let it sit overnight and two days in a row I see the 'you can't unlock' use loginctl unlock-session 3 screen. See attached photo. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libkscreenlocker5 5.22.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Feb 11 10:55:38 2022 InstallationDate: Installed on 2020-02-12 (729 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kscreenlocker UpgradeStatus: Upgraded to impish on 2022-01-04 (38 days ago) ** Affects: kscreenlocker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "photo of lock failure screen" https://bugs.launchpad.net/bugs/1960658/+attachment/5560414/+files/20220211_104418.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960658 Title: "The screen locker is broken and unlocking is not possible" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kscreenlocker/+bug/1960658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
It looks to be 'an interesting mystery' we're chasing. This system is in production, so the results below are with the whole 'snooping engine' off as without it the whole thing dies. As such, I don't think the contents of the fdb and mdb tables mean much. The setups below are unchanged, they fail if snooping is on, work when it's off. root@noc1:~# ip -s -d link show vmbridge 6: vmbridge: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 52:54:33:bf:a8:78 brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 maxmtu 65535 bridge forward_delay 1500 hello_time 200 max_age 2000 ageing_time 3 stp_state 0 priority 21 vlan_filtering 1 vlan_protocol 802.1Q bridge_id 0015.52:54:33:bf:a8:78 designated_root 0015.52:54:33:bf:a8:78 root_port 0 root_path_cost 0 topology_change 0 topology_change_detected 0 hello_timer 0.00 tcn_timer0.00 topology_change_timer0.00 gc_timer 137.32 vlan_default_pvid 0 vlan_stats_enabled 0 vlan_stats_per_port 0 group_fwd_mask 0 group_address 01:80:c2:00:00:00 mcast_snooping 0 mcast_router 1 mcast_query_use_ifaddr 0 mcast_querier 0 mcast_hash_elasticity 16 mcast_hash_max 4096 mcast_last_member_count 2 mcast_startup_query_count 2 mcast_last_member_interval 100 mcast_membership_interval 26000 mcast_querier_interval 25500 mcast_query_interval 12500 mcast_query_response_interval 1000 mcast_startup_query_interval 3124 mcast_stats_enabled 0 mcast_igmp_version 2 mcast_mld_version 1 nf_call_iptables 0 nf_call_ip6tables 0 nf_call_arptables 0 addrgenmode none numtxqueues 1 numrxqueues 1 gso_max_size 32000 gso_max_segs 24 RX: bytes packets errors dropped missed mcast 2013504987 17838769 0 0 0 5037107 TX: bytes packets errors dropped carrier collsns 84611 0 0 0 0 The bridge itself has no address of any kind other than a mac. Here's a detail from one of many identical vm setups: ip -s -d link show dbl 16: dbl: mtu 1500 qdisc noqueue master vmbridge state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:54:00:60:c5:db brd ff:ff:ff:ff:ff:ff promiscuity 1 minmtu 68 maxmtu 65521 tun type tap pi off vnet_hdr off persist off bridge_slave state forwarding priority 32 cost 100 hairpin off guard off root_block off fastleave off learning on flood on port_id 0x800a port_no 0xa designated_port 32778 designated_cost 0 designated_bridge 0015.52:54:33:bf:a8:78 designated_root 0015.52:54:33:bf:a8:78 hold_timer 0.00 message_age_timer0.00 forward_delay_timer0.00 topology_change_ack 0 config_pending 0 proxy_arp off proxy_arp_wifi off mcast_router 1 mcast_fast_leave off mcast_flood on mcast_to_unicast off neigh_suppress off group_fwd_mask 0 group_fwd_mask_str 0x0 vlan_tunnel off isolated off addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 RX: bytes packets errors dropped missed mcast 18895018565 174327707 0 25070 0 0 TX: bytes packets errors dropped carrier collsns 30861506740 198028258 0 14270 0 There's some confidential stuff, so I've deleted repetitive vlan entries below. vlan 121 in this sandbox carries 'local lan' traffic. The bridge has an interface on that. vlan 100 is an only-in-rack server-server backbone for ceph. 122 is a public internet ingress on this mixed-use box. #bridge vlan show port vlan-id enp5s2122 PVID Egress Untagged enp4s0f0 103 105 ... 121 PVID Egress Untagged 122 133 enp4s0f1 100 PVID Egress Untagged 101 102 104 lan0noc0port 121 PVID Egress Untagged <-- this has a v4/v6 address for the server's use. ... gate 100 101 ... registry 121 PVID Egress Untagged 127 131 dbl 101 PVID Egress Untagged 121 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
P.S. The reason this is a security issue is-- there is now an address on the host that the guest also 'knows' and it sits on the bridge giving access to all the other guests on the bridge. Most admins will not 'just know' they need rules to block fe80 traffic generated by host interfaces-- because of course at least one host interface needs an fe80 address for ipv6 neighbor protocols to work. It's a really big 'soft hole'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
I need to repeat: in sysctl.d put this line in a file, then reboot, then your test setup will show the failure: net.ipv6.conf.all.autoconf = 0 Otherwise, in your test setup the tables are populated, then you delete the addresses, but the L3/4 code engaged by even a little time with the fe80:... address at least until there is a timeout in the tables (longer than you wait for your test) kills the platform. Putting the above in then rebooting will avoid that, so you will see the bug when at no time was there an fe80 address on the interface. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960242] [NEW] kernel fault on monitor wakeup, only reboot recovers.
Public bug reported: After a normal day's operations, the monitors switch off after an hour or so. Every morning since Impish, upon waking up and unlocking the system: 2 of the monitors wake, the rest remain in sleep mode. The only recourse is to do a graceful poweroff and cold boot. There is a kernel fault, as follows and in the attached file. It is 100% repeatable. [121665.686476] ceph: mds0 caps renewed [126829.470180] [ cut here ] [126829.470183] WARNING: CPU: 6 PID: 4368 at drivers/gpu/drm/ttm/ttm_bo.c:437 ttm_bo_release+0x2de/0x330 [ttm] [126829.470191] Modules linked in: ceph libceph fscache netfs xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nft_chain_nat nf_nat xfrm_user nf_conntrack xfrm_algo nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nft_compat nft_counter br_netfilter nf_tables nfnetlink vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bridge stp llc overlay lz4 lz4_compress zram snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg intel_rapl_msr snd_intel_sdw_acpi intel_rapl_common snd_hda_codec sch_fq_codel snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm snd_seq_midi edac_mce_amd snd_seq_midi_event snd_rawmidi uvcvideo msr videobuf2_vmalloc parport_pc videobuf2_memops kvm_amd videobuf2_v4l2 videobuf2_common ppdev snd_seq videodev kvm snd_seq_device lp snd_timer rapl parport eeepc_wmi wmi_bmof joydev input_leds mc k10temp ccp snd soundcore mac_hid sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor [126829.470220] zstd_compress raid6_pq libcrc32c hid_generic uas usbhid usb_storage hid amdgpu iommu_v2 gpu_sched nouveau radeon mxm_wmi i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect crct10dif_pclmul sysimgblt fb_sys_fops crc32_pclmul cec ghash_clmulni_intel rc_core mfd_aaeon aesni_intel asus_wmi crypto_simd sparse_keymap nvme video xhci_pci r8169 gpio_amdpt ahci drm cryptd realtek i2c_piix4 libahci xhci_pci_renesas nvme_core wmi gpio_generic [126829.470239] CPU: 6 PID: 4368 Comm: kwin_x11:cs0 Tainted: G OE 5.13.0-28-generic #31-Ubuntu [126829.470241] Hardware name: System manufacturer System Product Name/PRIME B450-PLUS, BIOS 3211 08/10/2021 [126829.470242] RIP: 0010:ttm_bo_release+0x2de/0x330 [ttm] [126829.470246] Code: e8 17 27 3f f0 e9 ac fd ff ff 49 8b 7e 98 b9 4c 1d 00 00 31 d2 be 01 00 00 00 e8 4d 4a 3f f0 49 8b 46 e8 eb 9d 4c 89 e0 eb 98 <0f> 0b 41 c7 86 84 00 00 00 00 00 00 00 49 8d 76 08 31 d2 4c 89 ef [126829.470247] RSP: 0018:b0df43547d28 EFLAGS: 00010202 [126829.470248] RAX: 0002 RBX: 0002 RCX: [126829.470249] RDX: 0001 RSI: 0246 RDI: 89e51b945ac0 [126829.470250] RBP: b0df43547d50 R08: 89e4529488e8 R09: 0002 [126829.470251] R10: 89e894fe4d38 R11: 89e51c2ffce8 R12: 89e51b9452b0 [126829.470251] R13: 89e8aa050c58 R14: 89e8aa050db8 R15: 89eb3bb8c480 [126829.470252] FS: 7f21ee182640() GS:89ec1e30() knlGS: [126829.470253] CS: 0010 DS: ES: CR0: 80050033 [126829.470254] CR2: 7fbf8805e7e8 CR3: 00045811c000 CR4: 00350ee0 [126829.470255] Call Trace: [126829.470256] [126829.470258] ttm_bo_put+0x30/0x50 [ttm] [126829.470262] amdgpu_bo_unref+0x1e/0x30 [amdgpu] [126829.470365] amdgpu_gem_object_free+0x34/0x50 [amdgpu] [126829.470454] drm_gem_object_free+0x1d/0x30 [drm] [126829.470470] drm_gem_dmabuf_release+0x40/0x60 [drm] [126829.470486] dma_buf_release+0x46/0xa0 [126829.470488] __dentry_kill+0x10e/0x190 [126829.470490] dentry_kill+0x52/0x1c0 [126829.470491] dput+0x12f/0x180 [126829.470492] __fput+0xf0/0x250 [126829.470494] fput+0xe/0x10 [126829.470495] task_work_run+0x6d/0xa0 [126829.470497] exit_to_user_mode_loop+0x150/0x160 [126829.470499] exit_to_user_mode_prepare+0x9f/0xb0 [126829.470500] syscall_exit_to_user_mode+0x27/0x50 [126829.470503] do_syscall_64+0x6e/0xb0 [126829.470504] ? do_syscall_64+0x6e/0xb0 [126829.470506] ? asm_sysvec_apic_timer_interrupt+0xa/0x20 [126829.470507] entry_SYSCALL_64_after_hwframe+0x44/0xae [126829.470509] RIP: 0033:0x7f21fb43e9cb [126829.470510] Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 35 a4 0f 00 f7 d8 64 89 01 48 [126829.470511] RSP: 002b:7f21ee181738 EFLAGS: 0246 ORIG_RAX: 0010 [126829.470513] RAX: RBX: 7f21ee181770 RCX: 7f21fb43e9cb [126829.470513] RDX: 7f21ee181770 RSI: 40086409 RDI: 000d [126829.470514] RBP: 40086409 R08: 55849cb1c370 R09: [126829.470515] R10: R11: 0246 R12: 55849c056508 [126829.470515] R13: 000d R14: 55849c057434 R15: 7f21ee1817a0
Re: [Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
On 2/5/22 18:59, Jay Vosburgh wrote: > Harry, > > I am attempting to reproduce the behavior you describe, but have been > unable to do so. Could you clarify some of the configuration specifics, > as follows: > > Starting with step 2, > > "2. On the host, create a bridge and vlan with two ports, each with the > chosen vlan as PVID and egress untagged. Assign those ports one each to > the guests as the interface, use e1000. Be sure to NOT autoconfigure the > host side of the bridge ports with any ip4 or ip6 address (including > fe80::), [...]" > > I have configured testbr0 with no addresses, i.e., "ip addr show": > > 15: testbr0: mtu 1500 qdisc noqueue state > UP group default qlen 1000 > link/ether 8c:dc:d4:b3:cb:f1 brd ff:ff:ff:ff:ff:ff > > and added vnet1 and vnet3 (the interfaces that connect to the VMs), to > testbr0, and removing their respective fe80: addresses. I set the bridge > vlan behavior via > > bridge vlan add dev vnet1 vid 1234 pvid untagged > bridge vlan add dev vnet3 vid 1234 pvid untagged > bridge vlan del dev vnet1 vid 1 > bridge vlan del dev vnet3 vid 1 > > then added a separate Ethernet device to the testbr0, removed its fe80: > address, and set its bridge vlan as > > bridge vlan add dev eno50 vid 1234 > bridge vlan del dev eno50 vid 1 > > Adding addresses to the interfaces within the VMs results in ping between > the two functioning (even in the face of "ip neigh flush dev enp7s0"). > > At no time does "bridge mdb" affect the behavior (it lists no entries), > and it in unnecessary to add ff02:ffxx entries as you describe in step 6 > (I presume that your mention of "fe02::ff..." is a typo for "ff02"). > > I am testing with the Ubuntu 5.11.0-46 kernel, which differs slightly from > your 5.11.0-49. From which version did you upgrade (i.e., what was the > last known working version)? I'm preparing to test with 5.11.0-50 (I am > unable to locate -49), but would also like to know if the above > description matches your configuration. > > Thanks. > These are partial, showing the relevant bits. root@noc2:~# uname -a Linux noc2.1.quietfountain.com 5.11.0-49-generic #55-Ubuntu SMP Wed Jan 12 17:36:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@noc2:~# bridge vlan show port vlan-id enp4s0f1 100 PVID Egress Untagged 101 102 104 gate 100 101 102 103 104 105 ... dbs 102 PVID Egress Untagged 121 dbl 101 PVID Egress Untagged 121 4: enp4s0f1: mtu 1500 qdisc fq_codel master vmbridge state UP group default qlen 1000 link/ether 00:15:17:5a:ea:a9 brd ff:ff:ff:ff:ff:ff ... 13: gate: mtu 1500 qdisc noqueue master vmbridge state UNKNOWN group default qlen 1000 link/ether fe:54:00:9d:61:fa brd ff:ff:ff:ff:ff:ff 15: dbs: mtu 1500 qdisc noqueue master vmbridge state UNKNOWN group default qlen 1000 link/ether fe:54:00:2a:0e:ac brd ff:ff:ff:ff:ff:ff 16: dbl: mtu 1500 qdisc noqueue master vmbridge state UNKNOWN group default qlen 1000 link/ether fe:54:00:f7:d1:8a brd ff:ff:ff:ff:ff:ff 17: fssupport: mtu 1500 qdisc noqueue master vmbridge state UNKNOWN group default qlen 1000 Without turning off snooping, there was no v6 comm between any of them, or on vm's on dbl or dbs on other similarly set up hosts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
On 2/5/22 18:59, Jay Vosburgh wrote: > Harry, > > I am attempting to reproduce the behavior you describe, but have been > unable to do so. Could you clarify some of the configuration specifics, > as follows: > > Starting with step 2, > > "2. On the host, create a bridge and vlan with two ports, each with the > chosen vlan as PVID and egress untagged. Assign those ports one each to > the guests as the interface, use e1000. Be sure to NOT autoconfigure the > host side of the bridge ports with any ip4 or ip6 address (including > fe80::), [...]" > > I have configured testbr0 with no addresses, i.e., "ip addr show": > > 15: testbr0: mtu 1500 qdisc noqueue state > UP group default qlen 1000 > link/ether 8c:dc:d4:b3:cb:f1 brd ff:ff:ff:ff:ff:ff > > and added vnet1 and vnet3 (the interfaces that connect to the VMs), to > testbr0, and removing their respective fe80: addresses. I set the bridge > vlan behavior via > > bridge vlan add dev vnet1 vid 1234 pvid untagged > bridge vlan add dev vnet3 vid 1234 pvid untagged > bridge vlan del dev vnet1 vid 1 > bridge vlan del dev vnet3 vid 1 > > then added a separate Ethernet device to the testbr0, removed its fe80: > address, and set its bridge vlan as > > bridge vlan add dev eno50 vid 1234 > bridge vlan del dev eno50 vid 1 > > Adding addresses to the interfaces within the VMs results in ping between > the two functioning (even in the face of "ip neigh flush dev enp7s0"). > > At no time does "bridge mdb" affect the behavior (it lists no entries), > and it in unnecessary to add ff02:ffxx entries as you describe in step 6 > (I presume that your mention of "fe02::ff..." is a typo for "ff02"). > > I am testing with the Ubuntu 5.11.0-46 kernel, which differs slightly from > your 5.11.0-49. From which version did you upgrade (i.e., what was the > last known working version)? I'm preparing to test with 5.11.0-50 (I am > unable to locate -49), but would also like to know if the above > description matches your configuration. > > Thanks. Also, I'd say if any of the interfaces *ever* had v6 addresses, then there would be entries in the fdb and mdb. But on these systems we have: net.ipv6.conf.all.autoconf = 0 before the interfaces are created. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573345] Re: Dual monitor loses settings after screen sleep
Still exists 2/2022. KScreen. After a sleep, it's random which monitors are detected at all. After a sleep some, but not all the monitors come back at all, and the ones that do are horizontally aligned, the stored alignment is lost. The only way to fix it I've found is to reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573345 Title: Dual monitor loses settings after screen sleep To manage notifications about this bug go to: https://bugs.launchpad.net/kscreen/+bug/1573345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1959702] Re: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb
Yup, those failures were to do with an old radeon chipset on an ancient server. On 2/1/22 17:33, Seth Arnold wrote: > Sounds good, thanks: > > [0.00] Linux version 5.11.0-49-generic (buildd@lcy02-amd64-054) > (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) > 2.36.1) #55-Ubuntu SMP Wed Jan 12 17:36:34 UTC 2022 (Ubuntu > 5.11.0-49.55-generic 5.11.22) > > btw, there were a bunch of memory allocation failures in the dmesg, in > case they weren't obvious. > > ** Attachment removed: "apport.linux-image-5.11.0-49-generic.rw5aqx7x.apport" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+attachment/5558647/+files/apport.linux-image-5.11.0-49-generic.rw5aqx7x.apport > > ** Information type changed from Private Security to Public Security > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1959702 Title: Regression: ip6 ndp broken, host bridge doesn't add vlan guest entry to mdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944720] [NEW] kde-spectacle crashes every time
Public bug reported: I have a multi-display setup, a few traditional HD monitors. Under 21.04, every time I choose 'Take a new screenshot' with the rectangular region area capture mode-- the spectacle just disappears as if it was never launched. The system resumes as if Spectacle was never attempted, there is no option to choose any region, it is as if I had just quit spectacle or had never run it in the first place. Everything operates seemingly normally. Then-- when spectacle is launched a second time -- the system goes immediately into the mode of capturing a rectangular region -- it operates as if the 'take a new screenshot' had just been pressed. After the screenshot is taken, the menu reappears and is normal. ** Affects: kde-spectacle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944720 Title: kde-spectacle crashes every time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-spectacle/+bug/1944720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930756] [NEW] regression: virtiofsd in qemu-system-common fails selinux related xattr
Public bug reported:
System call lsetfilecon in the guest fails, it worked when the host ran
Groovy.
How to repeat/test virtiofs lsetfilecon regression that breaks dpkg,
prevents upgrades/fixes.
In the guest, for example fedora:
[root@registry1 ~]# getenforce
Permissive
[root@registry1 ~]# cat lsetfilecon.c
#include
#include
#include
void perror(const char *s);
int main(int argc,char *argv[]){
int i;
i= lsetfilecon("/usr/bin/rngtest","system_u:object_r:bin_t:s0");
//i= lsetfilecon("/usr/bin/rngtest;60b9120b","system_u:object_r:bin_t:s0");
printf("ret %lx\n",i);
perror("\n");
return 0;
}
[root@registry1 ~]# gcc lsetfilecon.c -lselinux -o lsetfilecon
[root@registry1 ~]# ./lsetfilecon
ret
: Operation not permitted
[root@registry1 ~]# ls -l /usr/bin/rngtest
-rwxr-xr-x. 1 root root 21176 Apr 27 18:26 /usr/bin/rngtest
[root@registry1 ~]# uname -a
Linux registry1. 5.11.19-300.fc34.x86_64 #1 SMP Fri May 7 14:17:15 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
On the ubuntu hirsuite host:
root@noc1:/vmsystems/registry1/usr/bin# getfattr -m - -d rngtest
# file: rngtest
security.selinux="system_u:object_r:bin_t:s0"
ls -l rngtest
-rwxr-xr-x. 1 root root 21176 Apr 27 18:26 rngtest
#/usr/lib/qemu/virtiofsd --version
using FUSE kernel interface version 7.32
#uname -a
5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64
x86_64 GNU/Linux
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Tags: virtiofs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930756
Title:
regression: virtiofsd in qemu-system-common fails selinux related
xattr
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1930756/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894902] Re: 2 apparmor items missing for 'groovy'
** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894902 Title: 2 apparmor items missing for 'groovy' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1894902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886148] Re: failure to boot groovy daily
S5000PSL - usb creator fails to boot using groovy daily build 9/12, 9/13. Works normally with unetbootin. Daily build did boot perhaps a week or 10 days ago. (Installer failed & crashed when 'something else/ grub bios boot only .. no efi .. but that's another issue. 'Something else' did work when I manually created both a efi and legacy bios partition, even though the efi partition was a waste of space. (gpt partition format). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886148 Title: failure to boot groovy daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883040] Re: groovy daily won't boot anymore on some older BIOS boxes
This is still an issue 9/13/20, ubuntu mate groovy daily build. pre- uefi server won't boot w/ubuntu usb creator, works with unetbootin. Whatever the change was, it happened within the last 10 days or so. An earlier daily build did boot on that same machine without trouble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883040 Title: groovy daily won't boot anymore on some older BIOS boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1883040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883040] Re: groovy daily won't boot anymore on some older BIOS boxes
server was bare-metal S5000PSL -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883040 Title: groovy daily won't boot anymore on some older BIOS boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1883040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894902] [NEW] 2 apparmor items missing for 'groovy'
Public bug reported: need to add ~# cat /etc/apparmor.d/local/usr.sbin.ntpd /run/systemd/userdb/io.systemd.Machine wr, /etc/ssl/openssl.cnf r, otherwise you get Sep 8 16:07:44 noc4 kernel: [ 1843.949193] audit: type=1400 audit(1599599264.140:52): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/systemd/userdb/io.systemd.Machine" pid=16851 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Sep 8 16:11:22 noc4 kernel: [ 2062.263356] audit: type=1400 audit(1599599482.449:138): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/etc/ssl/openssl.cnf" pid=17639 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 ** Affects: ntpsec (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894902 Title: 2 apparmor items missing for 'groovy' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntpsec/+bug/1894902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894868] [NEW] groovy installer crashes on non-efi capable systems
Public bug reported: Attempting to install Groovy using cd image. Normal until bootloader install. The system is not EFI capable (older server, some VMs). Installer advises without EFI the system will crash, etc. Though there is a grub/bios partition, and a btrfs install proceeded normally up till the installer bootloader complaint. After choosing 'continue anyway' and being told I'd have to install a boot loader myself, the installer crashed with what you see in this report. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.9 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 Date: Tue Sep 8 10:47:39 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200907) RebootRequiredPkgs: linux-image-5.8.0-18-generic linux-base SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.9 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894868 Title: groovy installer crashes on non-efi capable systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1894868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885632] Re: Focal requires tls > mariadb rev
Otto, thanks for the repeated reminder. Kindly note upstream includes a ubuntu repo that fixes this problem. Interested people can get the answer to this problem by following this link: https://downloads.mariadb.org/mariadb/repositories/#distro=Ubuntu_release=focal --ubuntu_focal=digitalocean-sfo=10.5 As of this writing, the steps to fix this bug without waiting or relying on Ubuntu/Canonical is: sudo apt-get install software-properties-common sudo apt-key adv --fetch-keys 'https://mariadb.org/mariadb_release_signing_key.asc' sudo add-apt-repository 'deb [arch=amd64,arm64,ppc64el] http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.5/ubuntu focal main' Otto, with that you can close this report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885632 Title: Focal requires tls > mariadb rev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1885632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885632] Re: Focal requires tls > mariadb rev
Thanks Otto. It would be an appreciated add-on to the bug reporting system if your firm would add a little alert when it accepts a bug submission to a package that's not in the 'main' repository so we users get a gentle reminder we ought not expect help of the sort the 'main' packages get. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885632 Title: Focal requires tls > mariadb rev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1885632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886970] Re: should be warned if major installed package not in upgrade.
That's it? A conclusion with no reasons, no exploration of options? How about a check in the upgrade routine that makes a list of currently installed packages with no reverse dependencies, that do not appear in the new release repos, and warn the user if they consent to the upgrade those packages will either be left behind or go away? That sounds feasible, I suspect many other options would as well. I was hoping for a little more thought here, or at least a reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886970 Title: should be warned if major installed package not in upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1886970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886970] [NEW] should be warned if major installed package not in upgrade.
Public bug reported: The clear, simple pop-up graphic advising of a new long term release can lead to major upset with Ubuntu in a way that can be avoided, as follows: Just for the purpose of this wish: Let's call an installed package that provides a capability of interest to the user that's optional, that is to say not a dependency of anything, user-driven. If an installed 'user-driven' package is not available in a new long term release: it's reasonable to suppose an average user would be upset if, trusting the cheery notice of new LTS release won't do 'anything bad', their package-of-interest is mysteriously gone upon reboot. It's just a question of the extent to which Ubuntu wants to be friendly to folks who think it's too much to comprehend the zooming console screenfulls of 'lib*' and so forth being upgraded. We know some major packages (where 'major' means the user went out of their way to install it) arrive only as 'backports' for long term releases, so accepting the LTS until those arrive when the prior version is installed -- will be a loss. There are lots of potential 'right answers', I think the only wrong answer is 'do nothing'. I call this a bug because going along with the clear, obvious intention of the pop-up will in these cases leave the user worse off as their chosen optional package will be gone though you'd think that Ubuntu would have taken that into account before presenting the 'it's all ready!' notice. The case that bit me was freeipa-server, but there are many others. Just dealing with repeated notices on consoles and pop-ups making me go out of my way to turn them off seems, well, less user-friendly than the standard Ubuntu keeps elsewhere. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886970 Title: should be warned if major installed package not in upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1886970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1878973] Re: clean focal install, crash report qemu-guest-agent
I agree. No issues here these many days. On 7/6/20 9:42 AM, Łukasz Zemczak wrote: > Ok, I think it's as good as it gets, waiting any longer won't make much > difference. Thank you for the verification - releasing! > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878973 Title: clean focal install, crash report qemu-guest-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1878973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885632] [NEW] Focal requires tls > mariadb rev has. ssl dead, websites down on upgrade
Public bug reported: Mariadb 10.3 as provided by Ubuntu and shipped in LTS is compiled against YaSSL version 2.4.4, which supports a maximum tls version of 1.1 as I understand it. See: https://ubuntuforums.org/showthread.php?t=2420831 Focal minimum tls requirement is higher, tls v1.2 as discussed here: https://discourse.ubuntu.com/t/default-to-tls-v1-2-in-all-tls-libraries- in-20-04-lts/12464/3 As a result, all attempts to use ssl that worked pre-focal now hit a hard failure with such as: ERROR 2026 (HY000): SSL connection error: The TLS connection was non- properly terminated. and via libraries: Unable to open database: SSL connection error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number Upstream offers a focal repository, so hopefully this won't be a hard one to merge into standard Ubuntu, since basically without some fix SSL/TLS via mariadb is broken entirely on an LTS version -- and that for 5 years, as they say, needs a close look. I suspect there are other compatibility issues preventing it, but as 'upgrading to focal' killed several web servers -- some sort of pragmatic work-around needs doing. Until then: sudo apt-get install software-properties-common sudo apt-key adv --fetch-keys 'https://mariadb.org/mariadb_release_signing_key.asc' sudo add-apt-repository 'deb [arch=amd64,arm64,ppc64el] http://ftp.utexas.edu/mariadb/repo/10.5/ubuntu focal main' Hope this helps someone... ** Affects: mariadb-10.3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885632 Title: Focal requires tls > mariadb rev has. ssl dead, websites down on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1885632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605224] Re: at-spi-registryd.desktop not responding on shutdown
Still happening in clean focal install, mate desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605224 Title: at-spi-registryd.desktop not responding on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/1605224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884980] Re: patch so apparmor complain->enforcing
Christian, Since to test whether the fix I provided was complete you'd have to install freeipa-server to see all the bloat from apparmor, then try the fix and tweak it that would be enough given the sample error message. But, since you asked, here's a zmore /var/log/syslog.7.gz | grep appa > It's quite small and incomplete, but 796k worth should be enough for you to accept this as a real thing I hope. This log was taken while sssd was in complain mode, not enforcing. Without that ssytemd drop in pushing sssd in complain, most of the 'allowed' would be 'denied', and of course normal operations would be impossible. ** Attachment added: "forChristianEhrhardt.log" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1884980/+attachment/5387541/+files/forChristianEhrhardt.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884980 Title: patch so apparmor complain->enforcing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1884980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885236] [NEW] focal upgrade python3.8 bugs
Public bug reported: Setting up python3-cephfs (15.2.1-0ubuntu2) ... /usr/lib/python3/dist-packages/ceph_volume_client.py:358: SyntaxWarning: "is not" with a literal. Did you mean "!="? group_id = group_id if group_id is not 'None' else None /usr/lib/python3/dist-packages/ceph_volume_client.py:381: SyntaxWarning: "is" with a literal. Did you mean "=="? readonly = True if access_level is 'r' else False /usr/lib/python3/dist-packages/ceph_volume_client.py:1102: SyntaxWarning: "is" with a literal. Did you mean "=="? unwanted_access_level = 'r' if want_access_level is 'rw' else 'rw' ** Affects: ceph (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885236 Title: focal upgrade python3.8 bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1885236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885235] [NEW] python 3.8 bugs in hplip / focal upgrade
Public bug reported: /usr/share/hplip/base/utils.py:2063: SyntaxWarning: "is" with a literal. Did you mean "=="? if weburl is "" or weburl is None: /usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did you mean "=="? if log_level is 'debug': /usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: /usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a literal. Did you mean "=="? if home_dir is "": /usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": /usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": ** Affects: hplip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885235 Title: python 3.8 bugs in hplip / focal upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1885235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884980] Re: patch so apparmor complain->enforcing
Seth, Thanks for the note! I've made the change. Harry Coin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884980 Title: patch so apparmor complain->enforcing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1884980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885061] [NEW] systemd drop in needed to allow krb5.log
Public bug reported: Kindly notice https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1885024 which won't be fixed in kerberos since freeipa changes the log destination. So freeipa needs to add a systemd drop in to allow the logging. krb5-kdc.service drop in: [Service] ReadWriteDirectories= /var/log ** Affects: freeipa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885061 Title: systemd drop in needed to allow krb5.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1885061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885024] [NEW] systemd patch fixes: krb5kdc.log Read-only file system
Public bug reported: Jun 24 11:29:34 registry1 krb5kdc[1244]: Couldn't open log file /var/log/krb5kdc.log: Read-only file system can be fixed by adding ReadWriteDirectories= /var/log to the krb5-kdc.service unit ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885024 Title: systemd patch fixes: krb5kdc.log Read-only file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1885024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884980] [NEW] patch so apparmor complain->enforcing
Public bug reported: Because /var/log/syslog gets bloated with sssd apparmor related messages, I put the following in /etc/apparmor.d/local/usr.sbin.sssd then I changed sssd from 'complain' to 'enforcing' mode. I put this on a heavy sssd vm running freeipa server that also is running the gui with mate. I can't promise I found all the cases, but I don't see any 'apparmor' messages in the logs on the freeipa servers after a couple days. signal (send) peer="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_pac", /usr/sbin/sssd ixr, /usr/libexec/sssd/sssd_be ixr, /etc/krb5.conf.d/** r, /etc/krb5.conf.d/ r, /etc/krb5.conf.d r, /etc/sssd r, /etc/sssd/ r, /etc/sssd/** r, /usr/share/sssd r, /usr/share/sssd/ r, /usr/share/sssd/** r, /usr/libexec/sssd/sssd_pac ixr, /etc/gss/mech.d/ r, /etc/gss/mech.d/** r, /usr/libexec/sssd/ldap_child ixr, dbus send bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers", There are thousands of varied examples you'll see in the logs, generally along the lines of Jun 23 06:41:55 registry2 kernel: [56263.674613] audit: type=1400 audit(1592912515.202:2329356): apparmor="DENIED" operation="signal" profile="/usr/sbin/sssd" pid=1058 comm="sssd" requested_mask="send" denied_mask="send" signal=term peer="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_pac I'm not a 'deep interest' apparmor dev, no doubt the above list could be improved. HTH Harry ** Affects: sssd (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884980 Title: patch so apparmor complain->enforcing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1884980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881611] [NEW] /usr/lib/python3/dist-packages/mysqlx/expr.py:972: SyntaxWarning: "is" with a literal. Did you mean "=="?
Public bug reported:
Setting up python3-mysql.connector (8.0.15-2build1) ...
/usr/lib/python3/dist-packages/mysqlx/expr.py:972: SyntaxWarning: "is" with a
literal. Did you mean "=="?
return "({0})".format(dimension[0]) if len(dimension) is 1 else \
/usr/lib/python3/dist-packages/mysqlx/statement.py:122: SyntaxWarning: "is"
with a literal. Did you mean "=="?
return (default_schema if len(temp) is 1 else temp[0].strip(quote),
Processing triggers for libc-bin (2.31-0ubuntu9) ...
Error: Timeout was reached
** Affects: mysql-connector-python (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881611
Title:
/usr/lib/python3/dist-packages/mysqlx/expr.py:972: SyntaxWarning: "is"
with a literal. Did you mean "=="?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-connector-python/+bug/1881611/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
No issues so far. Thanks for checking. On May 20, 2020 5:30:40 PM CDT, Dan Streetman <1873...@bugs.launchpad.net> wrote: >@hcoin I assume no more segfaults with the updated pkg? can we mark >this verified for eoan? > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1873607 > >Title: > systemd segv coredump, reboot/poweroff ignored. > >Status in systemd: > Fix Released >Status in systemd package in Ubuntu: > Fix Released >Status in systemd source package in Bionic: > Fix Committed >Status in systemd source package in Eoan: > Fix Committed >Status in systemd source package in Focal: > Fix Committed >Status in systemd source package in Groovy: > Fix Released > >Bug description: > [impact] > > during systemctl daemon-reload, systemd sometimes segfaults while > serializing a service. > > [test case] > > problem is intermittent, but the upstream bug suggests a reproducer. > Also see original description. > > [regression potential] > > this adjusts serialization, so any regression would likely occur > during serialization/deserialization, e.g. at daemon-reload. > > [scope] > > This is needed for Bionic and later. > > this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41 > which is included starting in v234. The commit to fix it is > e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in > any release. > > The PR to fix this is https://github.com/systemd/systemd/pull/15546 > > [other info] > >there is an additional PR that further avoids the error, but has not >yet been accepted, and may not be accepted as it may not be necessary. > https://github.com/systemd/systemd/pull/15370 > > [original description] > > Proximate syslog: > >Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all >netns del >Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: >ListenStream= references a path below legacy directory /var/run/, >updating /var/run/dbus/system_bus_socket → /r > un/dbus/system_bus_socket; please update the unit file accordingly. >Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: >PIDFile= references a path below legacy directory /var/run/, updating >/var/run/sssd.pid → /run/sssd.pid; plea > se update the unit file accordingly. >Apr 18 16:26:56 gate2 systemd[1]: >/lib/systemd/system/oddjobd.service:6: PIDFile= references a path below >legacy directory /var/run/, updating /var/run/oddjobd.pid → >/run/oddjobd.p > id; please update the unit file accordingly. >Apr 18 16:26:56 gate2 systemd[1]: >/lib/systemd/system/fail2ban.service:12: PIDFile= references a path >below legacy directory /var/run/, updating >/var/run/fail2ban/fail2ban.pid → /r > un/fail2ban/fail2ban.pid; please update the unit file accordingly. >Apr 18 16:26:56 gate2 systemd[1]: >/lib/systemd/system/certmonger.service:6: PIDFile= references a path >below legacy directory /var/run/, updating /var/run/certmonger.pid → >/run/cer > tmonger.pid; please update the unit file accordingly. > Apr 18 16:26:56 gate2 systemd[1]: Reloading. >Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 >ip 55946ed0d6f0 sp 7fff8409d210 error 4 in >systemd[55946ecb4000+ae000] >Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 >ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 >17 66 2e 0f 1f 84 00 00 00 00 00 <48 > > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d >Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl >daemon-reload >Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl >enable rssmonitor.service > Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled >Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output >lines suppressed due to ratelimiting >Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid >2034. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: systemd 242-7ubuntu3.7 > ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 > Uname: Linux 5.3.0-46-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.8 > Architecture: amd64 > Date: Sat Apr 18 18:09:06 2020 > InstallationDate: Installed on 2019-11-01 (169 days ago) >InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 >(20191017) > Lsusb: > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > MachineType: QEMU Standard PC (i440FX + PIIX, 1996) > ProcEnviron: > SHELL=/bin/bash > LANG=en_US.UTF-8 > TERM=xterm-256color > XDG_RUNTIME_DIR= > PATH=(custom, no user) >ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic >root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ >quiet
[Bug 1879083] Re: default sssd.conf after ipa-client-install crashes sssd
With the line not commented, upon each and every startup in all cases one sees this: May 19 11:37:25 email1 systemd[1]: Starting SSSD NSS Service responder socket. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72216]: (Tue May 19 11:37:12:251510 2020) [sssd] [main] (0x0010): Misconfiguration found for the nss responder. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72216]: The nss responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72216]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the nss's socket by calling: May 19 11:37:25 email1 sssd[pac]: Starting up May 19 11:37:25 email1 systemd[1]: Starting SSSD PAM Service responder private socket. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72216]: "systemctl disable sssd-nss.socket" May 19 11:37:25 email1 sssd_check_socket_activated_responders[72218]: (Tue May 19 11:37:12:022884 2020) [sssd] [main] (0x0010): Misconfiguration found for the pam responder. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72218]: The pam responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72218]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the pam's socket by calling: May 19 11:37:25 email1 sssd[ssh]: Starting up May 19 11:37:25 email1 systemd[1]: sssd-pam-priv.socket: Control process exited, code=exited, status=17/n/a May 19 11:37:25 email1 sssd_check_socket_activated_responders[72218]: "systemctl disable sssd-pam.socket" May 19 11:37:25 email1 sssd[pam]: Starting up May 19 11:37:25 email1 systemd[1]: sssd-pam-priv.socket: Failed with result 'exit-code'. May 19 11:37:25 email1 sssd[sudo]: Starting up May 19 11:37:25 email1 systemd[1]: Failed to listen on SSSD PAM Service responder private socket. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72224]: (Tue May 19 11:37:13:424695 2020) [sssd] [main] (0x0010): Misconfiguration found for the sudo responder. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72224]: The sudo responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72224]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the sudo's socket by calling: May 19 11:37:25 email1 systemd[1]: Dependency failed for SSSD PAM Service responder socket. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72224]: "systemctl disable sssd-sudo.socket" May 19 11:37:25 email1 systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start failed with result 'dependency'. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72221]: (Tue May 19 11:37:13:671260 2020) [sssd] [main] (0x0010): Misconfiguration found for the ssh responder. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72221]: The ssh responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf. May 19 11:37:25 email1 sssd_check_socket_activated_responders[72221]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the ssh's socket by calling: May 19 11:37:25 email1 systemd[1]: sssd-nss.socket: Control process exited, code=exited, status=17/n/a May 19 11:37:25 email1 sssd_check_socket_activated_responders[72221]: "systemctl disable sssd-ssh.socket" May 19 11:37:25 email1 systemd[1]: sssd-nss.socket: Failed with result 'exit-code'. May 19 11:37:25 email1 sssd[nss]: Starting up With the line commented, one sees: May 19 11:41:05 email1 systemd[1]: Starting System Security Services Daemon... May 19 11:41:07 email1 sssd: Starting up May 19 11:41:07 email1 kernel: [270731.176590] kauditd_printk_skb: 23 callbacks suppressed May 19 11:41:07 email1 kernel: [270731.176594] audit: type=1400 audit(1589906467.911:65972): apparmor="ALLOWED" operation="exec" profile="/usr/sbin/sssd" name="/usr/libexec/sssd/sssd_be" pid=72354 comm="sssd" requested_mask="x" denied_mask="x" fsuid=0 ouid=0 target="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_be" May 19 11:41:07 email1 kernel: [270731.178959] audit: type=1400 audit(1589906467.911:65973): apparmor="ALLOWED" operation="file_mmap" profile="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_be" name="/usr/libexec/sssd/sssd_be" pid=72354 comm="sssd_be" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 May 19 11:41:07 email1 kernel: [270731.179565] audit: type=1400 audit(1589906467.911:65974): apparmor="ALLOWED" operation="file_mmap" profile="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_be"
[Bug 1879083] [NEW] default sssd.conf after ipa-client-install crashes sssd
Public bug reported: Notice ipa-client-install creates /etc/sssd/sssd.conf but changes in the sssd process's socket approach calls for that file to change /etc/sssd.conf from ... [sssd] services = nss, pam, ssh, sud ... to [sssd] #services = nss, pam, ssh, sud otherwise the sssd service either won't start or complains. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: freeipa-client 4.8.6-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 16 12:51:21 2020 InstallationDate: Installed on 2020-05-13 (2 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: freeipa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: freeipa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879083 Title: default sssd.conf after ipa-client-install crashes sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1879083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878994] Re: python3-yubico/focal: "is" with a literal. Did you mean "=="?
python3-yubico specifically, not python-yubico ** Package changed: ubuntu => python-yubico (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878994 Title: python3-yubico/focal: "is" with a literal. Did you mean "=="? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-yubico/+bug/1878994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878994] [NEW] python3-yubico/focal: "is" with a literal. Did you mean "=="?
Public bug reported: Setting up python3-yubico (1.3.3-0.3) ... /usr/lib/python3/dist-packages/yubico/yubikey_config.py:478: SyntaxWarning: "is" with a literal. Did you mean "=="? if slot is 1: /usr/lib/python3/dist-packages/yubico/yubikey_config.py:483: SyntaxWarning: "is" with a literal. Did you mean "=="? elif slot is 2: /usr/lib/python3/dist-packages/yubico/yubikey_usb_hid.py:288: SyntaxWarning: "is" with a literal. Did you mean "=="? if mode is 'nand': /usr/lib/python3/dist-packages/yubico/yubikey_usb_hid.py:294: SyntaxWarning: "is" with a literal. Did you mean "=="? elif mode is 'and': /usr/lib/python3/dist-packages/yubico/yubikey_usb_hid.py:306: SyntaxWarning: "is" with a literal. Did you mean "=="? if mode is 'nand': ** Affects: python-yubico (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878994 Title: python3-yubico/focal: "is" with a literal. Did you mean "=="? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-yubico/+bug/1878994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1878985] Re: focal/python3-netaddr : SyntaxWarning: "is not" with a literal
While dropping python-netaddr may remove a 2.0 issue, notice the bug report was for python3-netaddr. The 3 bit is important and doesn't fix this bug. On 5/15/20 3:12 PM, Kai Kasurinen wrote: > python-netaddr (0.7.19-4) unstable; urgency=medium > >* Drop python2 support; Closes: #937942 >* debian/patches/PR200.patch > - address SyntaxWarning revealed by python3.8; Closes: #950787 > > > ** Package changed: ceph (Ubuntu) => python-netaddr (Ubuntu) > > ** Bug watch added: Debian Bug tracker #950787 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950787 > > ** Also affects: python-netaddr (Debian) via > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950787 > Importance: Unknown > Status: Unknown > > ** Changed in: python-netaddr (Ubuntu) > Status: New => Fix Released > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878985 Title: focal/python3-netaddr : SyntaxWarning: "is not" with a literal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1878985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878985] [NEW] focal/python3-netaddr : SyntaxWarning: "is not" with a literal
Public bug reported: Setting up python3-netaddr (0.7.19-3) ... /usr/lib/python3/dist-packages/netaddr/strategy/__init__.py:189: SyntaxWarning: "is not" with a literal. Did you mean "!="? if word_sep is not '': 'is' and == are not the same, tests will fail that succeeded on some x86 cpython platforms for other than 8 bit literals. These bugs are picked up on python3.8, included with focal, not seen on 3.7/eoan. ** Affects: python-netaddr (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: python-netaddr (Debian) Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878985 Title: focal/python3-netaddr : SyntaxWarning: "is not" with a literal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1878985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1878973] Re: clean focal install, crash report qemu-guest-agent
Segfaults attracted to me? That's possible. Or, I'm the only ubuntu user that actually reports bugs. It's lonely out here. More seriously, I think there's a problem with the apport system more generally. What's supposed to happen after a crash is a window pops up upon log-in, offering to send the report. That happens. I click 'yes'. Then after some grinding and a couple extra files created in /var/crash ... nothing. What's supposed to happen is firefox pops up and offers the usual process with all the attachments. What actually happens is nothing. I go run ubuntu-bug manually, file the stuff, attach the crash report manually. The only clue I have to offer is: At install time, I do NOT install the restricted third party options, and I go for the 'minimal install'. As opposed to all the desktop utility stuff. I'm guessing there's something taken out of the minimal install that apport needs to launch the browser. But it's sort of confidence sapping, to see accumulated items in /var/crash, to be asked upon each reboot to file a report, then agree, then have it... simply just nothing. On 5/15/20 2:31 PM, Dan Streetman wrote: > @hcoin are segfaults attracted to you somehow? ;-) at least this > doesn't *seem* to be related to bug 1873607. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878973 Title: clean focal install, crash report qemu-guest-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1878973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878973] Re: clean focal install, crash report qemu-guest-agent
crash report. I suppose there ought to be another crash report/bug report about how this crash report didn't get auto-uploaded upon detection as well. ** Attachment added: "_usr_sbin_qemu-ga.0.crash" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1878973/+attachment/5372270/+files/_usr_sbin_qemu-ga.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878973 Title: clean focal install, crash report qemu-guest-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1878973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878973] [NEW] clean focal install, crash report qemu-guest-agent
Public bug reported: Completely new/fresh focal / mate install. Crash during initial apt install of many packages after first log-in, including qemu-guest-agent. No other important load other than apt running. OS running in a vm as a guest (obviously...) No idea what caused it. Including crash report. VM was 2 penryn class cpus with 3G ram. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu-guest-agent 1:4.2-3ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri May 15 13:20:02 2020 InstallationDate: Installed on 2020-05-13 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878973 Title: clean focal install, crash report qemu-guest-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1878973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878939] Re: python3-cephfs focal 'syntax warning' is/literal
Good detail here on why this can go horribly wrong if ignored: https://adamj.eu/tech/2020/01/21/why-does-python-3-8-syntaxwarning-for-is-literal/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878939 Title: python3-cephfs focal 'syntax warning' is/literal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1878939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878939] [NEW] python3-cephfs focal 'syntax warning' is/literal
Public bug reported: During apt install from an otherwise blank focal/mate: setting up python3-cephfs (15.2.1-0ubuntu2) ... /usr/lib/python3/dist-packages/ceph_volume_client.py:358: SyntaxWarning: "is not" with a literal. Did you mean "!="? group_id = group_id if group_id is not 'None' else None /usr/lib/python3/dist-packages/ceph_volume_client.py:381: SyntaxWarning: "is" with a literal. Did you mean "=="? readonly = True if access_level is 'r' else False /usr/lib/python3/dist-packages/ceph_volume_client.py:1102: SyntaxWarning: "is" with a literal. Did you mean "=="? ... The compiler now produces a SyntaxWarning when identity checks (is and is not) are used with certain types of literals (e.g. strings, numbers). These can often work by accident in CPython, but are not guaranteed by the language spec. The warning advises users to use equality tests (== and !=) instead. (Contributed by Serhiy Storchaka in bpo-34850.) ** Affects: ceph (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878939 Title: python3-cephfs focal 'syntax warning' is/literal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1878939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
Trying it now on 1 of 4 previously affected systems. Accepted all 'proposed' items, including changes to libvirt. Will advise. On 5/14/20 3:19 PM, Brian Murray wrote: > Hello Harry, or anyone else affected, > > Accepted systemd into eoan-proposed. The package will build now and be > available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.9 > in a few hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed. Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested, what testing has been > performed on the package and change the tag from verification-needed- > eoan to verification-done-eoan. If it does not fix the bug for you, > please add a comment stating that, and change the tag to verification- > failed-eoan. In either case, without details of your testing we will not > be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance for helping! > > N.B. The updated package will be released to -updates after the bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > ** Changed in: systemd (Ubuntu Eoan) > Status: In Progress => Fix Committed > > ** Tags added: verification-needed-eoan > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1873607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
Still on eoan. Staying with Ubuntu depends on freeipa support. Presently only the freeipa client is supported past eoan, so the future is unclear. Can the fix be backported? On 5/13/20 3:03 PM, Dan Streetman wrote: > @hcoin are you still on Eoan or have you moved up to Focal yet? If > you're on Focal, could you test the version from -proposed? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1873607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
And again: root@noc1:~# Broadcast message from systemd-journ...@noc1.1.quietfountain.com (Tue 2020-04-28 12:32:15 CDT): systemd[1]: Caught , dumped core as pid 25084. Broadcast message from systemd-journ...@noc1.1.quietfountain.com (Tue 2020-04-28 12:32:15 CDT): systemd[1]: Freezing execution. root@noc1:~# from the syslog: Apr 28 12:31:46 noc1 rssmonitor.py[18369]: rssmain: Running: systemctl daemon-reload Apr 28 12:31:46 noc1 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Apr 28 12:31:46 noc1 systemd[1]: /lib/systemd/system/virtlockd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-sock → /run/libvirt/virtlockd-sock; please update the unit file accordingly. Apr 28 12:31:46 noc1 systemd[1]: /lib/systemd/system/virtlockd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-admin-sock → /run/libvirt/virtlockd-admin-sock; please update the unit file accordingly. Apr 28 12:31:46 noc1 systemd[1]: /lib/systemd/system/virtlogd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-sock → /run/libvirt/virtlogd-sock; please update the unit file accordingly. Apr 28 12:31:46 noc1 systemd[1]: /lib/systemd/system/virtlogd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-admin-sock → /run/libvirt/virtlogd-admin-sock; please update the unit file accordingly. Apr 28 12:31:46 noc1 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 28 12:31:46 noc1 systemd[1]: Reloading. Apr 28 12:31:46 noc1 kernel: [37890.433153] systemd[1]: segfault at 50 ip 55c2dd32d6f0 sp 7ffef173c7b0 error 4 in systemd[55c2dd2d4000+ae000] Apr 28 12:31:46 noc1 kernel: [37890.433172] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48> 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 28 12:31:47 noc1 rssmonitor.py[18369]: rssmain: Ran OK: systemctl daemon-reload The last entry means the systemctl daemon-reload command returned a normal 0 exit code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
Just tried it three times, all normal, nothing in the logs except a few netfilter reports of correctly dropped packets. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873607] [NEW] systemd segv coredump, reboot/poweroff ignored.
Public bug reported: Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-cosmic dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-cosmic:cvnQEMU:ct1:cvrpc-i440fx-cosmic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-cosmic dmi.sys.vendor: QEMU mtime.conffile..etc.systemd.resolved.conf: 2020-04-18T10:41:34.662328 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
crash log ** Attachment added: "_usr_lib_systemd_systemd.0.crash" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+attachment/5356610/+files/_usr_lib_systemd_systemd.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
This has been happening perhaps 3 times every 7 days, no obvious cause I can see. The system is a virtual machine that's just a router. No user activity, nobody logged in to the mate gui. Wish I had more to offer by way of a clue but that's it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854129] Re: regression: recent eoan patch killed ceph osd pool create
Yes, the upstream patches appear to have resolved this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854129 Title: regression: recent eoan patch killed ceph osd pool create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1854129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868157] Re: Regression: ceph dashboard upgrade crashes totally w/SSL
Yes, the upstream patches appear to have resolved this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868157 Title: Regression: ceph dashboard upgrade crashes totally w/SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1868157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871254] [NEW] install fails: 'trying to overwrite '/etc/php'
Public bug reported: apt install php-imagick fails complaining about overwriting /etc/php. This is the work-around: dpkg -i --force-overwrite ./php-php-imagick_3.4.3~rc2-2ubuntu7_amd64.deb dpkg: error: cannot access archive './php-php-imagick_3.4.3~rc2-2ubuntu7_amd64.deb': No such file or directory root@www1:~# dpkg -i --force-overwrite ./php-imagick_3.4.3~rc2-2ubuntu7_amd64.deb (Reading database ... 302485 files and directories currently installed.) Preparing to unpack .../php-imagick_3.4.3~rc2-2ubuntu7_amd64.deb ... Unpacking php-imagick (3.4.3~rc2-2ubuntu7) ... dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-common 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-gd 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-curl 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-ldap 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-zip 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-opcache 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-cli 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-xml 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-mysql 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-bz2 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-readline 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-json 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-fpm 7.3.11-0ubuntu0.19.10.3 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/etc/php', which is also in package php7.3-mbstring 7.3.11-0ubuntu0.19.10.3 ** Affects: php-imagick (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871254 Title: install fails: 'trying to overwrite '/etc/php' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-imagick/+bug/1871254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868157] Re: Regression: ceph dashboard upgrade crashes totally w/SSL
This looks to be relevant, upstream: https://tracker.ceph.com/issues/38378 ** Bug watch added: tracker.ceph.com/issues #38378 http://tracker.ceph.com/issues/38378 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868157 Title: Regression: ceph dashboard upgrade crashes totally w/SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1868157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868157] Re: Regression: ceph dashboard upgrade crashes totally w/SSL
James, As you'll note by the upgrade log below, your thought above that the dashboard was not changed needs a second look. Notice 2020-03-17 16:54:39, the dashboard module was in fact changed, and it broke SSL. Does Canonical have a working ceph cluster anywhere that uses ssl on the dashboard? It has got to be broken as well. root@nocsupport2:~# cd /var/log root@nocsupport2:/var/log# more apt/history.log Start-Date: 2020-03-03 06:06:34 Commandline: /usr/bin/unattended-upgrade Upgrade: libarchive13:amd64 (3.4.0-1, 3.4.0-1ubuntu0.1) End-Date: 2020-03-03 06:07:01 Start-Date: 2020-03-04 02:01:38 Commandline: apt-get -qy upgrade Upgrade: libegl-mesa0:amd64 (19.2.8-0ubuntu0~19.10.2, 19.2.8-0ubuntu0~19.10.3), libglapi-mesa:amd64 (19.2.8-0ubuntu0~19.10.2, 19.2.8-0ubuntu0~19.10.3), libxatracker2:amd64 (19.2.8- 0ubuntu0~19.10.2, 19.2.8-0ubuntu0~19.10.3), libegl1-mesa:amd64 (19.2.8-0ubuntu0~19.10.2, 19.2.8-0ubuntu0~19.10.3), libgbm1:amd64 (19.2.8-0ubuntu0~19.10.2, 19.2.8-0ubuntu0~19.10.3), apport:amd64 (2.20.11-0ubuntu8.4, 2.20.11-0ubuntu8.5), python3-apport:amd64 (2.20.11-0ubuntu8.4, 2.20.11-0ubuntu8.5), libgl1-mesa-dri:amd64 (19.2.8-0ubuntu0~19.10.2, 19.2.8-0ubunt u0~19.10.3), libgl1-mesa-glx:amd64 (19.2.8-0ubuntu0~19.10.2, 19.2.8-0ubuntu0~19.10.3), apport-gtk:amd64 (2.20.11-0ubuntu8.4, 2.20.11-0ubuntu8.5), mesa-vdpau-drivers:amd64 (19.2.8-0 ubuntu0~19.10.2, 19.2.8-0ubuntu0~19.10.3), mesa-vulkan-drivers:amd64 (19.2.8-0ubuntu0~19.10.2, 19.2.8-0ubuntu0~19.10.3), python3-problem-report:amd64 (2.20.11-0ubuntu8.4, 2.20.11-0 ubuntu8.5), mesa-va-drivers:amd64 (19.2.8-0ubuntu0~19.10.2, 19.2.8-0ubuntu0~19.10.3), libglx-mesa0:amd64 (19.2.8-0ubuntu0~19.10.2, 19.2.8-0ubuntu0~19.10.3) End-Date: 2020-03-04 02:04:41 Start-Date: 2020-03-10 02:05:06 Commandline: apt-get -qy upgrade Upgrade: fdisk:amd64 (2.34-0.1ubuntu2.2, 2.34-0.1ubuntu2.3), libreoffice-style-breeze:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libreoffice-math:amd64 (1:6.3.4-0u buntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), uuid-runtime:amd64 (2.34-0.1ubuntu2.2, 2.34-0.1ubuntu2.3), libfdisk1:amd64 (2.34-0.1ubuntu2.2, 2.34-0.1ubuntu2.3), libreoffice-gtk3:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libreoffice-core:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libmount1:amd64 (2.34-0.1ubuntu2.2, 2.34-0.1ubun tu2.3), util-linux:amd64 (2.34-0.1ubuntu2.2, 2.34-0.1ubuntu2.3), python3-uno:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libreoffice-qt5:amd64 (1:6.3.4-0ubuntu0.19. 10.1, 1:6.3.5-0ubuntu0.19.10.1), mount:amd64 (2.34-0.1ubuntu2.2, 2.34-0.1ubuntu2.3), libreoffice-base-core:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libreoffice-o gltrans:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libblkid1:amd64 (2.34-0.1ubuntu2.2, 2.34-0.1ubuntu2.3), libreoffice-impress:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6 .3.5-0ubuntu0.19.10.1), libreoffice-style-elementary:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libreoffice-help-common:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0u buntu0.19.10.1), libuuid1:amd64 (2.34-0.1ubuntu2.2, 2.34-0.1ubuntu2.3), libreoffice-style-colibre:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), ure:amd64 (6.3.4-0ubun tu0.19.10.1, 6.3.5-0ubuntu0.19.10.1), libreoffice-writer:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libreoffice-common:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ub untu0.19.10.1), libreoffice-kde5:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libsmartcols1:amd64 (2.34-0.1ubuntu2.2, 2.34-0.1ubuntu2.3), rfkill:amd64 (2.34-0.1ubunt u2.2, 2.34-0.1ubuntu2.3), quassel:amd64 (1:0.13.1-1ubuntu1, 1:0.13.1-1ubuntu1.19.10.1), bsdutils:amd64 (1:2.34-0.1ubuntu2.2, 1:2.34-0.1ubuntu2.3), quassel-data:amd64 (1:0.13.1-1ubu ntu1, 1:0.13.1-1ubuntu1.19.10.1), fonts-opensymbol:amd64 (2:102.11+LibO6.3.4-0ubuntu0.19.10.1, 2:102.11+LibO6.3.5-0ubuntu0.19.10.1), libreoffice-pdfimport:amd64 (1:6.3.4-0ubuntu0.1 9.10.1, 1:6.3.5-0ubuntu0.19.10.1), uno-libs3:amd64 (6.3.4-0ubuntu0.19.10.1, 6.3.5-0ubuntu0.19.10.1), libreoffice-style-tango:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10 .1), libreoffice-help-en-us:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libreoffice-gnome:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libreoffice-ca lc:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libreoffice-draw:amd64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1), libreoffice-avmedia-backend-gstreamer:am d64 (1:6.3.4-0ubuntu0.19.10.1, 1:6.3.5-0ubuntu0.19.10.1) End-Date: 2020-03-10 02:17:21 Start-Date: 2020-03-11 02:02:12 Commandline: apt-get -qy upgrade Upgrade: libmpx2:amd64 (8.3.0-23ubuntu2, 8.3.0-26ubuntu1~19.10), cpp-8:amd64 (8.3.0-23ubuntu2, 8.3.0-26ubuntu1~19.10), gcc-8-base:amd64 (8.3.0-23ubuntu2, 8.3.0-26ubuntu1~19.10), li bsqlite3-0:amd64 (3.29.0-2ubuntu0.1, 3.29.0-2ubuntu0.2), libgcc-8-dev:amd64 (8.3.0-23ubuntu2,
[Bug 1868157] Re: Regression: ceph dashboard upgrade crashes totally w/SSL
Just vanilla eoan on a vm with only the ceph subsystem loaded. No osds on that vm. Are you saying you have a working dashboard that uses ssl? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868157 Title: Regression: ceph dashboard upgrade crashes totally w/SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1868157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868157] [NEW] Regression: ceph dashboard upgrade crashes totally w/SSL
Public bug reported:
After the latest upgrade to ceph, the previously normal and well working
dashboard crashes on load. There were no configuration changes, just
the update. The dashboard is protected by an SSL cert that is valid.
The only change was the upgrade. Was this tested by anyone before it
was distributed? The crash was immediate. 100% reproducible.
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:04] ENGINE Bus
STARTING
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: CherryPy Checker:
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: The Application mounted at '' has
an empty config.
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:04] ENGINE
Started monitor thread '_TimeoutMonitor'.
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:04] ENGINE
Serving on https://:::8443
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:04] ENGINE Bus
STARTED
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:04] ENGINE
Error in HTTPServer.tick
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: Traceback (most recent call last):
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: File
"/usr/lib/python3/dist-packages/cherrypy/wsgiserver/__init__.py", line 2021, in
start
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: self.tick()
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: File
"/usr/lib/python3/dist-packages/cherrypy/wsgiserver/__init__.py", line 2090, in
tick
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: s, ssl_env =
self.ssl_adapter.wrap(s)
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: File
"/usr/lib/python3/dist-packages/cherrypy/wsgiserver/ssl_builtin.py", line 67,
in wrap
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: server_side=True)
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: File
"/usr/lib/python3.7/ssl.py", line 423, in wrap_socket
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: session=session
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: File
"/usr/lib/python3.7/ssl.py", line 870, in _create
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: self.do_handshake()
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: File
"/usr/lib/python3.7/ssl.py", line 1139, in do_handshake
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: self._sslobj.do_handshake()
Mar 19 00:05:04 nocsupport2 ceph-mgr[19871]: OSError: [Errno 0] Error
Mar 19 00:05:26 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:26] ENGINE Bus
STOPPING
Mar 19 00:05:26 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:26] ENGINE HTTP
Server cherrypy._cpwsgi_server.CPWSGIServer(('::', 8443)) shut down
Mar 19 00:05:26 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:26] ENGINE
Stopped thread '_TimeoutMonitor'.
Mar 19 00:05:26 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:26] ENGINE Bus
STOPPED
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: 2020-03-19 00:05:43.041
7f671ed1d700 -1 client.0 error registering admin socket command: (17) File
exists
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: message repeated 4 times: [
2020-03-19 00:05:43.041 7f671ed1d700 -1 client.0 error registering admin socket
command: (17) File exists]
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:43] ENGINE Bus
STARTING
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:43] ENGINE
Started monitor thread '_TimeoutMonitor'.
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:43] ENGINE
Serving on https://:::8443
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:43] ENGINE Bus
STARTED
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: [19/Mar/2020:00:05:43] ENGINE
Error in HTTPServer.tick
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: Traceback (most recent call last):
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: File
"/usr/lib/python3/dist-packages/cherrypy/wsgiserver/__init__.py", line 2021, in
start
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: self.tick()
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: File
"/usr/lib/python3/dist-packages/cherrypy/wsgiserver/__init__.py", line 2090, in
tick
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: s, ssl_env =
self.ssl_adapter.wrap(s)
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: File
"/usr/lib/python3/dist-packages/cherrypy/wsgiserver/ssl_builtin.py", line 67,
in wrap
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: server_side=True)
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: File
"/usr/lib/python3.7/ssl.py", line 423, in wrap_socket
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: session=session
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: File
"/usr/lib/python3.7/ssl.py", line 870, in _create
Mar 19 00:05:43 nocsupport2 ceph-mgr[19871]: self.do_handshake()
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ceph 14.2.4-0ubuntu0.19.10.2
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Mar 19 13:47:34 2020
InstallationDate: Installed on 2018-11-12
Re: [Bug 1848950] Re: pg not [deep] scrubbed since 0.000000 -- w/fix
Thanks Dan! On 2/13/20 1:24 PM, Dan Hill wrote: > pr#28869 fixed upstream in 14.2.3. This version is in the eoan-updates > and focal pockets. > > For UCA, both train-proposed and ussuri-proposed have this fixed, but these > have not yet landed: > ceph | 14.2.2-0ubuntu3~cloud0 | train | bionic-updates > | source > ceph | 14.2.4-0ubuntu0.19.10.1~cloud0 | train-proposed | bionic-proposed > | source > ceph | 14.2.2-0ubuntu3~cloud0 | ussuri | bionic-updates > | source > ceph | 14.2.5-3ubuntu4~cloud0 | ussuri-proposed | bionic-proposed > | source > > > ** Also affects: ceph (Ubuntu Focal) > Importance: Undecided > Status: New > > ** Also affects: ceph (Ubuntu Xenial) > Importance: Undecided > Status: New > > ** Also affects: ceph (Ubuntu Bionic) > Importance: Undecided > Status: New > > ** Also affects: ceph (Ubuntu Eoan) > Importance: Undecided > Status: New > > ** Changed in: ceph (Ubuntu Xenial) > Status: New => Won't Fix > > ** Changed in: ceph (Ubuntu Bionic) > Status: New => Won't Fix > > ** Changed in: ceph (Ubuntu Eoan) > Status: New => Fix Released > > ** Changed in: ceph (Ubuntu Focal) > Status: New => Fix Released > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848950 Title: pg not [deep] scrubbed since 0.00 -- w/fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1848950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1858673] Re: package missing dependencies
Steps to reproduce: Install the package. Run the program. Notice it fails either silently or with a default obscure error message. Browse the program which is a shell script. Notice it runs several programs as sub programs. Notice those programs are not dependencies of the package. See the above list as to which programs those are. Include those programs as dependencies of this package, then close this bug report. Thanks! On 1/8/20 3:57 AM, Faustin wrote: > Hi Harry, > Thanks for your report! > > Can you please explain me the steps to reproduce the issue you are > facing? > >> Without them, this package aborts without any indication as to why. > I am not sure that I understand what you mean here. Are you speaking of a > command that aborts silently? > >> Also, mariadb-server has a SST backup option among others that depends > on mariadb-backup. When this option is enabled mariadb's systemd call > just hangs then fails but without indication as to what's missing. > > Again, it would help me to know what is the exact error that you have > because I can't find any relevant information in the logs that you > provided... > > Regards, > Faustin > > ** Changed in: mariadb-10.3 (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858673 Title: package missing dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1858673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858673] [NEW] package missing dependencies
Public bug reported: Notice the script that produces the backup relies on pv, socat, sockstat and netcat.openbsd among other packages. These are not dependencies of mariadb-backup, but should be. Without them, this package aborts without any indication as to why. Also, mariadb-server has a SST backup option among others that depends on mariadb-backup. When this option is enabled mariadb's systemd call just hangs then fails but without indication as to what's missing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mariadb-backup 1:10.3.20-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Tue Jan 7 11:51:47 2020 InstallationDate: Installed on 2019-11-01 (66 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Logs.var.log.daemon.log: MySQLVarLibDirListing: ['grastate.dat', 'galera.cache', 'gvwstate.dat', 'ibdata1', 'mysql', 'aria_log.0001', 'aria_log_control', 'xtrabackup_galera_info', 'ib_buffer_pool', 'xtrabackup_info', 'ib_logfile1', 'ib_logfile0', 'ibtmp1', 'tc.log', 'multi-master.info', 'performance_schema', 'mysql_upgrade_info'] ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mariadb-10.3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mariadb-10.3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858673 Title: package missing dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1858673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858673] Re: package missing dependencies
The affected .deb file is mariadb-backup n.b. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858673 Title: package missing dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1858673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1627371] Re: Timing problems with FreeIPA installation
Timo, You might take a look at /etc/sssd/sssd.conf Consider changing services = ifp #services = nss, pam, ifp, ssh, sudo The reason is that unless you change this, systemctl is-system-running reports degraded instead of running, with messages akin to Dec 9 17:59:25 registry1 sssd_check_socket_activated_responders[1672]: (Mon Dec 9 17:59:25:697972 2019) [sssd] [main] (0x0010): Misconfiguration found for the pam responder. Dec 9 17:59:25 registry1 sssd_check_socket_activated_responders[1672]: The pam responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf. Dec 9 17:59:25 registry1 sssd_check_socket_activated_responders[1672]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the pam's socket by calling: Dec 9 17:59:25 registry1 sssd_check_socket_activated_responders[1672]: "systemctl disable sssd-pam.socket" On 11/28/19 8:17 AM, Timo Aaltonen wrote: > I'm just going to assume things are all fixed with 19.10 and up, which > have freeipa 4.8.x and dogtag 10.7.3, and they both depend on systemd > features now which should resolve all race conditions > > ** Changed in: freeipa (Ubuntu) > Status: Confirmed => Fix Released > > ** Changed in: dogtag-pki (Ubuntu) > Status: Confirmed => Fix Released > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627371 Title: Timing problems with FreeIPA installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dogtag-pki/+bug/1627371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853863] Re: freeipa replica crashes near end of basic install
Using the ppa, the upgrade to the primary server was successful. Then the replica install was successful, other than, at the end: ... Restarting named Updating DNS system records DNS query for registry1.1.quietfountain.com. 1 failed: All nameservers failed to answer the query registry1.1.quietfountain.com. IN A: Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered SERVFAIL; Server ::1 UDP port 53 answered SERVFAIL DNS query for registry1.1.quietfountain.com. 1 failed: All nameservers failed to answer the query registry1.1.quietfountain.com. IN A: Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered SERVFAIL; Server 127.0.0.1 UDP port 53 answered SERVFAIL unable to resolve host name registry1.1.quietfountain.com. to IP address, ipa-ca DNS record will be incomplete Global DNS configuration in LDAP server is empty You can use 'dnsconfig-mod' command to set global DNS options that would override settings in local named.conf files DNS query for registry1.1.quietfountain.com. 1 failed: All nameservers failed to answer the query registry1.1.quietfountain.com. IN A: Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered SERVFAIL; Server 127.0.0.1 UDP port 53 answered SERVFAIL DNS query for registry1.1.quietfountain.com. 1 failed: All nameservers failed to answer the query registry1.1.quietfountain.com. IN A: Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered SERVFAIL; Server 127.0.0.1 UDP port 53 answered SERVFAIL unable to resolve host name registry1.1.quietfountain.com. to IP address, ipa-ca DNS record will be incomplete WARNING: The CA service is only installed on one server (registry1.1.quietfountain.com). It is strongly recommended to install it on another server. Run ipa-ca-install(1) on another master to accomplish this. The ipa-replica-install command was successful ... The following ipa-ca-install proceeded without error. I suggest that as ubuntu has embraced ceph, it should consider, and for the same reasons, supporting freeipa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853863 Title: freeipa replica crashes near end of basic install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1853863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1853863] Re: freeipa replica crashes near end of basic install
Good to know. I was using ubuntu eoan. On 11/27/19 11:18 AM, Timo Aaltonen wrote: > for the record, ipa-replica-install works fine on the debian vm's that I > have set up for this (and finally had a go at replicating 4.8) > > my goal is to eventually have it all tested with a CI system somewhere, > and not rely just on the autopkgtests which can't run ipa-replica- > install > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853863 Title: freeipa replica crashes near end of basic install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1853863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854129] Re: regression: recent eoan patch killed ceph osd pool create
On all the monitors, mgrs and mds's I gave the command: find / -xdev -path "*/__pycache__/*.pyc" -delete Then rebooted them sequentially. Upon giving the same command to create a pool, ceph --verbose osd pool create qfblockdevsnoc2 32 the same as above was emitted, but then this happened: pool 'qfblockdevsnoc2' already exists And the pool appeared in the mix. A subsequent command to create another pool hung as before. So, I'm guessing some lock or another isn't released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854129 Title: regression: recent eoan patch killed ceph osd pool create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1854129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854129] Re: regression: recent eoan patch killed ceph osd pool create
The lock up happens also using the dashboard web interface. You can see the server side monitor gets the command then either loses it or waits forever somehow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854129 Title: regression: recent eoan patch killed ceph osd pool create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1854129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854129] [NEW] regression: recent eoan patch killed ceph osd pool create
Public bug reported:
After applying recent eaon normal upgrades to an otherwise vanilla
system (4 osd hosts x 6 rotating disks/host, usual mons, mgrs, mds): The
first time after a completely cold ceph cluster start (waiting for
health ok, idle otherwise): The command to create a ceph pool hangs, but
creates the pool. The second create pool attempt hangs forever, but
does not create the pool. I'm betting it has to do with the python3.7
patch just shipped, but that's just a guess I haven't tried to create a
pool in a while.
root@sysmon1:/etc/ceph# ceph --verbose osd pool create qfblockdevsnoc2 32
parsed_args: Namespace(admin_socket=None, block=False, cephconf=None,
client_id=None, client_name=None, cluster=None, cluster_timeout=None,
completion=False, help=False, input_file=None, output_file=None,
output_format=None, period=1, setgroup=None, setuser=None, status=False,
verbose=True, version=False, watch=False, watch_channel='cluster',
watch_debug=False, watch_error=False, watch_info=False, watch_sec=False,
watch_warn=False), childargs: ['osd', 'pool', 'create', 'qfblockdevsnoc2', '32']
cmd000: pg stat
cmd001: pg getmap
cmd002: pg dump {all|summary|sum|delta|pools|osds|pgs|pgs_brief
[all|summary|sum|delta|pools|osds|pgs|pgs_brief...]}
cmd003: pg dump_json {all|summary|sum|pools|osds|pgs
[all|summary|sum|pools|osds|pgs...]}
cmd004: pg dump_pools_json
cmd005: pg ls-by-pool { [...]}
cmd006: pg ls-by-primary {} { [...]}
cmd007: pg ls-by-osd {} { [...]}
cmd008: pg ls {} { [...]}
cmd009: pg dump_stuck {inactive|unclean|stale|undersized|degraded
[inactive|unclean|stale|undersized|degraded...]} {}
cmd010: pg debug unfound_objects_exist|degraded_pgs_exist
cmd011: pg scrub
cmd012: pg deep-scrub
cmd013: pg repair
cmd014: pg force-recovery [...]
cmd015: pg force-backfill [...]
cmd016: pg cancel-force-recovery [...]
cmd017: pg cancel-force-backfill [...]
cmd018: osd perf
cmd019: osd df {plain|tree} {class|name} {}
cmd020: osd blocked-by
cmd021: osd pool stats {}
cmd022: osd pool scrub [...]
cmd023: osd pool deep-scrub [...]
cmd024: osd pool repair [...]
cmd025: osd pool force-recovery [...]
cmd026: osd pool force-backfill [...]
cmd027: osd pool cancel-force-recovery [...]
cmd028: osd pool cancel-force-backfill [...]
cmd029: osd reweight-by-utilization {} {} {} {--no-increasing}
cmd030: osd test-reweight-by-utilization {} {} {}
{--no-increasing}
cmd031: osd reweight-by-pg {} {} {} {
[...]}
cmd032: osd test-reweight-by-pg {} {} {} {
[...]}
cmd033: osd destroy {--force} {--yes-i-really-mean-it}
cmd034: osd purge {--force} {--yes-i-really-mean-it}
cmd035: osd safe-to-destroy [...]
cmd036: osd ok-to-stop [...]
cmd037: osd scrub
cmd038: osd deep-scrub
cmd039: osd repair
cmd040: service dump
cmd041: service status
cmd042: config show {}
cmd043: config show-with-defaults
cmd044: device ls
cmd045: device info
cmd046: device ls-by-daemon
cmd047: device ls-by-host
cmd048: device set-life-expectancy {}
cmd049: device rm-life-expectancy
cmd050: balancer status
cmd051: balancer mode none|crush-compat|upmap
cmd052: balancer on
cmd053: balancer off
cmd054: balancer pool ls
cmd055: balancer pool add [...]
cmd056: balancer pool rm [...]
cmd057: balancer eval {}
cmd058: balancer eval-verbose {}
cmd059: balancer optimize { [...]}
cmd060: balancer show
cmd061: balancer rm
cmd062: balancer reset
cmd063: balancer dump
cmd064: balancer ls
cmd065: balancer execute
cmd066: crash info
cmd067: crash ls
cmd068: crash post
cmd069: crash prune
cmd070: crash rm
cmd071: crash stat
cmd072: crash json_report
cmd073: dashboard set-jwt-token-ttl
cmd074: dashboard get-jwt-token-ttl
cmd075: dashboard create-self-signed-cert
cmd076: dashboard grafana dashboards update
cmd077: dashboard get-alertmanager-api-host
cmd078: dashboard set-alertmanager-api-host
cmd079: dashboard reset-alertmanager-api-host
cmd080: dashboard get-audit-api-enabled
cmd081: dashboard set-audit-api-enabled
cmd082: dashboard reset-audit-api-enabled
cmd083: dashboard get-audit-api-log-payload
cmd084: dashboard set-audit-api-log-payload
cmd085: dashboard reset-audit-api-log-payload
cmd086: dashboard get-enable-browsable-api
cmd087: dashboard set-enable-browsable-api
cmd088: dashboard reset-enable-browsable-api
cmd089: dashboard get-ganesha-clusters-rados-pool-namespace
cmd090: dashboard set-ganesha-clusters-rados-pool-namespace
cmd091: dashboard reset-ganesha-clusters-rados-pool-namespace
cmd092: dashboard get-grafana-api-password
cmd093: dashboard set-grafana-api-password
cmd094: dashboard reset-grafana-api-password
cmd095: dashboard get-grafana-api-url
cmd096: dashboard set-grafana-api-url
cmd097: dashboard reset-grafana-api-url
cmd098: dashboard get-grafana-api-username
cmd099: dashboard set-grafana-api-username
cmd100: dashboard reset-grafana-api-username
cmd101: dashboard get-grafana-update-dashboards
cmd102: dashboard set-grafana-update-dashboards
cmd103: dashboard reset-grafana-update-dashboards
[Bug 1853863] Re: freeipa replica crashes near end of basic install
I appreciate your efforts. The thing is folks who use freeipa put it in the same 'has-got-to-work' 'no-regressions' category as the kernel. While it might lack a feature or need work in this or that area, it just can't 'not install' or have some major user-facing thing like the 'here's how you change your password' UI just not work after an 'upgrade'. There are so many moving parts and subsystems in freeipa I can't imagine how one person could possibly take on keeping up with it. FYI, I put a 30 second sleep just before the query that failed, and it failed the same way so I don't think it was a race issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853863 Title: freeipa replica crashes near end of basic install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1853863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1853863] Re: freeipa replica crashes near end of basic install
Timo, Thank you. I didn't understand freeipa wasn't supported on Ubuntu. You can consider this matter closed, I have to move to a different distro. On 11/25/19 2:20 PM, Timo Aaltonen wrote: > replica install is untested, not surprising to see it being broken > > and freeipa is in universe and not officially supported > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853863 Title: freeipa replica crashes near end of basic install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1853863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853863] Re: freeipa replica crashes near end of basic install
Of some interest, a curl of exactly the same link works (kinit admin in effect,
just after failure above).
root@registry2:/tmp# curl
https://registry1.1.quietfountain.com/ipa/keys/ca/caSigningCert%20cert-pki-ca?type=kem=eyJhbGciOiJSU0EtT0FFUCIsImVuYyI6IkEyNTZDQkMtSFM1MTIiLCJraWQiOm51bGx9.FjcSSiXUpFmdUiDGjqSx6RqQviY_rVOkMuskX-QRUx6boPUox9KvoadV9s9odZc8slpnLF974ew-L_UQ-udd5aO2CD2m0meTVwqLymJOpnjSmD-wFIOxvWYH4lPZiZPPnN6DmGmbDc0kFI5O43eL9z3HocN3nYsTNjg-obhZuCVwNsS7xhUqthosBC8XzFadu0N4c800u13SPLAgmFBuXH3_ICMGsf3E9bGppqEo3BZWSiyBYacMSP40etk9YQaxzknWM4hCxIzH_UALuhubTvnrHswUlqpuQFfCxYAGt-RswwYCkjG1B_UJ1-YKmcSPdw7dePgvxd8aHs-CeztU-g.tXofwhux7QSRKzYBB6ek9w.UNrq-g-MfjRsJ8ZGSdPGvQjIKEw9vk4wp04bG0ZZ7AzvsRT1Tf1bwKHqcWWtC5c0FuQ6YB3j1jvObjJOjoD176S710XpGg_DucL1rvDBSCPTQTHH06QDaE_LwcUIpLZH3bjyyAh9L3yh07-6WCCYDvuHQgfkASeWb916Q7-yTyGuKxk6Tg6wf27gFQS2_q91vllv4g148DX2cREaDb60HOhdkAn3BdWuyomoT3tdwLXX2kUavc-UmUth2WWqPICBaCFXbE1pNVxOMB0cMHD43WPxBzQqQgHV7Xz7QlpyAYJmjJZj0KSu4K4AzXZzX7DPCmBkjReuJvcIOL_zOmn-E38G-ApKLdzXFpr_GFJamzKx5A2AiTzQkivnN_1mwZK65si7NM1wi-10BRQcUL3cz5u2uDxBQZHA0eN26uOHS_OFXke37zuKjqw319GQnXfw_Mlys6Cxilnc0vcjmk6vpx4gJFoQbobbtfaFgzfmYtI3sACLXJLhS8yNQgv03d3zbAaFrZHc7LLv6iKQ_w-jBFxBQf_PepLIaoeebtA1Fld0r3OqZokXAE1vaFfN0nVBAhh4sx-BD3gHpVopCZQHsoeZvKZF23xCbXQCKMAe_8rgNEtuhig2dgXY_3vL2V0xbD_7c2eNcsvutBm-9DGkGiotCOJhrUR2riXCvSIPb-Vt-G2WDg_U8z44JfyvkVHo.3nNEjhuACxacf-BrFl5aN5F0XNUbsF-plMhJ6Sbzt5c
[1] 4501
root@registry2:/tmp#
IPA: Identity Policy Audit
var dojoConfig = {
baseUrl: "../ui/js",
has: {
'dojo-firebug': false,
'dojo-debug-messages': true
},
parseOnLoad: false,
async: true,
packages: [
{
name:'dojo',
location:'dojo'
},
{
name: 'freeipa',
location: 'freeipa'
}
]
};
(function() {
var icons = [
'../ui/favicon.ico'
];
var styles = [
'../ui/css/patternfly.css',
'../ui/css/ipa.css'
];
var scripts = [
'../ui/js/libs/jquery.js',
'../ui/js/libs/jquery.ordered-map.js',
'../ui/js/dojo/dojo.js'
];
ipa_loader.scripts(scripts, function() {
require([
'dojo/dom',
'freeipa/core',
'dojo/domReady!'
],
function(dom) {
var text = require('freeipa/text');
var msg = text.get('@i18n:unauthorized-page');
if (msg) {
dom.byId('unauthorized-msg').innerHTML=msg;
}
});
});
ipa_loader.styles(styles);
ipa_loader.icons(icons);
})();
Unable to verify your Kerberos credentials
Please make sure that you have valid Kerberos tickets (obtainable via
kinit), and that you have configured your browser correctly.
Browser configuration
If this is your first time, please configure your
browser.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853863
Title:
freeipa replica crashes near end of basic install
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1853863/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853863] Re: freeipa replica crashes near end of basic install
Here's the shell script log root@registry2:~# kinit admin Password for ad...@1.quietfountain.com: root@registry2:~# ipa-replica-install --setup-dns --no-forwarders WARNING: conflicting time synchronization service 'ntp' will be disabled in favor of chronyd Lookup failed: Preferred host registry2.1.quietfountain.com does not provide DNS. Run connection check to master Connection check OK Configuring directory server (dirsrv). Estimated time: 30 seconds [1/41]: creating directory server instance Starting installation... Created symlink /etc/systemd/system/multi-user.target.wants/dirsrv@1-QUIETFOUNTAIN-COM.service → /lib/systemd/system/dirsrv@.service. Allocate local instance with ldapi://%2fvar%2frun%2fslapd-1-QUIETFOUNTAIN-COM.socket [2/41]: configure autobind for root [3/41]: stopping directory server [4/41]: updating configuration in dse.ldif [5/41]: starting directory server [6/41]: adding default schema [7/41]: enabling memberof plugin [8/41]: enabling winsync plugin [9/41]: configure password logging [10/41]: configuring replication version plugin [11/41]: enabling IPA enrollment plugin [12/41]: configuring uniqueness plugin [13/41]: configuring uuid plugin [14/41]: configuring modrdn plugin [15/41]: configuring DNS plugin [16/41]: enabling entryUSN plugin [17/41]: configuring lockout plugin [18/41]: configuring topology plugin [19/41]: creating indices [20/41]: enabling referential integrity plugin [21/41]: configuring certmap.conf [22/41]: configure new location for managed entries [23/41]: configure dirsrv ccache and keytab [24/41]: enabling SASL mapping fallback [25/41]: restarting directory server [26/41]: creating DS keytab [27/41]: ignore time skew for initial replication [28/41]: setting up initial replication Starting replication, please wait until this has completed. Update in progress, 62 seconds elapsed Update succeeded [29/41]: prevent time skew after initial replication [30/41]: adding sasl mappings to the directory [31/41]: updating schema [32/41]: setting Auto Member configuration [33/41]: enabling S4U2Proxy delegation [34/41]: initializing group membership [35/41]: adding master entry [36/41]: initializing domain level [37/41]: configuring Posix uid/gid generation [38/41]: adding replication acis [39/41]: activating sidgen plugin [40/41]: activating extdom plugin [41/41]: configuring directory to start on boot Done configuring directory server (dirsrv). Configuring Kerberos KDC (krb5kdc) [1/5]: configuring KDC [2/5]: adding the password extension to the directory [3/5]: creating anonymous principal [4/5]: starting the KDC [5/5]: configuring KDC to start on boot Done configuring Kerberos KDC (krb5kdc). Configuring kadmin [1/2]: starting kadmin [2/2]: configuring kadmin to start on boot Done configuring kadmin. Configuring directory server (dirsrv) [1/3]: configuring TLS for DS instance [2/3]: importing CA certificates from LDAP [3/3]: restarting directory server Done configuring directory server (dirsrv). Configuring the web interface (httpd) [1/21]: stopping httpd [2/21]: backing up ssl.conf [3/21]: disabling nss.conf [4/21]: configuring mod_ssl certificate paths [5/21]: setting mod_ssl protocol list [6/21]: configuring mod_ssl log directory [7/21]: disabling mod_ssl OCSP [8/21]: adding URL rewriting rules [9/21]: configuring httpd [10/21]: setting up httpd keytab [11/21]: configuring Gssproxy [12/21]: setting up ssl [13/21]: configure certmonger for renewals [14/21]: publish CA cert [15/21]: clean up any existing httpd ccaches [16/21]: configuring SELinux for httpd [17/21]: create KDC proxy config [18/21]: enable KDC proxy [19/21]: starting httpd [20/21]: configuring httpd to start on boot [21/21]: enabling oddjobd Done configuring the web interface (httpd). Configuring ipa-otpd [1/2]: starting ipa-otpd [2/2]: configuring ipa-otpd to start on boot Done configuring ipa-otpd. Custodia uses 'registry1.1.quietfountain.com' as master peer. Configuring ipa-custodia [1/4]: Generating ipa-custodia config file [2/4]: Generating ipa-custodia keys [3/4]: starting ipa-custodia [4/4]: configuring ipa-custodia to start on boot Done configuring ipa-custodia. Your system may be partly configured. Run /usr/sbin/ipa-server-install --uninstall to clean up. 404 Client Error: Not Found for url:
[Bug 1853863] Re: freeipa replica crashes near end of basic install
Both registry1 and registry2 are 'vanilla' eoan mate vms. Host registry1... has a working freeipa-server based on eoan installed. No other packages. It does include the dns support. registry2 is the attempt to install a replica. No other packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853863 Title: freeipa replica crashes near end of basic install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1853863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853863] [NEW] freeipa replica crashes near end of basic install
Public bug reported: Just trying to see if freeipa works on Ubuntu, I installed freeipa- server on one system, then tried to install the freeipa-replica on another. The two system setup works just fine on Fedora, but I need to standardize on one distro so I'm evaluating Ubuntu hoping that Canonical doesn't push out patches without at least testing whether basic installs will or won't work. After installing the server, I found that the GUI was unusable because the font necessary to show such things as 'next' and 'back' and so on misconfigured. Pretty big 'bug' to miss. So I put in the time to figure out a work around and report a bug. OK. Now I go to do the basic installation of a replica. It gets near to the end of the install, then crashes with something as basic as https auth access. My hunch is some difference to do with mod_nss and mod_ssl in apache2, but that's just a guess. The debug log follows. But two 'crashes on install attempt' bugs on a major package meant to operate at the core of a large-user-count installation? How can this be trusted going forward? Is my understanding of 'release' about Ubuntu wrong, are my expectations what's wrong here? Here's the debug log. I trimmed most of the lead which was entirely normal, no bug reports. I pick it up near the end, the whole traceback is at the very end. 2019-11-25T05:06:29Z DEBUG [4/4]: configuring ipa-custodia to start on boot 2019-11-25T05:06:29Z DEBUG Starting external process 2019-11-25T05:06:29Z DEBUG args=['/bin/systemctl', 'is-enabled', 'ipa-custodia.service'] 2019-11-25T05:06:29Z DEBUG Process finished, return code=1 2019-11-25T05:06:29Z DEBUG stdout=disabled 2019-11-25T05:06:29Z DEBUG stderr= 2019-11-25T05:06:29Z DEBUG Loading StateFile from '/var/lib/ipa/sysrestore/sysrestore.state' 2019-11-25T05:06:29Z DEBUG Saving StateFile to '/var/lib/ipa/sysrestore/sysrestore.state' 2019-11-25T05:06:29Z DEBUG Starting external process 2019-11-25T05:06:29Z DEBUG args=['/bin/systemctl', 'disable', 'ipa-custodia.service'] 2019-11-25T05:06:32Z DEBUG Process finished, return code=0 2019-11-25T05:06:33Z DEBUG stdout= 2019-11-25T05:06:33Z DEBUG stderr= 2019-11-25T05:06:33Z DEBUG step duration: ipa-custodia __enable 3.54 sec 2019-11-25T05:06:33Z DEBUG Done configuring ipa-custodia. 2019-11-25T05:06:33Z DEBUG service duration: ipa-custodia 9.01 sec 2019-11-25T05:06:33Z DEBUG Loading StateFile from '/var/lib/ipa/sysupgrade/sysupgrade.state' 2019-11-25T05:06:33Z DEBUG Saving StateFile to '/var/lib/ipa/sysupgrade/sysupgrade.state' 2019-11-25T05:06:33Z DEBUG Waiting up to 300 seconds to see our keys appear on host ldap://registry1.1.quietfountain.com 2019-11-25T05:06:34Z DEBUG Starting external process 2019-11-25T05:06:34Z DEBUG args=['/usr/bin/certutil', '-d', '/tmp/tmpjou8ki45', '-N', '-f', '/tmp/tmpjou8ki45/pwdfile.txt', '-@', '/tmp/tmpjou8ki45/pwdfile.txt'] 2019-11-25T05:06:36Z DEBUG Process finished, return code=0 2019-11-25T05:06:36Z DEBUG stdout= 2019-11-25T05:06:36Z DEBUG stderr= 2019-11-25T05:06:36Z DEBUG Starting external process 2019-11-25T05:06:36Z DEBUG args=['/usr/sbin/selinuxenabled'] 2019-11-25T05:06:36Z DEBUG Process finished, return code=1 2019-11-25T05:06:36Z DEBUG stdout= 2019-11-25T05:06:36Z DEBUG stderr= 2019-11-25T05:06:36Z DEBUG Starting external process 2019-11-25T05:06:36Z DEBUG args=['/usr/sbin/selinuxenabled'] 2019-11-25T05:06:36Z DEBUG Process finished, return code=1 2019-11-25T05:06:36Z DEBUG stdout= 2019-11-25T05:06:36Z DEBUG stderr= 2019-11-25T05:06:36Z DEBUG Starting external process 2019-11-25T05:06:36Z DEBUG args=['/usr/sbin/selinuxenabled'] 2019-11-25T05:06:36Z DEBUG Process finished, return code=1 2019-11-25T05:06:36Z DEBUG stdout= 2019-11-25T05:06:36Z DEBUG stderr= 2019-11-25T05:06:36Z DEBUG Starting external process 2019-11-25T05:06:36Z DEBUG args=['/usr/sbin/selinuxenabled'] 2019-11-25T05:06:36Z DEBUG Process finished, return code=1 2019-11-25T05:06:36Z DEBUG stdout= 2019-11-25T05:06:36Z DEBUG stderr= 2019-11-25T05:06:36Z DEBUG Starting external process 2019-11-25T05:06:36Z DEBUG args=['/usr/sbin/selinuxenabled'] 2019-11-25T05:06:36Z DEBUG Process finished, return code=1 2019-11-25T05:06:36Z DEBUG stdout= 2019-11-25T05:06:36Z DEBUG stderr= 2019-11-25T05:06:37Z DEBUG Starting new HTTPS connection (1): registry1.1.quietfountain.com:443 2019-11-25T05:06:38Z DEBUG https://registry1.1.quietfountain.com:443 "GET
[Bug 1853676] [NEW] Regression: fontawesome in is freeipa font-awesome in ubuntu
Public bug reported: Notice the bug and fix mentioned in https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1772921 is, somehow 're-broken' in eoan. Possibly because of: https://pagure.io/freeipa/c/78652a52f083bac5238f9e0a6520e0e448dadabe The result is none of the directional glyphs appear in the freeipa UI. Renders freeipa's web-ui unusable. work-around until patch is released: ln -s /usr/share/fonts/truetype/font-awesome /usr/share/fonts/truetype/fontawesome ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: freeipa-server 4.8.1-2ubuntu1 [modified: usr/share/ipa/html/ca.crt usr/share/ipa/html/krb.con usr/share/ipa/html/krb5.ini usr/share/ipa/html/krbrealm.con] ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Nov 22 22:05:14 2019 InstallationDate: Installed on 2019-11-01 (21 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: freeipa UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.ipa-dnskeysyncd: [modified] mtime.conffile..etc.default.ipa-dnskeysyncd: 2019-11-21T23:18:49.543399 ** Affects: freeipa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853676 Title: Regression: fontawesome in is freeipa font-awesome in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1853676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850648] Re: ubuntu debs missing ctdb_mutex_ceph_rados_helper
Adding usr/lib/*/ctdb/ctdb_mutex_ceph_rados_helper and usr/share/man/man7/ctdb_mutex_ceph_rados_helper.7 to /debian/ctdb.install puts those files in the ctdb deb and corrects the above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850648 Title: ubuntu debs missing ctdb_mutex_ceph_rados_helper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1850648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850648] Re: ubuntu debs missing ctdb_mutex_ceph_rados_helper
When --enable-ceph-relock is added to rules, and librados-dev is installed, dpkg-buildpackage reports this error: ake[1]: Entering directory '/tmp/samba/samba-4.10.7+dfsg' dh_missing --fail-missing dh_missing: usr/lib/x86_64-linux-gnu/ctdb/ctdb_mutex_ceph_rados_helper exists in debian/tmp but is not installed to anywhere dh_missing: usr/share/man/man7/ctdb_mutex_ceph_rados_helper.7 exists in debian/tmp but is not installed to anywhere The following debhelper tools have reported what they installed (with files per package) * dh_install: ctdb (58), libnss-winbind (2), libpam-winbind (4), libparse-pidl-perl (9), libsmbclient (3), libsmbclient-dev (3), libwbclient-dev (3), libwbclient0 (4), python3-samba (1), registry-tools (8), samba (56), samba-common (5), samba-common-bin (23), samba-dev (113), samba-dsdb-modules (2), samba-libs (157), samba-testsuite (12), samba-vfs-modules (82), smbclient (23), winbind (23) * dh_installdocs: ctdb (6), libnss-winbind (0), libpam-winbind (0), libparse-pidl-perl (0), libsmbclient (0), libsmbclient-dev (0), libwbclient-dev (0), libwbclient0 (0), python3-samba (0), registry-tools (0), samba (0), samba-common (2), samba-common-bin (0), samba-dev (0), samba-dsdb-modules (0), samba-libs (0), samba-testsuite (0), samba-vfs-modules (0), smbclient (0), winbind (0) * dh_installexamples: ctdb (9), libnss-winbind (0), libpam-winbind (1), libparse-pidl-perl (0), libsmbclient (0), libsmbclient-dev (24), libwbclient-dev (0), libwbclient0 (0), python3-samba (0), registry-tools (0), samba (4), samba-common (1), samba-common-bin (0), samba-dev (5), samba-dsdb-modules (0), samba-libs (0), samba-testsuite (1), samba-vfs-modules (0), smbclient (0), winbind (0) * dh_installman: ctdb (0), libnss-winbind (0), libpam-winbind (0), libparse-pidl-perl (0), libsmbclient (0), libsmbclient-dev (0), libwbclient-dev (0), libwbclient0 (0), python3-samba (0), registry-tools (0), samba (1), samba-common (0), samba-common-bin (0), samba-dev (0), samba-dsdb-modules (0), samba-libs (0), samba-testsuite (0), samba-vfs-modules (0), smbclient (0), winbind (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built For a short-term work-around: Add the files to debian/not-installed dh_missing: missing files, aborting make[1]: *** [debian/rules:251: override_dh_missing] Error 255 make[1]: Leaving directory '/tmp/samba/samba-4.10.7+dfsg' make: *** [debian/rules:88: binary] Error 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850648 Title: ubuntu debs missing ctdb_mutex_ceph_rados_helper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1850648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850648] [NEW] ubuntu debs missing ctdb_mutex_ceph_rados_helper
Public bug reported: In the samba source subdirectory ctdb/utils/ceph there is ctdb_mutex_ceph_rados_helper.c, needed for proper operation of ctdb in a ceph environment. But, ubuntu doesn't include the --enable-ceph-reclock option so that program doesn't appear in the ubuntu version of the ctdb/samba debs. As ubuntu distributes ceph, it should provide the ctdb support package. Thanks HC ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850648 Title: ubuntu debs missing ctdb_mutex_ceph_rados_helper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1850648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848950] [NEW] pg not [deep] scrubbed since 0.000000 -- w/fix
Public bug reported: Would ubuntu include the nautilus patch https://github.com/ceph/ceph/pull/28869 ? Right now the ceph dashboard won't report 'normal'/'green' because of the bug/hack of resetting scrub timestamps to 0 when auto-repair is set. The above patch, accepted in May by Ceph, fixes that. Fixes: http://tracker.ceph.com/issues/40073 >From upstream.. osd: Fix the way that auto repair triggers after regular scrub We used a trick to get auto repair to happen after scrub errors which reset the scrub/deep-scrub stamps. This not only looks bad to the user, but causes health warnings. Instead use a new scrubber flag need_auto which causes reg_next_srub() to set deadline for immediate scrubbing. It also causes time_for_deep to be set so that auto repair triggers. Every regular scrub was triggering a deep scrub. Check scrubber.authoritative.size() (scrub error count), so regular scrub doesn't trigger deep-scrub when there are no errors. Caused by: 2202e5d ** Affects: ceph (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848950 Title: pg not [deep] scrubbed since 0.00 -- w/fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1848950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip
I see the same thing related to slowness in a old-style parallel port device passed to a VM. Shortly after there's traffic related to the parallel port the task will hang forever, eventually locking up the VM entirely. This has happened on two SuperMicro servers, the problem did not exist in Xenial and began with the upgrade to bionic and remains in eoan. Oct 9 03:43:40 noc2 kernel: [48455.643616] INFO: task CPU 0/KVM:18338 blocked for more than 845 seconds. Oct 9 03:43:40 noc2 kernel: [48455.643624] Tainted: P O 5.3.0-13-generic #14-Ubuntu Oct 9 03:43:40 noc2 kernel: [48455.643625] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 9 03:43:40 noc2 kernel: [48455.643627] CPU 0/KVM D0 18338 1 0x0100 Oct 9 03:43:40 noc2 kernel: [48455.643630] Call Trace: Oct 9 03:43:40 noc2 kernel: [48455.643643] __schedule+0x2b9/0x6c0 Oct 9 03:43:40 noc2 kernel: [48455.643655] ? handle_io+0x4c/0xc0 [kvm_intel] Oct 9 03:43:40 noc2 kernel: [48455.643659] schedule+0x42/0xb0 Oct 9 03:43:40 noc2 kernel: [48455.643661] schedule_preempt_disabled+0xe/0x10 Oct 9 03:43:40 noc2 kernel: [48455.643663] __mutex_lock.isra.0+0x182/0x4f0 Oct 9 03:43:40 noc2 kernel: [48455.643712] ? kvm_arch_vcpu_put+0xe4/0xf0 [kvm] Oct 9 03:43:40 noc2 kernel: [48455.643731] ? kvm_arch_vcpu_ioctl_run+0x37a/0x590 [kvm] Oct 9 03:43:40 noc2 kernel: [48455.643733] __mutex_lock_slowpath+0x13/0x20 Oct 9 03:43:40 noc2 kernel: [48455.643735] mutex_lock+0x2e/0x40 Oct 9 03:43:40 noc2 kernel: [48455.643738] pp_ioctl+0x25/0x50 [ppdev] Oct 9 03:43:40 noc2 kernel: [48455.643741] do_vfs_ioctl+0x407/0x670 Oct 9 03:43:40 noc2 kernel: [48455.643745] ? __secure_computing+0x42/0xe0 Oct 9 03:43:40 noc2 kernel: [48455.643747] ksys_ioctl+0x67/0x90 Oct 9 03:43:40 noc2 kernel: [48455.643748] __x64_sys_ioctl+0x1a/0x20 Oct 9 03:43:40 noc2 kernel: [48455.643752] do_syscall_64+0x5a/0x130 Oct 9 03:43:40 noc2 kernel: [48455.643754] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 9 03:43:40 noc2 kernel: [48455.643756] RIP: 0033:0x7fb9e75b167b Oct 9 03:43:40 noc2 kernel: [48455.643764] Code: Bad RIP value. Oct 9 03:43:40 noc2 kernel: [48455.643765] RSP: 002b:7fb9e4d743a8 EFLAGS: 0246 ORIG_RAX: 0010 Oct 9 03:43:40 noc2 kernel: [48455.643767] RAX: ffda RBX: 0004 RCX: 7fb9e75b167b Oct 9 03:43:40 noc2 kernel: [48455.643768] RDX: 7fb9e4d743b7 RSI: 40017086 RDI: 000a Oct 9 03:43:40 noc2 kernel: [48455.643769] RBP: 000a R08: 55a2756817e8 R09: 55a275289de0 Oct 9 03:43:40 noc2 kernel: [48455.643770] R10: 0001 R11: 0246 R12: 7fb9e4d743ef Oct 9 03:43:40 noc2 kernel: [48455.643771] R13: R14: 0001 R15: 55a276e69010 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825413 Title: mdadm, mkfs, other io commands hang, stuck task, bad rip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846975] Re: extra } crashes update-grub in eaon w/zfs
deleting 10_linux_zfs restored previous normal zfs boot operations. Note the script shows more severe errors than the extra }, the initrd arguments were blank. Perhaps some guidance for those of us that already have zfs roots as per the previous guides... to have the new 'for desktops' feature for zfs disabled until explicitly enabled? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846975 Title: extra } crashes update-grub in eaon w/zfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1846975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846975] [NEW] extra } crashes update-grub in eaon w/zfs
Public bug reported:
Despite the attempted patch to prevent a double } } by 10_linux_zfs in grub.cfg
for pure zfs systems, the failure remains in the latest eoan.
Total install failure results crashing do-release-upgrade. Critical.
A debug run follows, then the generated file with the extra }
I added a set -x at the top of the loop. the results were
a799481e327948b6a6dc54d8582a111c- history
2016-07-01_05.30.00--6m, Ubuntu 16.04 LTS on 07/01/2016 @ 05:30
zfsroots/std@2016-07-01_05.30.00--6m/dev/sda1
a799481e327948b6a6dc54d8582a111c- history pristinewntp, Ubuntu
16.04 LTS on 05/08/2016 @ 15:02 zfsroots/std@pristinewntp /dev/sda1
+ true
+ have_zsys=
+ printf \t
+ IFS= read -r machineid iszsys section name dataset device initrd kernel opt
+ [ main = history ]
+ [ != main -a -n ]
+ title=Ubuntu Eoan Ermine (development branch)
+ main_dataset_name=Ubuntu Eoan Ermine (development branch)
+ main_dataset=zfsroots/std
+ zfs_linux_entry 0 Ubuntu Eoan Ermine (development branch) simple zfsroots/std
/dev/sda1
+ submenu_level=0
+ title=Ubuntu Eoan Ermine (development branch)
+ type=simple
+ dataset=zfsroots/std
+ boot_device=/dev/sda1
+ initrd=
+ kernel=
+ kernel_additional_args=
+ basename
+ sed -e s,^[^0-9]*-,,g
+ kernel_version=
+ printf %0s
+ tr
+ submenu_indentation=
+ sed s/^//
+ echo Ubuntu Eoan Ermine (development branch)
+ grub_quote
+ sed s/'/'\\''/g
+ echo menuentry 'Ubuntu Eoan Ermine (development branch)' --class ubuntu
--class gnu-linux --class gnu --class os ${menuentry_id_option}
'gnulinux-zfsroots/std-' {
+ [ 1 = 1 ]
+ echo recordfail
+ sed s/^//
+ [ = ]
+ echo load_video
+ sed s/^//
+ [ 1 = 0 ]
+ [ simple != recovery ]
+ [ != ]
+ [ 1 = 1 ]
+ echo gfxmode ${linux_gfx_mode}
+ sed s/^//
+ echo insmod gzio
+ sed s/^//
+ echo if [ "${grub_platform}" = xen ]; then insmod xzio; insmod lzopio; fi
+ sed s/^//
+ prepare_grub_to_access_device_cached /dev/sda1
+ local boot_device=/dev/sda1
+ grub_add_tab
+ sed+ -e s/^/ /
sed s/^//
+ echo /dev/sda1
+ tr / _
+ local boot_device_idx=_dev_sda1
+ echo boot_device_dev_sda1
+ cache_file=/tmp/zfstmp.qX6P4N/boot_device_dev_sda1
+ [ ! -f /tmp/zfstmp.qX6P4N/boot_device_dev_sda1 ]
+ set +u
+ prepare_grub_to_access_device /dev/sda1
+ old_ifs=
+ IFS=
+ /usr/sbin/grub-probe --device /dev/sda1 --target=partmap
+ partmap=msdos
+ echo insmod part_msdos
+ loop_file=
+ /usr/sbin/grub-probe --device /dev/sda1 --target=abstraction
+ abstraction=
+ /usr/sbin/grub-probe --device /dev/sda1 --target=fs
+ fs=zfs
+ echo insmod zfs
+ [ x = xy ]
+ /usr/sbin/grub-probe --device /dev/sda1 --target=compatibility_hint
+ fs_hint=hd0,msdos1
+ [ xhd0,msdos1 != x ]
+ echo set root='hd0,msdos1'
+ /usr/sbin/grub-probe --device /dev/sda1 --target=fs_uuid
+ fs_uuid=7a1b09c5771f32a5
+ /usr/sbin/grub-probe --device /dev/sda1 --target=hints_string
+ hints=--hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1
--hint-baremetal=ahci0,msdos1
+ echo if [ x$feature_platform_search_hint = xy ]; then
+ echo search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 7a1b09c5771f32a5
+ echo else
+ echo search --no-floppy --fs-uuid --set=root 7a1b09c5771f32a5
+ echo fi
+ IFS=
+ [ x != x ]
+ echo insmod part_msdos
insmod zfs
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 7a1b09c5771f32a5
else
search --no-floppy --fs-uuid --set=root 7a1b09c5771f32a5
fi
+ set -u
+ cat /tmp/zfstmp.qX6P4N/boot_device_dev_sda1
+ echo insmod part_msdos
insmod zfs
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 7a1b09c5771f32a5
else
search --no-floppy --fs-uuid --set=root 7a1b09c5771f32a5
fi
+ [ 1 = 0 ]
+ [ simple != simple ]
+ linux_default_args=boot=zfs rpool=zfsroot bootfs=zfsroot/std
+ [ simple = recovery ]
+ sed s/^//
+ [ 1 = 0 ]
+ [ simple != simple ]
+ sed s/^//
+ echo }
+ sed s/^//
+ at_least_one_entry=1
+ last_section=main
+ printf \t
+ IFS= read -r machineid iszsys section name dataset device initrd kernel opt
+ [ history = history ]
+ [ - != yes ]
+ continue
+ printf \t
+ IFS= read -r machineid iszsys section name dataset device initrd kernel opt
+ [ history = history ]
+ [ - != yes ]
+ continue
+ printf \t
+ IFS= read -r machineid iszsys section name dataset device initrd kernel opt
+ [ history = history ]
+ [ - != yes ]
+ continue
+ printf \t
+ IFS= read -r machineid iszsys section name dataset device initrd kernel opt
+ [ history = history ]
+ [ - != yes ]
+ continue
+ printf \t
+ IFS= read -r machineid iszsys section name dataset device initrd kernel opt
+ [ history = history ]
+ [ - != yes ]
+ continue
+ printf \t
+ IFS= read -r machineid iszsys
[Bug 1843857] [NEW] IPMasquerade=yes -> ignored on eoan
Public bug reported: I'm testing out eoan, I have a [Network] section with IPMasquerade=yes. The system starts without complaint from systemd in the logs, but I see no evidence of source natting going on. I'm not sure of sub-dependencies, but I think source natting depends on libiptc-dev, which I don't see among the listings in eoan. I found Systemd-networkd updates 'iptables-legacy' with the source natting/masquerade detail -- which is disused by default. So it has no effect and doesn't throw an error. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843857 Title: IPMasquerade=yes -> ignored on eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1843857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
Upstream has two approaches to a solution. One was to disable sdpk except for development versions because the spdk folks set their lowest usable software level to corei7. I couldn't get that patch to work in the ubuntu packaging 'apt-get source ceph'. I was able to get the patch working that edited the two files mentioned in the above-- editing the memcpy code and commenting out the corei7. What I would like to see, and see as a general solution that might set canonical apart from others in a good way is: when compiling using dpkg-buildpackage ... a canonical-wide flag that overrides whatever -msse and -march might be the defaults and replace that with -march=native. In that way, those who want to compile a package to get best performance (or any performance) on a particular machine can make it 'just work'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
Not so great minds think alike. Here it is, from upstream: https://tracker.ceph.com/issues/41330 ** Bug watch added: tracker.ceph.com/issues #41330 http://tracker.ceph.com/issues/41330 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
I think I found it, but could use some validation. Notice at https://ceph.io/geen-categorie/sse-optimization-for-erasure-code-in-ceph/ we have the precedent for ceph's checking what level of SSE instructions are available then using the appropriate one. However, in the ubuntu version, littered around the makefiles we see -msse4.2 in several places oddly (there is no mssse3) -msse -msse2 -msse3 -mssse3 -mpclmul -msse4.1 -msse4.2 in rocksdb we see often -msse4.2 Canonical should remove the -msse4.2 compiler flags as ceph doesn't advertise it is not compatible with systems with less than sse4 capabilities. I'm looking in to this further, but it appears to fit what I know so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
And with debug symbols:
(gdb) run
Starting program: /usr/bin/ceph-bluestore-tool
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Program received signal SIGILL, Illegal instruction.
0x55743984 in eth_dev_init_cb_lists ()
(gdb) backtrace full
#0 0x55743984 in eth_dev_init_cb_lists ()
No symbol table info available.
#1 0x55dc045d in __libc_csu_init ()
No symbol table info available.
#2 0x7fffee524e2e in __libc_start_main (main=0x557346b0 , argc=1, argv=0x7fffe328, init=0x55dc0410 <__libc_csu_init>,
fini=, rtld_fini=, stack_end=0x7fffe318)
at ../csu/libc-start.c:264
result =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737351328816,
5390835150573769728, 140737353589600, 140737353586152, 1, 140737488347944,
140737488347960, 140737354007706}, mask_was_saved = 8}}, priv = {pad = {0x1,
0x7fffe328, 0x7fffe338, 0x77ffe190}, data = {prev = 0x1, cleanup =
0x7fffe328, canceltype = -7368}}}
not_first_call =
#3 0x5581e47e in _start () at /usr/include/c++/9/ostream:108
No symbol table info available.
(gdb) backtrace full
#0 0x55743984 in eth_dev_init_cb_lists () at
/usr/include/c++/9/ostream:108
No symbol table info available.
#1 0x55dc045d in __libc_csu_init ()
No symbol table info available.
#2 0x7fffee524e2e in __libc_start_main (main=0x557346b0 , argc=1, argv=0x7fffe328, init=0x55dc0410 <__libc_csu_init>,
fini=, rtld_fini=, stack_end=0x7fffe318)
at ../csu/libc-start.c:264
result =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737351328816,
5390835150573769728, 140737353589600, 140737353586152, 1, 140737488347944,
140737488347960, 140737354007706}, mask_was_saved = 8}}, priv = {pad = {0x1,
0x7fffe328, 0x7fffe338, 0x77ffe190}, data = {prev = 0x1, cleanup =
0x7fffe328, canceltype = -7368}}}
not_first_call =
#3 0x5581e47e in _start () at /usr/include/c++/9/ostream:108
No symbol table info available.
(gdb) info registers
rax0x55fe0340 93825003291456
rbx0x3654
rcx0xb 11
rdx0x568921a0 93825012408736
rsi0x7fffe328 140737488347944
rdi0x1 1
rbp0xc50xc5
rsp0x7fffe208 0x7fffe208
r8 0x0 0
r9 0x0 0
r100x642e6264626f6c62 7218815436009204834
r110x2032
r120x55f2b510 93825002550544
r130x1 1
r140x7fffe328 140737488347944
r150x568921a0 93825012408736
rip0x55743984 0x55743984
eflags 0x10212 [ AF IF RF ]
cs 0x3351
ss 0x2b43
ds 0x0 0
es 0x0 0
fs 0x0 0
gs 0x0 0
(gdb) x/16i $pc
=> 0x55743984 : pextrq $0x1,%xmm2,0x40c0(%rax)
0x5574398f : pextrq $0x1,%xmm1,0xc1c0(%rax)
0x5574399a : movdqa 0x6c2eae(%rip),%xmm2
# 0x55e06850
0x557439a2 : movq %xmm1,0x8140(%rax)
0x557439aa : movdqa 0x6c2eae(%rip),%xmm1
# 0x55e06860
0x557439b2 : movq $0x0,0x8138(%rax)
0x557439bd : paddq %xmm0,%xmm2
0x557439c1 : movq %xmm2,0x10240(%rax)
0x557439c9 : paddq %xmm0,%xmm1
0x557439cd : pextrq $0x1,%xmm2,0x142c0(%rax)
0x557439d8 : movdqa 0x6c2e90(%rip),%xmm2
# 0x55e06870
0x557439e0 : movq %xmm1,0x18340(%rax)
0x557439e8 : pextrq $0x1,%xmm1,0x1c3c0(%rax)
0x557439f3 : movdqa 0x6c2e85(%rip),%xmm1
# 0x55e06880
0x557439fb : movq $0x0,0xc1b8(%rax)
0x55743a06 : paddq %xmm0,%xmm2
(gdb) thread apply all backtrace
Thread 1 (Thread 0x7fffee0e20c0 (LWP 825)):
#0 0x55743984 in eth_dev_init_cb_lists () at
/usr/include/c++/9/ostream:108
#1 0x55dc045d in __libc_csu_init ()
#2 0x7fffee524e2e in __libc_start_main (main=0x557346b0 , argc=1, argv=0x7fffe328, init=0x55dc0410 <__libc_csu_init>,
fini=, rtld_fini=, stack_end=0x7fffe318) at
../csu/libc-start.c:264
#3 0x5581e47e in _start () at /usr/include/c++/9/ostream:108
(gdb)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842020
Title:
ceph patch as of 8/29 segfaults all bluestore osds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
Try it setting the processors on the VM to dual conroe. On 8/30/19 3:38 AM, Trent Lloyd wrote: > At a super basic level I can't reproduce this. With an eoan container on > an eoan host I don't get a segfault from ceph-bluestore-tool. > > I'd suggest we may need to look at getting > (1) a coredump > (2) the somewhat unlikely but not impossible chance that it's CPU-dependent > for some kind of optimization reason or similar as this CPU is quite old [can > you confirm the install is also 64-bit?] > (3) A bunch of information about the system configuration.. e.g. from > 'sosreport' would work or similar. [I'm not sure if you can use reportbug to > upload system info about an existing bug] - including at least the "dpkg -l" > full package list. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
here's a core.gz of a typical crash in case the previous apport thing didn't get it to you. ** Attachment added: "core.gz of typical crash" https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+attachment/5285838/+files/core.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] modified.conffile..etc.default.apport.txt
apport information ** Attachment added: "modified.conffile..etc.default.apport.txt" https://bugs.launchpad.net/bugs/1842020/+attachment/5285824/+files/modified.conffile..etc.default.apport.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
apport information ** Tags added: apport-collected eoan ** Description changed: The ceph patch on eoan distributed 8/29 crashes all bluestore OSD's and is unusable at least on some systems. Failed on an old dual Xeon E5345 box. Easy test. Run: /usr/bin/ceph-bluestore-tool On working systems it reports a help message. On the latest eoan release distributed by canonical it turns in to an illegal instruction process kill, just after reading /proc/<...>/auxv looks like something to do with vsock issues. strace -k -y /usr/bin/ceph-bluestore-tool is instructive. Notice valgrind against that program reports thousands of memory allocation issues. Reverting the system to the snapshot before the apt upgrade restores full operations. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu7 + Architecture: amd64 + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-07-30 (30 days ago) + InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190726) + Package: ceph 14.2.2-0ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_US + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 + Tags: eoan + Uname: Linux 5.2.0-15-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + mtime.conffile..etc.default.apport: 2019-08-30T11:35:29.463071 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1842020/+attachment/5285822/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1842020/+attachment/5285823/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
FYI, in the eoan VM you used to duplicate the bug, try it again with the
processor set to 2 'Conroe' cpus. i440FX chipset, BIOS, kvm-spice
emulator.
Also, I tried compiling ceph nautilus from upstream, can't do it in eoan
without installing tox from bionic, and a couple other packages not in
eoan (e.g. libcui60 dependency upstream, eoan has ...63). Had to add
these #pragmas which look memory related...
src/spdk/dpdk/lib/librte_eal/common/eal_common_memory.c:#pragma GCC diagnostic
warning "-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_eal/common/eal_common_memzone.c:#pragma GCC diagnostic
warning "-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_eal/common/eal_common_tailqs.c:#pragma GCC diagnostic
warning "-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_eal/common/malloc_heap.c:#pragma GCC diagnostic
warning "-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_eal/common/rte_malloc.c:#pragma GCC diagnostic warning
"-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_eal/linuxapp/eal/eal_memalloc.c:#pragma GCC diagnostic
warning "-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_eal/linuxapp/eal/eal_memory.c:#pragma GCC diagnostic
warning "-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_eal/linuxapp/eal/eal_vfio.c:#pragma GCC diagnostic
warning "-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_eal/linuxapp/eal/eal_vfio.h:#pragma message("VFIO
configured but not supported by this kernel, disabling.")
src/spdk/dpdk/lib/librte_ethdev/rte_tm.c:#pragma GCC diagnostic warning
"-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_ethdev/ethdev_profile.c:#pragma GCC diagnostic warning
"-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_ethdev/rte_ethdev.c:#pragma GCC diagnostic warning
"-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_ethdev/rte_flow.c:#pragma GCC diagnostic warning
"-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_ethdev/rte_mtr.c:#pragma GCC diagnostic warning
"-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_mempool/rte_mempool.c:#pragma GCC diagnostic warning
"-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_net/rte_arp.c:#pragma GCC diagnostic warning
"-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_net/rte_net.c:#pragma GCC diagnostic warning
"-Waddress-of-packed-member"
src/spdk/dpdk/lib/librte_ring/rte_ring.c:#pragma GCC diagnostic warning
"-Waddress-of-packed-member"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842020
Title:
ceph patch as of 8/29 segfaults all bluestore osds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
The above data is from a run in an eoan VM on the same processor that hosts the osd's in the baremetal layer (same bug in both cases, but I reverted the baremetal layer to the state prior to the 'upgrade' to restore ceph osd function). Here's the dpkg -l you asked for. Here's cat /proc/cpuinfo on the VM processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel Celeron_4x0 (Conroe/Merom Class Core 2) stepping: 3 microcode : 0x1 cpu MHz : 2327.284 cache size : 16384 KB physical id : 0 siblings: 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx lm constant_tsc rep_good nopl cpuid tsc_known_freq pni vmx ssse3 cx16 x2apic tsc_deadline_timer hypervisor lahf_lm cpuid_fault pti tpr_shadow vnmi flexpriority tsc_adjust arat arch_capabilities bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs bogomips: 4654.56 clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel Celeron_4x0 (Conroe/Merom Class Core 2) stepping: 3 microcode : 0x1 cpu MHz : 2327.284 cache size : 16384 KB physical id : 1 siblings: 1 core id : 0 cpu cores : 1 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx lm constant_tsc rep_good nopl cpuid tsc_known_freq pni vmx ssse3 cx16 x2apic tsc_deadline_timer hypervisor lahf_lm cpuid_fault pti tpr_shadow vnmi flexpriority tsc_adjust arat arch_capabilities bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs bogomips: 4654.56 clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ** Attachment added: "list of packages installed on system with crashes." https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+attachment/5285813/+files/dpkg-l.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
Backtrace log for you. ** Attachment added: "backtrace log" https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+attachment/5285808/+files/gdb-ceph-bluestore-tool.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
Attached is the result of apport-bug --save it can be viewed with apport-unpack It has the answers to most of the above questions. Yes, it is amd64 (dual xeon...) ** Attachment added: "result of apport-bug" https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+attachment/5285804/+files/_usr_bin_ceph-bluestore-tool.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
Bisected the problem starts with 14.2.2-0ubuntu1, might be the next one. It works in 14.2.1-0ubuntu3. Look for the change in the file size of ceph-bluestore-osd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842020] Re: ceph patch as of 8/29 segfaults all bluestore osds
Confirmed on two different boxes of the same processor vintage. Otherwise latest eoan updates. Desktop ceph mate though it shouldn't matter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842020 Title: ceph patch as of 8/29 segfaults all bluestore osds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1842020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
