[Bug 1641124] [NEW] Default failback value is badly chosen
Public bug reported: As described by: https://help.ubuntu.com/lts/serverguide/multipath-setting-up-dm- multipath.html The default value for failback is set to manual, instead of immediate. This effectively breaks the idea of multipath, which allows for upgrading E.G SAN A side, then upgrade B side when A is complete. With this set to manual, the system effectively halts. With a system containing 4 paths to a block device, you'll see this in logs during SAN firmware upgrade: November 11th 2016, 13:58:05.0003 systemd dev-disk-by\x2did-wwn\x2d0x600a098038303731702b486638665456.device: Dev dev-disk-by\x2did-wwn\x2d0x600a098038303731702b486638665456.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/:03:00.0/:04:02.0/:07:00.0/host0/rport-0:0-4/target0:0:3/0:0:3:0/block/sde and /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/:03:00.0/:04:02.0/:07:00.0/host0/rport-0:0-2/target0:0:1/0:0:1:0/block/sda November 11th 2016, 13:58:05.0003 systemd dev-disk-by\x2did-scsi\x2d3600a098038303731702b486638665456.device: Dev dev-disk-by\x2did-scsi\x2d3600a098038303731702b486638665456.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/:03:00.0/:04:02.0/:07:00.0/host0/rport-0:0-4/target0:0:3/0:0:3:0/block/sde and /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/:03:00.0/:04:02.0/:07:00.0/host0/rport-0:0-2/target0:0:1/0:0:1:0/block/sda November 11th 2016, 13:58:05.0003 systemd dev-disk-by\x2did-scsi\x2d3600a098038303731702b486638665456.device: Dev dev-disk-by\x2did-scsi\x2d3600a098038303731702b486638665456.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/:03:00.0/:04:03.0/:08:00.0/host7/rport-7:0-1/target7:0:0/7:0:0:0/block/sdc and /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/:03:00.0/:04:02.0/:07:00.0/host0/rport-0:0-2/target0:0:1/0:0:1:0/block/sda November 11th 2016, 13:58:05.0004 kernel [585264.496735] sd 0:0:1:0: Asymmetric access state changed November 11th 2016, 13:58:05.0003 systemd dev-disk-by\x2did-scsi\x2d3600a098038303731702b486638665456.device: Dev dev-disk-by\x2did-scsi\x2d3600a098038303731702b486638665456.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/:03:00.0/:04:03.0/:08:00.0/host7/rport-7:0-1/target7:0:0/7:0:0:0/block/sdc and /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/:03:00.0/:04:02.0/:07:00.0/host0/rport-0:0-2/target0:0:1/0:0:1:0/block/sda November 11th 2016, 13:58:05.0003 systemd dev-disk-by\x2did-wwn\x2d0x600a098038303731702b486638665456.device: Dev dev-disk-by\x2did-wwn\x2d0x600a098038303731702b486638665456.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/:03:00.0/:04:03.0/:08:00.0/host7/rport-7:0-1/target7:0:0/7:0:0:0/block/sdc and /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/:03:00.0/:04:02.0/:07:00.0/host0/rport-0:0-2/target0:0:1/0:0:1:0/block/sda November 11th 2016, 13:58:05.0003 systemd dev-disk-by\x2did-wwn\x2d0x600a098038303731702b486638665456.device: Dev dev-disk-by\x2did-wwn\x2d0x600a098038303731702b486638665456.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/:03:00.0/:04:03.0/:08:00.0/host7/rport-7:0-1/target7:0:0/7:0:0:0/block/sdc and /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/:03:00.0/:04:02.0/:07:00.0/host0/rport-0:0-2/target0:0:1/0:0:1:0/block/sda With the end result that the filesystem is no longer available. If the root partition is on a multipath device (SAN device), then /bin etc. are gone. Suggested fix: Set failback to immediate as default value This would ensure that what you would expect to happen, actually happens - which is when you upgrade SAN firmware, machines continue running like nothing happened due to redundant paths ** Affects: multipath-tools (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/1641124 Title: Default failback value is badly chosen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1641124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598759] Re: incomplete apparmor definition for ntpd
I am suffering from a similar issue, but with slightly different behavior # journalctl -u ntp Oct 11 10:23:29 lys-stats ntp[5670]: * Starting NTP server ntpd Oct 11 10:23:29 lys-stats ntpd[5681]: ntpd 4.2.8p4@1.3265-o Wed Oct 5 12:34:45 UTC 2016 (1): Starting Oct 11 10:23:29 lys-stats ntp[5670]:...done. Oct 11 10:23:29 lys-stats systemd[1]: Started LSB: Start NTP daemon. Oct 11 10:23:29 lys-stats ntpd[5683]: proto: precision = 0.091 usec (-23) Oct 11 10:23:29 lys-stats ntpd[5683]: restrict 0.0.0.0: KOD does nothing without LIMITED. Oct 11 10:23:29 lys-stats ntpd[5683]: restrict ::: KOD does nothing without LIMITED. Oct 11 10:23:29 lys-stats ntpd[5683]: Listen and drop on 0 v6wildcard [::]:123 Oct 11 10:23:29 lys-stats ntpd[5683]: Listen and drop on 1 v4wildcard 0.0.0.0:123 Oct 11 10:23:29 lys-stats ntpd[5683]: ./../lib/isc/unix/ifiter_getifaddrs.c:99: unexpected error: Oct 11 10:23:29 lys-stats ntpd[5683]: getting interface addresses: getifaddrs: Permission denied Oct 11 10:23:29 lys-stats ntpd[5683]: unable to open routing socket (Permission denied) - using polled interface up Oct 11 10:23:31 lys-stats ntpd[5683]: ./../lib/isc/unix/ifiter_getifaddrs.c:99: unexpected error: Oct 11 10:23:31 lys-stats ntpd[5683]: getting interface addresses: getifaddrs: Permission denied # dmesg -T [Tue Oct 11 10:23:29 2016] audit: type=1400 audit(1476174209.696:24): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=5683 comm="ntpd" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" [Tue Oct 11 10:23:29 2016] audit: type=1400 audit(1476174209.700:25): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=5683 comm="ntpd" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" [Tue Oct 11 10:23:29 2016] audit: type=1400 audit(1476174209.700:26): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=5683 comm="ntpd" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" [Tue Oct 11 10:23:31 2016] audit: type=1400 audit(1476174211.356:27): apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=5683 comm="ntpd" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" # apt-cache policy apparmor apparmor: Installed: 2.10.95-0ubuntu2.2 Candidate: 2.10.95-0ubuntu2.2 Version table: *** 2.10.95-0ubuntu2.2 500 500 http://archive.ubuntu.com:80/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.10.95-0ubuntu2 500 500 http://archive.ubuntu.com:80/ubuntu xenial/main amd64 Packages # apt-cache policy ntp ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.3 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.3 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.3 500 500 http://archive.ubuntu.com:80/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.8p4+dfsg-3ubuntu5 500 500 http://archive.ubuntu.com:80/ubuntu xenial/main amd64 Packages # cat /etc/ntp.conf tinker panic 0 disable monitor restrict -4 default kod nomodify notrap nopeer noquery restrict -6 default kod nomodify notrap nopeer noquery restrict 127.0.0.1 restrict ::1 server pool.ntp.org iburst driftfile /var/lib/ntp/drift # cat /etc/apparmor.d/usr.sbin.ntpd # vim:syntax=apparmor # Updated for Ubuntu by: Jamie Strandboge# -- # #Copyright (C) 2002-2005 Novell/SUSE #Copyright (C) 2009-2012 Canonical Ltd. # #This program is free software; you can redistribute it and/or #modify it under the terms of version 2 of the GNU General Public #License published by the Free Software Foundation. # # -- #include #include /usr/sbin/ntpd { #include #include #include capability ipc_lock, capability net_bind_service, capability setgid, capability setuid, capability sys_chroot, capability sys_resource, capability sys_time, capability sys_nice, # ntp uses AF_INET, AF_INET6 and AF_UNSPEC network dgram, network stream, @{PROC}/net/if_inet6 r, @{PROC}/*/net/if_inet6 r, @{NTPD_DEVICE} rw, # pps devices are almost exclusively used with NTP /dev/pps[0-9]* rw, /{,s}bin/ r, /usr/{,s}bin/ r, /usr/sbin/ntpd rmix, /etc/ntp.conf r, /etc/ntp.conf.dhcp r, /etc/ntpd.conf r, /etc/ntpd.conf.tmp r, /var/lib/ntp/ntp.conf.dhcp r, /etc/ntp.keys r, /etc/ntp/** r, /etc/ntp.drift rwl, /etc/ntp.drift.TEMP rwl, /etc/ntp/drift* rwl, /var/lib/ntp/*drift rw, /var/lib/ntp/*drift.TEMP rw, /var/log/ntp w, /var/log/ntp.log w, /var/log/ntpd w, /var/log/ntpstats/clockstats* rwl, /var/log/ntpstats/loopstats* rwl, /var/log/ntpstats/peerstats* rwl, /var/log/ntpstats/protostats* rwl,
[Bug 1332440] Re: apt-get update very slow when ulimit -n is big
When running Ubuntu 14.04 inside Docker I've seen this issue with CentOS as well: CentOS 7.2 3.10.0-327.4.4.el7.x86_64 I tested a few kernels with Ubuntu 14.04 as host OS and I found: apt-get update extremely slow on kernels: 3.13.0-76 3.13.0-65 3.13.0-30 3.13.0-29 apt-get update fast on kernel: 3.13.0-45 So my workaround for now is to install and run kernel 3.13.0-45 My working setup is; # docker --version Docker version 1.9.1, build a34a1d5 # uname -a Linux lys-jenkins 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:36:28 UTC 2015 x86_64 x86_64 x86_64 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/1332440 Title: apt-get update very slow when ulimit -n is big To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1332440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332440] Re: apt-get update very slow when ulimit -n is big
Running apt-get update takes ~80 seconds for me running: * Virtualbox 4.3.12 * Ubuntu 14.04 LTS 64 bit desktop (3.13.0-30-generic #55-Ubuntu SMP) * Docker version 1.0.1, build 990021a * Official 'ubuntu:14.04' docker image In the VirtualBox machine it takes 10s Running a similar setup in VMware does not display this behavior: * VMware ESXi 5.5 * Ubuntu 14.04 LTS 64 bit server (3.13.0-30-generic #55-Ubuntu SMP) * Docker version 1.0.1, build 990021a apt-get executed in 9.87 seconds * Official 'ubuntu:14.04' docker image -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332440 Title: apt-get update very slow when ulimit -n is big To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1332440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 668415] Re: Movement of Unity launcher
Given the 290 comments before me, I realize I won't be adding anything new, but I wanted to share my frustration anyway, just to point out how annoying this is to a lot of people by pure volume of complaints. I have been using the unity-rotate plugin a while, but it has severe limitations, such as it only works in 3D and doesn't support 12.04. Why don't you believe in the freedom to choose? There's so many options with Ubuntu to choose how you want your desktop, E.G using KDE or something completely different. This tiny option, which affect so many peoples experience with Ubuntu as a whole should be configurable. Who are you to decide that my 90 degrees tilted widescreen obviously must have the launcher at the side? One size fits all, simply doesn't fit all. Setups differ, hardware differ - what makes sense on your setup, doesn't have to make sense elsewhere. Why don't you allow Windows users to have a tiny piece of familiar environment in Ubuntu? Coming from Windows to Ubuntu, or switching back and forth between Windows and Ubuntu (E.G virtualized) comes with a certain set of 'trained'/'built-in' mouse movements, such as 'drag to the lower left' which always hits start menu. In Unity, with the same logic, you close whatever window on top that is maximized when pulling to the upper left corner! Why mess with peoples heads? Most people have brains that are wired to read in a horizontal line. This skill is continuously improved while reading text. Getting an overview of running applications if you don't already have a mental image of this (which is the default, when launcher is hidden), you need to move your eyes down the line of the launcher - again inefficient and frustrating. - FRUSTRATED USER - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/668415 Title: Movement of Unity launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/668415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs