[Bug 1913900] Re: Reset of USB device leads to GPF in cdc_acm kernel module
Kai-Heng Feng: The full dmesg output is already part of the ticket. However, I've now also included the latest crash as an attachment. The issue happened again tonight. When the crash happens, the system loses the ability to write to the filesystem(s). Specifically, if you type 'sync' in a window, it will hang. ** Attachment added: "dmesg output caused by resetting the RED-V board - leads to system hang" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913900/+attachment/5464649/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913900 Title: Reset of USB device leads to GPF in cdc_acm kernel module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913900] [NEW] Reset of USB device leads to GPF in cdc_acm kernel module
Public bug reported: Ubuntu 20.04 system, and a SparkFun RED-V RISC-V devboard attached via USB. Software used includes SEGGER J-Link (proprietary) and /opt/riscv- bin/riscv32-unknown-elf-gdb from the riscv github repo. With a 'gdb remote' connection established, via the JLink software, pressing the RESET button on the devboard leads to a GPF in the cdc_acm kernel module. The machine doesn't go dowdn instantly, but becomes progressively more unusable after that (e.g. ssh login hangs after password prompt, unlocking from screensaver leads to a black screen, but no desktop. Usually a reset is required because the system will fail to properly shut down. Although this description still lacks some precision, the effect is very reproducible. A USB device, and software without any special privileges, should not be able to destabilize the system. Jan 30 13:24:46 crunchy kernel: [ 4839.033113] cdc_acm 1-8.3:1.0: failed to set dtr/rts Jan 30 13:24:46 crunchy kernel: [ 4839.045325] xhci_hcd :00:14.0: WARN Cannot submit Set TR Deq Ptr Jan 30 13:24:46 crunchy kernel: [ 4839.045329] xhci_hcd :00:14.0: A Set TR Deq Ptr command is pending. Jan 30 13:24:46 crunchy kernel: [ 4839.046417] general protection fault: [#1] SMP PTI Jan 30 13:24:46 crunchy kernel: [ 4839.046430] CPU: 5 PID: 55103 Comm: kworker/5:3 Tainted: P OE 5.4.0-65-generic #73-Ubuntu Jan 30 13:24:46 crunchy kernel: [ 4839.046435] Hardware name: System manufacturer System Product Name/PRIME Z270M-PLUS, BIOS 1205 05/14/2018 Jan 30 13:24:46 crunchy kernel: [ 4839.046451] Workqueue: events acm_softint [cdc_acm] Jan 30 13:24:46 crunchy kernel: [ 4839.046465] RIP: 0010:usb_clear_halt+0x1d/0xc0 Jan 30 13:24:46 crunchy kernel: [ 4839.046474] Code: 85 f6 75 e8 c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 89 f0 48 89 e5 41 54 49 89 fc 53 89 f3 c1 fb 0f 83 e3 0f 48 83 ec 08 <8b> 37 c1 e6 08 81 ce 00 00 00 80 a8 80 74 44 68 88 13 00 00 80 cb Jan 30 13:24:46 crunchy kernel: [ 4839.046480] RSP: 0018:b4523f1e3e18 EFLAGS: 00010296 Jan 30 13:24:46 crunchy kernel: [ 4839.046487] RAX: c0408780 RBX: 0001 RCX: 92bbe148 Jan 30 13:24:46 crunchy kernel: [ 4839.046493] RDX: 0001 RSI: c0408780 RDI: 9b444bbb6b70a4de Jan 30 13:24:46 crunchy kernel: [ 4839.046498] RBP: b4523f1e3e30 R08: 0108 R09: 98c5b6b46068 Jan 30 13:24:46 crunchy kernel: [ 4839.046503] R10: 8a0a R11: R12: 9b444bbb6b70a4de Jan 30 13:24:46 crunchy kernel: [ 4839.046508] R13: 98c5b6b70700 R14: 98c3e5537000 R15: 98c3d454be40 Jan 30 13:24:46 crunchy kernel: [ 4839.046515] FS: () GS:98c5b6b4() knlGS: Jan 30 13:24:46 crunchy kernel: [ 4839.046520] CS: 0010 DS: ES: CR0: 80050033 Jan 30 13:24:46 crunchy kernel: [ 4839.046526] CR2: 7efd6d25f020 CR3: 000fa64e8005 CR4: 003606e0 Jan 30 13:24:46 crunchy kernel: [ 4839.046531] DR0: DR1: DR2: Jan 30 13:24:46 crunchy kernel: [ 4839.046537] DR3: DR6: fffe0ff0 DR7: 0400 Jan 30 13:24:46 crunchy kernel: [ 4839.046540] Call Trace: Jan 30 13:24:46 crunchy kernel: [ 4839.046556] acm_softint+0x65/0xf0 [cdc_acm] Jan 30 13:24:46 crunchy kernel: [ 4839.046570] process_one_work+0x1eb/0x3b0 Jan 30 13:24:46 crunchy kernel: [ 4839.046580] worker_thread+0x4d/0x400 Jan 30 13:24:46 crunchy kernel: [ 4839.046591] kthread+0x104/0x140 Jan 30 13:24:46 crunchy kernel: [ 4839.046600] ? process_one_work+0x3b0/0x3b0 Jan 30 13:24:46 crunchy kernel: [ 4839.046607] ? kthread_park+0x90/0x90 Jan 30 13:24:46 crunchy kernel: [ 4839.046619] ret_from_fork+0x35/0x40 Jan 30 13:24:46 crunchy kernel: [ 4839.046627] Modules linked in: cdc_acm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) intel_rapl_msr zlua(PO) snd_hda_codec_hdmi mei_hdcp intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_seq_midi kvm snd_seq_midi_event snd_hda_intel snd_intel_dspcfg snd_rawmidi rapl snd_hda_codec intel_cstate snd_hda_core snd_hwdep eeepc_wmi asus_wmi sparse_keymap wmi_bmof mxm_wmi snd_pcm snd_seq snd_seq_device snd_timer input_leds joydev snd mei_me soundcore mei nvidia_uvm(OE) mac_hid acpi_pad sch_fq_codel coretemp parport_pc ppdev parport ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor Jan 30 13:24:46 crunchy kernel: [ 4839.046733] raid6_pq libcrc32c raid0 multipath linear hid_generic usbhid hid uas usb_storage raid1 nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE)
[Bug 1862602] Re: Better document how to listen on the network
Ideally, the gpsd.socket unit would parse the defaults file and enable this transparently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862602 Title: Better document how to listen on the network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1862602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1826405] Re: Repeatedly "storage error [503 Inconsistent file state], last errno: File exists
Hi Steve, On 8/15/19 11:04 PM, Steve Dodd wrote: > acng seems totally broken in bionic. I'm not knowingly behind a proxy - > can't completely rule out ISP doing something evil though. Anyone have > any pointers on this? Very few google hits, nothing on bugs.debian.org > that I can see, very little activity for acng on salsa.debian.org .. Could you perhaps be a bit more specific in the bug tracker about how it is totally broken? It works fine for us (on Bionic), with the workarounds noted in this bug, and in https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1771914 Regards, Paul Boven. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826405 Title: Repeatedly "storage error [503 Inconsistent file state], last errno: File exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1826405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792860] Re: do-release-upgrade error
Ubuntu now uses https to connect to changelogs.ubuntu.com (LP: #1744318) When using ACNG, this causes two things to break: do-release-upgrade tries to download from changelogs.ubuntu.com via https, and fails The daily release-upgrade-motd fails to connect to changelogs.ubuntu.com, and generates the error message "Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings" As proposed in LP: #1771914, it would be good to add this setting to the default acng.conf on Ubuntu: PassThroughPattern: ^changelogs.ubuntu.com:443$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792860 Title: do-release-upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1792860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771914] Re: release-upgrade-motd can't update message via apt proxy
Using https for changelogs.ubuntu.com breaks both release-update-motd, and ubuntu-release-upgrader-core, when apt-cacher-ng is being used. The solution in #15 worked for me, and I support the suggestion to add this statement to the default apt-cacher-ng configuration, as it takes a while to figure out what's going wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771914 Title: release-upgrade-motd can't update message via apt proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1771914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826405] Re: Repeatedly "storage error [503 Inconsistent file state], last errno: File exists
Further analysis shows that this problem is due to a fun interaction
between lighttpd an ACNG. We use lighttpd to serve a local Debian/Ubuntu
package repository. In about half the cases where we run 'apt update',
it will fail with error 503 on the 'Release' file of such a repository.
What happens is:
1) Client asks ACNG for a new file. ACNG downloads it, serves it to the
client, adds it to /var/cache/apt-cacher-ng/
2) Subsequent requests for this file will work as expected
3) If the file hasn't been requested for a while, ACNG will run
'fileitem::DoDelayedUnregAndCheck'
4) The file is still in /var/cache/apt-cacher-ng/, but ACNG
has forgotten about it. A new request will fail with error 503 because
ACNG detects the file being in the cache ('Inconsistent File State').
ACNG deletes the file in question, and the next request will work.
This only happens if there is no 'Last Modified' HTTP header sent by
lighttpd. I've modified the lighttpd.conf to add this header, and ACNG
no longer gives the '503 Inconsistent File State' error.
Lighttpd.conf addition (from https://www.anexia-it.com/blog/en/the-tale-
of-lighttpd-not-sending-the-last-modified-header/ ):
mimetype.assign += ("" => "application/octet-stream" )
This still seems like a bug in ACNG, but this work-around might be
useful for some.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826405
Title:
Repeatedly "storage error [503 Inconsistent file state], last errno:
File exists
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1826405/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826405] [NEW] Repeatedly "storage error [503 Inconsistent file state], last errno: File exists
Public bug reported: Since upgrading to Bionic (18.04) our apt-cacher-ng often reports this error in its log: "storage error [503 Inconsistent file state], last errno: File exists" This results in the client not being served the file in question, and 'apt update' failing. The problem happens especially often with some 'local' repositories, where the 'Release' file sometimes gets cached properly, and moments later, is not available anymore on the next 'apt update' run. And a few minutes later, the file may be available again. Running acng with 'Debug: 7' results in this: Returning to last state, 6 Decoded request URI: http://install/Xenial-16.04-amd64/binary/Release Processing new job, GET http://install/Xenial-16.04-amd64/binary/Release HTTP/1.1 Download started, storeHeader for install/Xenial-16.04-amd64/binary/Release, current status: 1 install/Xenial-16.04-amd64/binary/Release storage error [503 Inconsistent file state], last errno: File exists Response header to be sent in the next cycle: HTTP/1.1 503 Inconsistent file state Content-Length: 145 Content-Type: text/html Date: Thu Apr 25 13:02:08 2019 Server: Debian Apt-Cacher NG/3.1 X-Original-Source: http://install/Xenial-16.04-amd64/binary/Release Connection: Keep-Alive A few minutes later (from the same client, and without restarting acng, it works again: Returning to last state, 6 Decoded request URI: http://install/Xenial-16.04-amd64/binary/Release Processing new job, GET http://install/Xenial-16.04-amd64/binary/Release HTTP/1.1 Download started, storeHeader for install/Xenial-16.04-amd64/binary/Release, current status: 1 Response header to be sent in the next cycle: HTTP/1.1 200 OK Content-Length: 1658 Content-Type: application/octet-stream Date: Thu Apr 25 13:04:30 2019 Server: Debian Apt-Cacher NG/3.1 X-Original-Source: http://install/Xenial-16.04-amd64/binary/Release Connection: Keep-Alive apt policy apt-cacher-ng: apt-cacher-ng: Installed: 3.1-1build1 Candidate: 3.1-1build1 lsb_release -rd: Description:Ubuntu 18.04.2 LTS Release:18.04 The apt-cacher-ng is running on a virtual machine, with the above configuration. There is plenty of diskspace available. The problem even occurs after removing acng, clearing /var/cache/apt-cacher-ng/, and re- installing the package. ** Affects: apt-cacher-ng (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/1826405 Title: Repeatedly "storage error [503 Inconsistent file state], last errno: File exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1826405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666900] Re: avahi-autoipd fails because network interface name is too long
Happened to connect my Pi Zero through a hub today. The interface name on the PC becomes "enp0s26u1u3u3i1" which itself is already 15 characters, so no room at all to append a label. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666900 Title: avahi-autoipd fails because network interface name is too long To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1666900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1350932] Re: Installation error message: egrep: character class syntax is [[:space:]], not [:space:]
Nowadays (Ubuntu 16.04), the shipped version of adjtimex is 1.29-7, which has this bug fixed. Closing the bug. ** Changed in: adjtimex (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/1350932 Title: Installation error message: egrep: character class syntax is [[:space:]], not [:space:] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adjtimex/+bug/1350932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666900] [NEW] avahi-autoipd fails because network interface name is too long
Public bug reported: Trying to use avahi-autoipd on a USB network interface, which gets created when I connect a USB gadget (g_ether) device (my raspberry pi zero). Avahi-autoipd fails to assign an IPv4LL address, and instead reports: # avahi-autoipd enp0s29u1u2 Found user 'avahi-autoipd' (UID 110) and group 'avahi-autoipd' (GID 120). Successfully called chroot(). Successfully dropped root privileges. Starting with address 169.254.7.125 Callout BIND, address 169.254.7.125 on interface enp0s29u1u2 client: RTNETLINK answers: Numerical result out of range Script execution failed with return value 2 Successfully claimed IP address 169.254.7.125 Although avahi-autoipd claims that the IP address gets configured, ifconfig shows that it didn't succeed. The root cause is that the label for the interface exceeds the maximum length of 15 characters. This happens in line 44 of /etc/avahi/avahi- autoipd.action: ip addr add "$3"/16 brd 169.254.255.255 label "$2:avahi" scope link dev "$2" With $2 the interface name, and $3 the IPv4LL address that it wants to claim. Interface names and label names can only be 15 characters in length, this is a kernel limitation. IF_NAMESIZE = 16, leaving 15 chars for the name, see /usr/include/net/if.h and IFNAMSIZ in the kernel includes. The rather long interface name, appended with ":avahi", exceeds this length. This results in the 'Numerical result out of range' error message. Workaround: I've edited the /etc/avahi/avahi-autopid.action script to only append ":a" for the label (lines 44 and 50) ,and in this case it works as designed. avahi-autoipd should perhaps check that the label does not exceed this limit of 15 characters. Note that the label must start with the full interface name, see ip- address(8). A more compact interface name would be helpful, as these long interface names tend to break other things as well. The kernel assigns 'usb0', but this gets changed right away. This occurs on both 16.04 and 16.10, haven't tried any other versions yet. ** Affects: avahi (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/1666900 Title: avahi-autoipd fails because network interface name is too long To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1666900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609666] Re: fail2ban is too severe when pam_unix + pam_ldap are used together
A successful login subsequently emits this log entry: Dec 20 17:53:36 REDACTED sshd[1281]: Accepted password for REDACTED from REDACTED port 40684 ssh2 A failed (password) login attempt however adds this log entry: Dec 20 18:18:24 REDACTED sshd[1393]: pam_ldap: error trying to bind as user "uid=REDACTED,ou=people,dc=REDACTED,dc=REDACTED" (Invalid credentials) In the LDAP+PAM case, fail2ban is now triggering on an entry added by upstream in April 2015: "Added line to match sshd auth errors on OpenSuSE systems" https://github.com/fail2ban/fail2ban/commit/8825a5f31b984fe52f705df6cec4720c9c1f0beb Perhaps the proper solution would be to create a multi-line match here, that only triggers if the same IP and hostname does not have a subsequent 'Accepted password' entry? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609666 Title: fail2ban is too severe when pam_unix + pam_ldap are used together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1609666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1513913] [NEW] ZFS pool does not get mounted on reboot
Public bug reported: Release: Ubuntu 15.10 Package versions: zfs-dkms: 0.6.4.2-0ubuntu1 zfsutils-linux: 0.6.4.2-0ubuntu1 mountall: 2.54ubuntu1 Installed the native ZFS packages that ship with Wily, and created a ZFS pool. Upon reboot, the pool is not mounted, a manual 'zfs import' is required. It is expected that the system mounts the pool(s) again after a reboot. Presumably this is caused by the 'mountall' package not having been updated to support ZFS (as it is in the ZFS -on-Linux PPA). See also: http://zfsonlinux.org/faq.html#HowDoIAutomaticallyMountZFSFilesystemsDuringStartup ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1513913 Title: ZFS pool does not get mounted on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1513913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1513917] [NEW] zfs-dkms is missing dependency on build-essential
Public bug reported: Release: 15.10 Wily Werewolf Package versions: zfs-dkms: 0.6.4.2-0ubuntu1 On a newly installed machine, I did 'apt-get install zfs-dkms zfsutils- linux'. Expected: To have the ZFS kernel module and utilities installed. Result: failed, due to compiler etc. not being installed. It's probably sufficient to add a dependency on build-essential to the zfs-dkms package. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1513917 Title: zfs-dkms is missing dependency on build-essential To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1513917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325606] Re: grub-installer fails on disks 26th (restrictive shell pattern)
Ran into this when installing Ubuntu 14.04 on a SuperMicro 847 (36 disks + 2 SataDOMS for the OS), so just commenting to say this is not a merely hypothetical situation. The SataDoms end up at /dev/sdak and /de/sdal. Applying the 'sed' workaround from the description worked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325606 Title: grub-installer fails on disks 26th (restrictive shell pattern) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1325606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
Andrey: the bug also occurs when not using '--copy-storage-inc'. I originally encountered the bug on a pair of servers that share a glusterfs filesystem. As part of the debugging effort, I took glusterfs out of the equation to show that it is not the cause of the issue. My test envirement is therefore currently setup with --copy-storage-inc, but my production environment uses glusterfs, and has the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
Another test with NTP disabled on the servers (but enabled on the guest): Still running qemu-git-2.1.0-rc2-git-20140721 server-a:~$ ntpdate -q cl0 stratum 3, offset -29.405612, delay 0.02597 server-b$ ntpdate -q cl0 stratum 3, offset -32.990292, delay 0.02597 The guest is running NTP, hosted on server-b for more than 10 days. Its NTP reports:. ntp.drift=-35.387 ppm. This matches the offset of server-b (32.99 seconds in 10 days, 19h21) very well: -35.33 ppm. Doing a live migration of the guest from server-b to server-a: Guest does not hang at all (NTP offset after migration: 0.38s). So if NTP is not running on the hosts, then there are no issues with the guest, it seems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
As another test (still running qemu-git-2.1.0-rc2-git-20140721), I disabled NTP on the two servers (and rebooted them), but left it running on the guest. When doing the migration, server a (where the guest was running) had an NTP offset of -3.037619 s, and server b was at -3.337718 s. The guest was nicely synchronized before the migration, but afterwards had a clock offset of 0.349590 s, which roughly corresponds to the difference in offsets. The small NTP offset on the guest after the migration implies that it did briefly freeze, but too short to notice. I'll leave it running for longer to be able to confirm this with sufficient accuracy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1350932] [NEW] Installation error message: egrep: character class syntax is [[:space:]], not [:space:]
Public bug reported: When installing adjtimex, this error is thrown: Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for man-db (2.6.7.1-1) ... Setting up adjtimex (1.29-2.2) ... egrep: character class syntax is [[:space:]], not [:space:] Regulating system clock...done. The egrep error is a know bug, that just got fixed in Debian. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630812 I'd suggest taking the updated Debian version of adjtimex. I ran into this on trusty, but this version of adjtimes (1.29-2.2) is available in precise, raring and saucy as well. Utopic (14.10) already includes the updated Debian version (1.29-3). ** Affects: adjtimex (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/1350932 Title: Installation error message: egrep: character class syntax is [[:space:]], not [:space:] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adjtimex/+bug/1350932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
** Also affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1297218/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349920] [NEW] ledmon does not work in Ubuntu 14.04
Public bug reported: ledmon will not work in Ubuntu 14.04, due to a change in kernel 3.13. I've tested this with ICH10R and C600/X79 chipset. Symptoms: ledctl gives 'enclosure management not supported' on supported hardware. This problem has just been fixed by upstream, see this patch: http://sourceforge.net/p/ledmon/code/ci/6f7d38bbe5d7b13c84987cf3b3b550a11c39392e/ Please update the Ubuntu package to include this patch, so ledmon works again. Installed package: ledmon 0.79-0.2 ~$ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 ** Affects: ledmon (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/1349920 Title: ledmon does not work in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1349920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
** Also affects: qemu 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/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
I've installed the latest virt-daily-upstream yesterday, and tried a migration today. Result: guest froze for 3.6 seconds after only 1 day of uptime, exactly the behaviour as seen with the stock Ubuntu-14.04 packages. So with qemu-git-2.1.0-rc2-git-20140721, the migration problem is back. This is not completely unexpected, as upstream recently reverted the patches that were supposed to fix this: http://lists.gnu.org/archive/html/qemu-devel/2014-05/msg00508.html http://lists.gnu.org/archive/html/qemu-devel/2014-07/msg02866.html http://lists.gnu.org/archive/html/qemu-devel/2014-07/msg02864.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
Using the packages from the virt-daily-upstream PPA, as suggested in
#16, seems to resolve the issue: there are no detectable hangs after a
live migration, and the clock offset afterwards is only 0.13s, where it
used to be 2.3s for the same amount of uptime.
$ dpkg -l \*qemu\* |awk '/^ii/{print $2 \t$3}'
ipxe-qemu 1.0.0+git-2013.c3d1e78-2ubuntu1
qemu2.0~git-20140609.959e41-0ubuntu1
qemu-keymaps2.0.0+dfsg-2ubuntu1.1
qemu-system 2.0~git-20140609.959e41-0ubuntu1
qemu-system-arm 2.0~git-20140609.959e41-0ubuntu1
qemu-system-common 2.0~git-20140609.959e41-0ubuntu1
qemu-system-mips2.0~git-20140609.959e41-0ubuntu1
qemu-system-misc2.0~git-20140609.959e41-0ubuntu1
qemu-system-ppc 2.0~git-20140609.959e41-0ubuntu1
qemu-system-sparc 2.0~git-20140609.959e41-0ubuntu1
qemu-system-x86 2.0~git-20140609.959e41-0ubuntu1
qemu-user 2.0~git-20140609.959e41-0ubuntu1
qemu-utils 2.0~git-20140609.959e41-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297218
Title:
guest hangs after live migration due to tsc jump
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1297218/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
In the production setup, we have two KVM servers. According to NTP, their clock corrections are: server-a: -147.2 ppm server-b: -142.1 ppm NTP is running on the guest as well, and it's drift-rate matches whichever server the guest is running on, after NTP has had time to adjust. The length of time that the guest freezes is exactly the time since the last migration, times the NTP rate of the server it is on. I did two migrations, one at 11h30, and another at 14h10, so 9600 seconds between migrations. The freeze after the second migration was 1.369s (as reported by ntpdate -q server-a, right after the migration). This 9600 seconds, times the 142.1 ppm of the server it was on, would predict a freeze of 1.364 s. I will set up a pair of machines with the qemu PPA later this week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
I've repeated the experiment without any shared storage, so that eliminates GlusterFS as a suspect. server-a# virsh migrate --live --persistent --undefinesource --copy- storage-inc guest qemu+tls://server-b/system Result: After about a week of uptime, the guest froze solid for 27 seconds after the migration. This is after the migration, because the guest is running on the destination server, using up a full core, and not present on the originating server anymore. CPU usage goes back to normal once the guest becomes responsive again. Just before the migration, NTP was perfectly locked to well within 100us. Right after the machine become responsive again, this NTP status shows the machine simply lost more than 27 seconds: root@guest:~# ntpq -p remote refid st t when poll reach delay offset jitter == *cl0 xx.xx.xx.xx 3 u 15 16 3770.457 27388.3 0.100 cl1 xx.xx.xx.xx 3 u 13 16 3770.429 27388.4 0.178 root@guest:~# uptime 16:03:30 up 8 days, 23:45, 1 user, load average: 0.02, 0.02, 0.05 During these 27 seconds, it did not respond to any network activity or (virtual) console. There is no mention of clock-jumps or anything else in dmesg this time. Note that I have now reproduced this on two different pairs of machines: our original KVM cluster, and two compute nodes (different hardware) to test this with a supported Ubuntu release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
After some deliberation on what shared storage to use, I decided to take that factor out of the equation alltogether: server-a# virsh migrate --live --persistent --undefinesource --copy- storage-inc guest qemu+tls://server-b/system So the storage is now on a non-shared directory and copied across before the VM is migrated. This works, so I'm going to have it accrue uptime for a week or so again, to see how the clock behaves on migration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
I've just done a migration on my test setup, on a guest having 21 days of uptime. Result: The guest froze for 53 seconds, then went happily on its way again. The 'TSC unstable' message did not show up, but ntp shows that the machine is now 53 seconds behind. The physical hosts have no NTP timing error. I'm not sure how gluster could cause this post-migration freeze. I'll rebuild the test-setup to run on a different clustered filesystem and will try again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
I've set up a test environment using Ubuntu 14.04 LTS on two servers. These are running glusterfs as a shared filesystem (3.5.0 from semiosis' PPA), connected through QDR infiniband as a backend. Live migrating a guest (also running 14.04 LTS) after a few days of uptime still leads to a clock jump: [Fri May 16 14:12:37 2014] Clocksource tsc unstable (delta = 85707222 ns) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
I've tried running apport, but it says 'no packages found matching libvirt' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1297218/+attachment/4113905/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] RelatedPackageVersions.txt
apport information ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/1297218/+attachment/4113906/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
apport information ** Tags added: apparmor apport-collected trusty ** Description changed: We have two identical Ubuntu servers running libvirt/kvm/qemu, sharing a Gluster filesystem. Guests can be live migrated between them. However, live migration often leads to the guest being stuck at 100% for a while. In that case, the dmesg output for such a guest will show (once it recovers): Clocksource tsc unstable (delta = 662463064082 ns). In this particular example, a guest was migrated and only after 11 minutes (662 seconds) did it become responsive again. It seems that newly booted guests doe not suffer from this problem, these can be migrated back and forth at will. After a day or so, the problem becomes apparent. It also seems that migrating from server A to server B causes much more problems than going from B back to A. If necessary, I can do more measurements to qualify these observations. The VM servers run Ubuntu 13.04 with these packages: Kernel: 3.8.0-35-generic x86_64 Libvirt: 1.0.2 Qemu: 1.4.0 Gluster-fs: 3.4.2 (libvirt access the images via the filesystem, not using libgfapi yet as the Ubuntu libvirt is not linked against libgfapi). The interconnect between both machines (both for migration and gluster) is 10GbE. Both servers are synced to NTP and well within 1ms form one another. Guests are either Ubuntu 13.04 or 13.10. On the guests, the current_clocksource is kvm-clock. The XML definition of the guests only contains: clock offset='utc'/ - Now as far as I've read in the documentation of kvm-clock, it - specifically supports live migrations, so I'm a bit surprised at these - problems. There isn't all that much information to find on these issue, - although I have found postings by others that seem to have run into the - same issues, but without a solution. + Now as far as I've read in the documentation of kvm-clock, it specifically supports live migrations, so I'm a bit surprised at these problems. There isn't all that much information to find on these issue, although I have found postings by others that seem to have run into the same issues, but without a solution. + --- + ApportVersion: 2.14.1-0ubuntu3 + Architecture: amd64 + DistroRelease: Ubuntu 14.04 + Package: libvirt (not installed) + ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=1b0c3c6d-a9b8-4e84-b076-117ae267d178 ro console=ttyS1,115200n8 BOOTIF=01-00-25-90-75-b5-c8 + ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 + Tags: trusty apparmor apparmor apparmor apparmor apparmor + Uname: Linux 3.13.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + modified.conffile..etc.default.libvirt.bin: [modified] + modified.conffile..etc.libvirt.libvirtd.conf: [modified] + modified.conffile..etc.libvirt.qemu.conf: [modified] + modified.conffile..etc.libvirt.qemu.networks.default.xml: [deleted] + mtime.conffile..etc.default.libvirt.bin: 2014-05-12T19:07:40.020662 + mtime.conffile..etc.libvirt.libvirtd.conf: 2014-05-13T14:40:25.894837 + mtime.conffile..etc.libvirt.qemu.conf: 2014-05-12T18:58:27.885506 ** Attachment added: KernLog.txt https://bugs.launchpad.net/bugs/1297218/+attachment/4113904/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313740] [NEW] config/database.yml.example is missing
Public bug reported: Trying to install the redmine pacakge on a machine (VM) with 14.04 LTS. Did not want to use dbconf as we already have a working database set up. After installation, there is no file /usr/share/redmine/config/database.yml.example which should be copied to database.yml and edited. The database.yml is also absent. root@jrm:/usr/share/redmine/config# apt-cache policy redmine redmine: Installed: 2.4.2-1 Candidate: 2.4.2-1 ** Affects: redmine (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/1313740 Title: config/database.yml.example is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redmine/+bug/1313740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1040177] Re: slapd install fails when requesting to 'Omit OpenLDAP server configuration
Still the same error with Trusty when installing the OpenLDAP (slapd) package. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1040177 Title: slapd install fails when requesting to 'Omit OpenLDAP server configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1040177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1040177] Re: slapd install fails when requesting to 'Omit OpenLDAP server configuration
Still the same error with Trusty when installing the OpenLDAP (slapd) package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1040177 Title: slapd install fails when requesting to 'Omit OpenLDAP server configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1040177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] Re: guest hangs after live migration due to tsc jump
These servers will be upgraded to 14.04LTS once that's released, I'll update the ticket accordingly once we've tested this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297218] [NEW] guest hangs after live migration due to tsc jump
Public bug reported: We have two identical Ubuntu servers running libvirt/kvm/qemu, sharing a Gluster filesystem. Guests can be live migrated between them. However, live migration often leads to the guest being stuck at 100% for a while. In that case, the dmesg output for such a guest will show (once it recovers): Clocksource tsc unstable (delta = 662463064082 ns). In this particular example, a guest was migrated and only after 11 minutes (662 seconds) did it become responsive again. It seems that newly booted guests doe not suffer from this problem, these can be migrated back and forth at will. After a day or so, the problem becomes apparent. It also seems that migrating from server A to server B causes much more problems than going from B back to A. If necessary, I can do more measurements to qualify these observations. The VM servers run Ubuntu 13.04 with these packages: Kernel: 3.8.0-35-generic x86_64 Libvirt: 1.0.2 Qemu: 1.4.0 Gluster-fs: 3.4.2 (libvirt access the images via the filesystem, not using libgfapi yet as the Ubuntu libvirt is not linked against libgfapi). The interconnect between both machines (both for migration and gluster) is 10GbE. Both servers are synced to NTP and well within 1ms form one another. Guests are either Ubuntu 13.04 or 13.10. On the guests, the current_clocksource is kvm-clock. The XML definition of the guests only contains: clock offset='utc'/ Now as far as I've read in the documentation of kvm-clock, it specifically supports live migrations, so I'm a bit surprised at these problems. There isn't all that much information to find on these issue, although I have found postings by others that seem to have run into the same issues, but without a solution. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1297218/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1297218] [NEW] guest hangs after live migration due to tsc jump
Public bug reported: We have two identical Ubuntu servers running libvirt/kvm/qemu, sharing a Gluster filesystem. Guests can be live migrated between them. However, live migration often leads to the guest being stuck at 100% for a while. In that case, the dmesg output for such a guest will show (once it recovers): Clocksource tsc unstable (delta = 662463064082 ns). In this particular example, a guest was migrated and only after 11 minutes (662 seconds) did it become responsive again. It seems that newly booted guests doe not suffer from this problem, these can be migrated back and forth at will. After a day or so, the problem becomes apparent. It also seems that migrating from server A to server B causes much more problems than going from B back to A. If necessary, I can do more measurements to qualify these observations. The VM servers run Ubuntu 13.04 with these packages: Kernel: 3.8.0-35-generic x86_64 Libvirt: 1.0.2 Qemu: 1.4.0 Gluster-fs: 3.4.2 (libvirt access the images via the filesystem, not using libgfapi yet as the Ubuntu libvirt is not linked against libgfapi). The interconnect between both machines (both for migration and gluster) is 10GbE. Both servers are synced to NTP and well within 1ms form one another. Guests are either Ubuntu 13.04 or 13.10. On the guests, the current_clocksource is kvm-clock. The XML definition of the guests only contains: clock offset='utc'/ Now as far as I've read in the documentation of kvm-clock, it specifically supports live migrations, so I'm a bit surprised at these problems. There isn't all that much information to find on these issue, although I have found postings by others that seem to have run into the same issues, but without a solution. ** Affects: libvirt (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/1297218 Title: guest hangs after live migration due to tsc jump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1297218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986412] Re: Need to add support for PDF Portfolios
Evince doesn't always work. I'm currently trying to read the HP Procurve Release Notes of a switch we have, and the PDF will only give the 'upgrade to acrobat 9' image, and there is only one thumbnail at the left, that leads back to this image. Acrobat 9 itself meanwhile only shows a completly black page, so is also no use. The only way I could actually read the document was by using pdf2ps and the gv. Try the 'Release Notes' link at the top of this page: https://h10145.www1.hp.com/downloads/SoftwareReleases.aspx?ProductNumber=J9641A -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986412 Title: Need to add support for PDF Portfolios To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/986412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365300] Re: Randomly I get double clicks when I do a single click.
My Logitech mouse (B110) has started to give me double instead of single clicks when using the left mouse button, and the problem has been getting worse for a few months. Webbrowsing became quite annoying, because every time you click 'back', the browser woudl go back two pages. This seems mostly a hardware problem, although other OS-es might handle the situation a bit better. My solution: I opened the mouse and put two small pieces of yellow Post- it note on top of the two switches for the mouse buttons, and closed the mouse again. The extra thickness ensures that the microswitche contacts move enough to prevent contact bounce. It now works 100% reliably again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/365300 Title: Randomly I get double clicks when I do a single click. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/365300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249395] [NEW] Tree view fails, Fatal error: Cannot redeclare password_hash()
Public bug reported: This is likely an incompatibility with PHP5.5 as included in Saucy, where password_hash is now an internal function. How to reproduce: on a working LAM install, click on the Tree View button on the top row. Instead of showing the tree view, it reports the error message below: Fatal error: Cannot redeclare password_hash() in /usr/share/ldap- account-manager/templates/3rdParty/pla/lib/functions.php on line 2085 ~$ lsb_release -rd Description:Ubuntu 13.10 Release:13.10 ~$ apt-cache policy ldap-account-manager ldap-account-manager: Installed: 4.2.1-2 Candidate: 4.2.1-2 ** Affects: ldap-account-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/1249395 Title: Tree view fails, Fatal error: Cannot redeclare password_hash() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldap-account-manager/+bug/1249395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090002] Re: biosdevname gives name of device as rename7 in Quantal
Server configuration: SuperMicro X9DRi-F mainboard On-board dual I350 (rev 01) Gigabit Ethernet controller [8086:1521], igb driver PCI-E X540-AT2 (rev01) 10Gbase-T Ethernet card [8086:1528], ixgbe driver. bios: Version 2.0a, 03/27/2013 The current situation causes two issues: 1.) The former interface p2p2 is now consistently named 'rename3'. 2.) There's a delay of more than a minute during the boot process, where nothing happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090002 Title: biosdevname gives name of device as rename7 in Quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090002] Re: biosdevname gives name of device as rename7 in Quantal
Same problem on two identical machines that have dual 1Gb/s ethernet cards on the motherboard. This apparently causes booting to stall for about a minute, see this snippet from syslog after a boot. These timestamps are while the machine is booting, and hasn't gotten to the point where it presents a login prompt. Sep 27 15:48:31 cl1 ntpd[1432]: new interface(s) found: waking up resolver Sep 27 15:49:54 cl1 udevd[691]: error changing net interface name rename3 to p2p1: File exists That interface really shouldn't be renamed to p2p1 though! BIOS device: p2p2 Kernel name: rename3 Permanent MAC: 00:25:90:64:6D:E9 Assigned MAC : 00:25:90:64:6D:E9 ifIndex: 3 Driver: igb Driver version: 4.1.2-k Firmware version: 1.96, 0x890e Bus Info: :02:00.1 PCI name : :02:00.1 PCI Slot : 2 Index in slot: 2 Machines are running Raring Ringtail 3.8.0.31 (patches updated today, didn't have this issue previously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090002 Title: biosdevname gives name of device as rename7 in Quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090002] Re: biosdevname gives name of device as rename7 in Quantal
Hi Narinder, Well, that's exactly the problem - sometime during the boot, apparently biosdev thought it was p2p1, and the OS tried to assign the name p2p1 to it, which it had already given out. When I run biosdev now, it shows up as being p2p2 allright - but the interface doesn't get assigned the name p2p2 during boot anymore, and instead I have an unexpected interface name 'rename3' show up in my ifconfig. Which breaks things quite badly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090002 Title: biosdevname gives name of device as rename7 in Quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090002] Re: biosdevname gives name of device as rename7 in Quantal
Ugh, I also just noticed that this messes up the order of my interfaces in SNMP - it's swapped the two ones, so now my graphs that used to show the external interfaces, are showing the internal ones, and v.v. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090002 Title: biosdevname gives name of device as rename7 in Quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205075] Re: mountall doesn't treat glusterfs correctly
Running into the same issue here, I can't get glusterfs to mount at boot. System: Ubuntu 13.04 Output from mountall --verbose: mount /export/brick0 [2508] exited normally Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT] or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT] Try `glusterfs --help' or `glusterfs --usage' for more information. mount /gluster [2509] exited normally The 'exited normally' seems wrong, too. Output from mountall --verbose --debug: run_mount: mtab /gluster spawn: mount -f -t fuse.glusterfs -o defaults localhost:/gv0 /gluster spawn: mount /gluster [2599] Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT] or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT] Try `glusterfs --help' or `glusterfs --usage' for more information. mount /gluster [2599] exited normally My fstab entry: localhost:/gv0 /glusterglusterfs defaults,nobootwait 0 0 It seems that mountall tries to emit mount -f -t fuse.glusterfs, which fails. mount -f -t glusterfs (with the same arguments) does work, but I can find no documentation on mountall and where it could have decided to prepend the 'fuse' part. Note that I have /sbin/mount.glusterfs, which is not part of Ubuntu but from a PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205075 Title: mountall doesn't treat glusterfs correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1205075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 782116] Re: Package OpenNTPd does not install
Bug still exists in Raring (13.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/782116 Title: Package OpenNTPd does not install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openntpd/+bug/782116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159770] [NEW] debconf configuration for SSL/TLS is missing in ldap-auth-config
Public bug reported: The file /etc/ldap.conf contains the settings for LDAP authentication. The recommended way of configuring this file and LDAP authentication, is through debconf. However, there is no way to specify whether TLS or SSL must be used for LDAP authentication, and without this setting, the user passwords will be sent in cleartext over the network. Release: Ubuntu 12.04.2 LTS Version: ldap-auth-config: Installed: 0.5.3 Expected: To be able to set up secure LDAP authentication through debconf Instead: Configuring that TLS or SSL is required, is not possible. This also means that it cannot be preseeded during automated installs. To enable TLS or SSL, the /etc/ldap.conf must contain ssl start_tls' or 'ssl on' as appropriate. These are available already in the file, but currently commented out. These can be failry easily brought under debconf control, would only require a new question in control/Templates, and code in control/postinst. ** Affects: ldap-auth-client (Ubuntu) Importance: Undecided Status: New ** Description changed: The file /etc/ldap.conf contains the settings for LDAP authentication. The recommended way of configuring this file and LDAP authentication, is through debconf. However, there is no way to specify whether TLS or SSL must be used for LDAP authentication, and without this setting, the user passwords will be sent in cleartext over the network. Release: Ubuntu 12.04.2 LTS Version: ldap-auth-config: Installed: 0.5.3 Expected: To be able to set up secure LDAP authentication through debconf Instead: Configuring that TLS or SSL is required, is not possible. This also means that it cannot be preseeded during automated installs. To enable TLS or SSL, the /etc/ldap.conf must contain ssl start_tls' or 'ssl on' as appropriate. These are available already in the file, but - currently commented out. These can be failry easyily brought under + currently commented out. These can be failry easily brought under debconf control, would only require a new question in control/Templates, and code in control/postinst. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159770 Title: debconf configuration for SSL/TLS is missing in ldap-auth-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldap-auth-client/+bug/1159770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159770] Re: debconf configuration for SSL/TLS is missing in ldap-auth-config
Corrected name of package: the actual configuration is done in ldap- auth-config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159770 Title: debconf configuration for SSL/TLS is missing in ldap-auth-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldap-auth-client/+bug/1159770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159770] Re: debconf configuration for SSL/TLS is missing in ldap-auth-config
Upstream bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432537 ** Bug watch added: Debian Bug tracker #432537 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432537 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159770 Title: debconf configuration for SSL/TLS is missing in ldap-auth-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldap-auth-client/+bug/1159770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159770] Re: debconf configuration for SSL/TLS is missing in ldap-auth-config
Proposal patch to enable configuring SSL through debconf. ** Patch added: ldap-auth-config_sever-ssl.patch https://bugs.launchpad.net/ubuntu/+source/ldap-auth-client/+bug/1159770/+attachment/3596385/+files/ldap-auth-config_sever-ssl.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159770 Title: debconf configuration for SSL/TLS is missing in ldap-auth-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldap-auth-client/+bug/1159770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1149931] [NEW] 12.04 openldap page TLS section is incorrect
Public bug reported: Bug report regarding this page: https://help.ubuntu.com/12.04/serverguide/openldap-server.html#openldap-tls The instructions tell to copy the CA-certificate to /etc/ssl/certs. This no longer works on 12.04. Instead the certificate should be renamed cacert.crt and placed in /usr/local/share/ca-certificates, then run update-ca-certificates, which will output: Updating certificates in /etc/ssl/certs... 1 added, 0 removed; done. ** Affects: ubuntu-docs (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/1149931 Title: 12.04 openldap page TLS section is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1149931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1072880] Re: grub fails to install on dmraid during upgrade to 12.10
Managed to get the system bootable again. From the rescue CD, I did these steps: Do NOT assemble any raids. Start a shell on the rescue root file system. Then: dmraid -ay mount /dev/mapper/isw_isw_cbfbcabehj_Volume0p1 /mnt mount -o bind /mnt/dev /dev mount -t proc none /mnt/chroot/proc chroot /mnt /bin/bash grub-install /dev/dm-0 reboot! (please note, the above commands were recreated from memory, but the main idea is that grub-install under chroot only works once you have access to /dev from the chroot environment). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072880 Title: grub fails to install on dmraid during upgrade to 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1072880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1072880] Re: grub fails to install on dmraid during upgrade to 12.10
Hi Philip, On 10/30/2012 09:22 PM, Phillip Susi wrote: Can you run sudo dpkg-reconfigure grub-pc and verify that /dev/mapper/isw_isw_cbfbcabehj_Volume0 is selected as the location to install to, and that you get no errors? When I run sudo dpkg-reconfigure grub-pc, I get: Configuring grub-pc. The grub-pc package is being ugpraded, this menu allows you to select which devices (etc.) It then provides a list of devices: /dev/sda, /dev/sdb (the hard drives themselves), /dev/mapper/isw_cbfbcabehj_Volume0 (the raid device for the full disk) and /dev/dm-1 (the mirrored root partition). None of these is highlighted. I can select the /dev/mapper/isw_(...)_Volume0, and then dpkg-reconfigure ends with Installation finished. No error reported. Generating grub.cfg... (and concludes with all the Linux kernel images it found). Regards, Paul Boven. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072880 Title: grub fails to install on dmraid during upgrade to 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1072880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1072880] [NEW] grub fails to install on dmraid during upgrade to 12.10
Public bug reported: During the upgrade from 12.04LTS to 12.10, grub reported the following errors: run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.2.0-30-generic /boot/vmlinuz-3.2.0-30-generic generating grub.cfg /usr/sbin/grub-probe: error: cannot find a GRUB driv for /dev/mapper/isw_cbfbcabehj_Volume0p1. Check your device.map. (repeated 34 more times). And a big popup: GRUB failed to install to the following devices: /dev/dm-0 Do you want to continue anyway? If you do your computer may not start up properly. Writing GRUB to boot device failed - continue? (I decided to continue, as the system already had a working grub, and there seemed no way out of the situation anyway) After reboot, the system is stuck in grub rescue and is currently unbootable. When booting from a rescue-USB, I can activate the fakeraid (Intel Matrix raid) with 'dmraid -ay' and can mount the root partition, but I am unable to put grub on it: grub-installer fails (cannot find device for /, /boot - grub installer clobbers much of its own output) /mnt/usr/sbin/grub-install fails (Cannot open /usr/share/grub/grub-mkconfig_lib) chroot /mnt grub-install fails (Path /boot/grub is not readable by GRUB on boot. Installation is impossible. Aborting) The system was originally installed, brand new, with 12.04 LTS (no other OS on it). DMraid was configured through the regular installer, I don't recall any grub issues back then. I'm happy to provide any additional information that's needed, but this might be difficult due to the system not being bootable. While running a chroot on /mnt (the dmraid-device with my original root filesystem) I get: lsb_release -rd: Description: Ubuntu 12.10, Release: 12.10 apt-cache policy grub2-common: Installed: 2.00-7ubuntu11, Candidate: 2.00-7ubuntu11 Recovery CD has kernel 3.2.0-32, target system has 3.5.0-32 on it but does not boot into that. Expected: a clean upgrade to 12.10 and being able to use the system again. What happened instead: system is currently unbootable, hangs in grub rescue, though no dataloss seems to have happened. I cannot even boot into an older kernel. ** Affects: grub2 (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/1072880 Title: grub fails to install on dmraid during upgrade to 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1072880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1040177] Re: slapd install fails when requesting to 'Omit OpenLDAP server configuration
I would say that the 'old' behaviour would be preferable if somoene choses to have an unconfigured slapd: Instead of failing to start the service, an empty slapd that is live and can be configured from the root account would be a bit more user-friendly. This seems to be how slapd was packaged in Ubuntu before, until the addition of an automatically populated tree recently. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1040177 Title: slapd install fails when requesting to 'Omit OpenLDAP server configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1040177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1040177] Re: slapd install fails when requesting to 'Omit OpenLDAP server configuration
I would say that the 'old' behaviour would be preferable if somoene choses to have an unconfigured slapd: Instead of failing to start the service, an empty slapd that is live and can be configured from the root account would be a bit more user-friendly. This seems to be how slapd was packaged in Ubuntu before, until the addition of an automatically populated tree recently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1040177 Title: slapd install fails when requesting to 'Omit OpenLDAP server configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1040177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1040177] [NEW] slapd install fails when requesting to 'Omit OpenLDAP server configuration
Public bug reported: Ubuntu slapd package now installs a default DIT. If one doesn't need this DIT, debconf question Omit OpenLDAP server configuration? (at prio low) gives the option to not install that, but then the package installation doesn't complete: Setting up slapd (2.4.28-1.1ubuntu4.1) ... Omitting slapd configuration as requested. * No configuration file was found for slapd at /etc/ldap/slapd.conf. invoke-rc.d: initscript slapd, action start failed. dpkg: error processing slapd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: slapd E: Sub-process /usr/bin/dpkg returned an error code (1) Expected: apt-get install to not give an error when requesting Omit OpenLDAP server configuration, and a 'clean' slapd with only the minimal required cn=config loaded so that it can then be configured as needed. # lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 # apt-cache policy slapd Installed: 2.4.28-1.1ubuntu4.1 Candidate: 2.4.28-1.1ubuntu4.1 ** Affects: openldap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1040177 Title: slapd install fails when requesting to 'Omit OpenLDAP server configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1040177/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1040177] [NEW] slapd install fails when requesting to 'Omit OpenLDAP server configuration
Public bug reported: Ubuntu slapd package now installs a default DIT. If one doesn't need this DIT, debconf question Omit OpenLDAP server configuration? (at prio low) gives the option to not install that, but then the package installation doesn't complete: Setting up slapd (2.4.28-1.1ubuntu4.1) ... Omitting slapd configuration as requested. * No configuration file was found for slapd at /etc/ldap/slapd.conf. invoke-rc.d: initscript slapd, action start failed. dpkg: error processing slapd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: slapd E: Sub-process /usr/bin/dpkg returned an error code (1) Expected: apt-get install to not give an error when requesting Omit OpenLDAP server configuration, and a 'clean' slapd with only the minimal required cn=config loaded so that it can then be configured as needed. # lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 # apt-cache policy slapd Installed: 2.4.28-1.1ubuntu4.1 Candidate: 2.4.28-1.1ubuntu4.1 ** Affects: openldap (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/1040177 Title: slapd install fails when requesting to 'Omit OpenLDAP server configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1040177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995877] [NEW] resolv.conf produces errors when postfix main.cfg is missing (regression of #530323)
Public bug reported: This seems to be a regression of #530323 on 12.04 LTS: # ifup eth0 /etc/resolvconf/update-libc.d/postfix: 7: /etc/resolvconf-update-libc.d/postfix: /usr/sbin/postconf: not found cp: '/etc/resolv.conf' and '/etc/resolv.conf' are the same file run-parts: /etc/resolvconf/update-libc.d/postfix exited with return code 1 run-parts: /etc/resolvconf/update.d/libc exited with return code 1 run-parts: /etc/network/if-up.d/000resolvconf exited with return code 1 ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: - This seems to be a regression of #530323: + This seems to be a regression of #530323 on 12.04 LTS: # ifup eth0 /etc/resolvconf/update-libc.d/postfix: 7: /etc/resolvconf-update-libc.d/postfix: /usr/sbin/postconf: not found cp: '/etc/resolv.conf' and '/etc/resolv.conf' are the same file run-parts: /etc/resolvconf/update-libc.d/postfix exited with return code 1 run-parts: /etc/resolvconf/update.d/libc exited with return code 1 run-parts: /etc/network/if-up.d/000resolvconf exited with return code 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995877 Title: resolv.conf produces errors when postfix main.cfg is missing (regression of #530323) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/995877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995877] Re: resolv.conf produces errors when postfix main.cfg is missing (regression of #530323)
** Package changed: ubuntu = resolvconf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995877 Title: resolv.conf produces errors when postfix main.cfg is missing (regression of #530323) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/995877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839172] Re: update-manager assert failure: *** glibc detected *** /usr/bin/python: double free or corruption (fasttop): 0x0abbd1d8 ***
Same crash as above in Xilinx tools 13.3 trce. Ubuntu 11.10 3.0.0-14-generic-pae #23-Ubuntu SMP Mon Nov 21 22:07:10 UTC 2011 i686 i686 i386 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839172 Title: update-manager assert failure: *** glibc detected *** /usr/bin/python: double free or corruption (fasttop): 0x0abbd1d8 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/839172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 756485] Re: [e1000e] Intel 82579V suffering from packet drop with e1000e 1.2.20
Confirming that this is a serious network problem. One of our machines has about 30% of packet loss, the other about 15%. The packet loss does not occur when the link is at 1Gb/s, but does occur at 100Mb/s (haven't tried 10Mb/s). lspci: 00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05) Workaround: install the up-to-date driver from Intel and then run update-initramfs -u. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/756485 Title: [e1000e] Intel 82579V suffering from packet drop with e1000e 1.2.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/756485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790538] Re: pam update causes cron to stop working with Module is unknown error
Just for the record: pulling the pam packages like this completely breaks the network-based install I'm doing from an official Ubuntu mirror, because of the 404-errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790538 Title: pam update causes cron to stop working with Module is unknown error -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 330285] [NEW] fv crashes with *** buffer overflow detected ***: /usr/bin/wish8.3 terminated
Public bug reported: Binary package hint: fv 1) $ lsb_release -rd Description:Ubuntu 8.10 Release:8.10 2) $ apt-cache policy fv fv: Installed: 3.0-17ubuntu1 Candidate: 3.0-17ubuntu1 Version table: *** 3.0-17ubuntu1 0 500 http://archive.ubuntu.com intrepid/universe Packages 100 /var/lib/dpkg/status 3) Expected: start up the fits-viewer 4) Happened instead: fv crashed on startup, might also be a problem with wish/tcl. $ fv *** buffer overflow detected ***: /usr/bin/wish8.3 terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7cbf548] /lib/tls/i686/cmov/libc.so.6[0xb7cbd670] /lib/tls/i686/cmov/libc.so.6(__fgets_chk+0x127)[0xb7cbd9b7] /usr/lib/fv/../fitsTcl/libfitstcl.so(isFitsCmd+0x19d)[0xb7b1f6aa] /usr/lib/libtcl8.3.so.1(TclInvokeStringCommand+0x6e)[0xb7e7277e] /usr/lib/libtcl8.3.so.1(TclExecuteByteCode+0xb48)[0xb7e94f68] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0x1c5)[0xb7e73b05] /usr/lib/libtcl8.3.so.1(Tcl_SwitchObjCmd+0x2d1)[0xb7e7f281] /usr/lib/libtcl8.3.so.1(TclExecuteByteCode+0xb48)[0xb7e94f68] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0x1c5)[0xb7e73b05] /usr/lib/libitcl3.1.so.1(Itcl_EvalMemberCode+0x38a)[0xb7b5139a] /usr/lib/libitcl3.1.so.1(Itcl_ExecMethod+0xf2)[0xb7b523e2] /usr/lib/libtcl8.3.so.1(TclExecuteByteCode+0xb48)[0xb7e94f68] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0x1c5)[0xb7e73b05] /usr/lib/libitcl3.1.so.1(Itcl_EvalMemberCode+0x38a)[0xb7b5139a] /usr/lib/libitcl3.1.so.1(Itcl_ExecMethod+0xf2)[0xb7b523e2] /usr/lib/libtcl8.3.so.1(TclExecuteByteCode+0xb48)[0xb7e94f68] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0x1c5)[0xb7e73b05] /usr/lib/libitcl3.1.so.1(Itcl_EvalMemberCode+0x38a)[0xb7b5139a] /usr/lib/libitcl3.1.so.1(Itcl_ExecMethod+0xf2)[0xb7b523e2] /usr/lib/libitcl3.1.so.1(Itcl_EvalArgs+0x78)[0xb7b5a7b8] /usr/lib/libitcl3.1.so.1(Itcl_HandleInstance+0x18f)[0xb7b53ecf] /usr/lib/libtcl8.3.so.1(TclExecuteByteCode+0xb48)[0xb7e94f68] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0x1c5)[0xb7e73b05] /usr/lib/libtcl8.3.so.1(TclObjInterpProc+0x34a)[0xb7ebeada] /usr/lib/libtcl8.3.so.1(TclExecuteByteCode+0xb48)[0xb7e94f68] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0x1c5)[0xb7e73b05] /usr/lib/libitcl3.1.so.1(Itcl_EvalMemberCode+0x38a)[0xb7b5139a] /usr/lib/libitcl3.1.so.1(Itcl_InvokeMethodIfExists+0xb9)[0xb7b51529] /usr/lib/libitcl3.1.so.1(Itcl_CreateObject+0x453)[0xb7b54b83] /usr/lib/libitcl3.1.so.1(Itcl_HandleClass+0x13f)[0xb7b4971f] /usr/lib/libtcl8.3.so.1[0xb7eb6a5a] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjv+0x9f)[0xb7eb6e6f] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0x290)[0xb7e73bd0] /usr/lib/libtcl8.3.so.1(Tcl_UplevelObjCmd+0x126)[0xb7ebf296] /usr/lib/libtcl8.3.so.1(TclExecuteByteCode+0xb48)[0xb7e94f68] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0x1c5)[0xb7e73b05] /usr/lib/libtcl8.3.so.1(TclObjInterpProc+0x34a)[0xb7ebeada] /usr/lib/libtcl8.3.so.1[0xb7eb6a5a] /usr/lib/libtcl8.3.so.1[0xb7eb6c00] /usr/lib/libtcl8.3.so.1(Tcl_EvalEx+0x2f1)[0xb7eb8441] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0xa3)[0xb7e739e3] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjCmd+0x62)[0xb7e7a972] /usr/lib/libtcl8.3.so.1(TclExecuteByteCode+0xb48)[0xb7e94f68] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0x1c5)[0xb7e73b05] /usr/lib/libtcl8.3.so.1(TclObjInterpProc+0x34a)[0xb7ebeada] /usr/lib/libtcl8.3.so.1[0xb7eb6a5a] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjv+0x9f)[0xb7eb6e6f] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0x290)[0xb7e73bd0] /usr/lib/libtcl8.3.so.1(Tcl_UplevelObjCmd+0x126)[0xb7ebf296] /usr/lib/libtcl8.3.so.1(TclExecuteByteCode+0xb48)[0xb7e94f68] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0x1c5)[0xb7e73b05] /usr/lib/libtcl8.3.so.1(TclObjInterpProc+0x34a)[0xb7ebeada] /usr/lib/libtcl8.3.so.1[0xb7eb6a5a] /usr/lib/libtcl8.3.so.1[0xb7eb6c00] /usr/lib/libtcl8.3.so.1(Tcl_EvalEx+0x2f1)[0xb7eb8441] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjEx+0xa3)[0xb7e739e3] /usr/lib/libtcl8.3.so.1(Tcl_EvalObjCmd+0x62)[0xb7e7a972] /usr/lib/libtcl8.3.so.1[0xb7eb6a5a] /usr/lib/libtcl8.3.so.1(Tcl_EvalEx+0x2f1)[0xb7eb8441] /usr/lib/libtcl8.3.so.1(Tcl_EvalFile+0x284)[0xb7eacdb4] /usr/lib/libtk8.3.so.1(Tk_MainEx+0x379)[0xb7f1e979] /usr/bin/wish8.3(main+0x4b)[0x804893b] === Memory map: 08048000-08049000 r-xp 08:01 1285519/usr/bin/wish8.3 08049000-0804a000 r--p 08:01 1285519/usr/bin/wish8.3 0804a000-0804b000 rw-p 1000 08:01 1285519/usr/bin/wish8.3 08805000-08a4 rw-p 08805000 00:00 0 [heap] b7874000-b7881000 r-xp 08:01 8765467/lib/libgcc_s.so.1 b7881000-b7882000 r--p c000 08:01 8765467/lib/libgcc_s.so.1 b7882000-b7883000 rw-p d000 08:01 8765467/lib/libgcc_s.so.1 b789a000-b789b000 rw-p b789a000 00:00 0 b789b000-b79ed000 r-xp 08:01 1278754/usr/lib/libcfitsio.so.3.080 b79ed000-b79ee000 r--p 00152000 08:01 1278754/usr/lib/libcfitsio.so.3.080 b79ee000-b79f rw-p 00153000 08:01 1278754/usr/lib/libcfitsio.so.3.080 b79f-b7a65000 rw-p b79f 00:00 0 b7a65000-b7a9f000 rw-p b7a9f000 00:00 0 b7aba000-b7af5000 r-xp 08:01 1789267
