[Bug 1358835] Comment bridged from LTC Bugzilla
--- Comment From thierry.fa...@fr.ibm.com 2015-03-05 10:05 EDT---
Verified:
gcc test.c -ldl -o test
ubuntu@vm19:~$ ./test 80
80
cpu 80 belongs to node 2
ubuntu@vm19:~$ numactl -H
available: 4 nodes (0-3)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
node 0 size: 969 MB
node 0 free: 445 MB
node 1 cpus: 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61
62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
node 1 size: 1022 MB
node 1 free: 777 MB
node 2 cpus: 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120
121 122 123 124 125 126 127
node 2 size: 1022 MB
node 2 free: 37 MB
node 3 cpus: 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143
144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159
node 3 size: 1017 MB
node 3 free: 907 MB
node distances:
node 0 1 2 3
0: 10 40 40 40
1: 40 10 40 40
2: 40 40 10 40
3: 40 40 40 10
ubuntu@vm19:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
--- Comment From mainam...@in.ibm.com 2015-03-19 05:43 EDT---
The test described in the bug fails in Ubuntu 14.04.2.
The following packages were tried as well: libnuma1 2.0.9~rc5-1ubuntu3
and numactl 2.0.9~rc5-1ubuntu3
In all cases the test failed. The efix for 14.04.1 provided by Thierry
Fauck worked but it was not used in 14.04.02
--- Comment From mainam...@in.ibm.com 2015-03-25 10:41 EDT---
Any updates on this?
--- Comment From thierry.fa...@fr.ibm.com 2015-04-08 07:54 EDT---
Commit 573609fb2711b6c09090cc3fef9a771ae9eb246b sent to maintainers
>From 573609fb2711b6c09090cc3fef9a771ae9eb246b Mon Sep 17 00:00:00 2001
From: Thierry FAUCK - IBM LTC
Date: Tue, 7 Apr 2015 17:53:34 +0200
Subject: [PATCH] libnuma.so On ppc64el, cpu number are not contigous
Commit 32075635db57c3d5efe12f8fb569af857e01ccad issuea warning message
/sys not mounted when it find a non existent cpu number, and that's the
default for multinode on ppc64el bare metal installed system. This patch
removes the message when the /sys entry doesn't exist, but use the return
code.
Signed-off-by: Thierry FAUCK - IBM LTC
modified: libnuma.c
---
libnuma.c | 22 +-
1 file changed, 13 insertions(+), 9 deletions(-)
diff --git a/libnuma.c b/libnuma.c
index 3717d5b..98aa10f 100644
--- a/libnuma.c
+++ b/libnuma.c
@@ -1276,11 +1276,13 @@ numa_node_to_cpus_v1(int node, unsigned long *buffer,
int bufferlen)
sprintf(fn, "/sys/devices/system/node/node%d/cpumap", node);
f = fopen(fn, "r");
if (!f || getdelim(&line, &len, '\n', f) < 1) {
- numa_warn(W_nosysfs2,
- "/sys not mounted or invalid. Assuming one node: %s",
+ if (f) {
+ numa_warn(W_nosysfs2,
+ "/sys not mounted or invalid. Assuming one node: %s",
strerror(errno));
- numa_warn(W_nosysfs2,
- "(cannot open or correctly parse %s)", fn);
+ numa_warn(W_nosysfs2,
+ "(cannot open or correctly parse %s)", fn);
+ }
bitmask.maskp = (unsigned long *)mask;
bitmask.size = buflen_needed * 8;
numa_bitmask_setall(&bitmask);
@@ -1355,11 +1357,13 @@ numa_node_to_cpus_v2(int node, struct bitmask *buffer)
sprintf(fn, "/sys/devices/system/node/node%d/cpumap", node);
f = fopen(fn, "r");
if (!f || getdelim(&line, &len, '\n', f) < 1) {
- numa_warn(W_nosysfs2,
- "/sys not mounted or invalid. Assuming one node: %s",
- strerror(errno));
- numa_warn(W_nosysfs2,
- "(cannot open or correctly parse %s)", fn);
+ if (f) {
+ numa_warn(W_nosysfs2,
+ "/sys not mounted or invalid. Assuming one node: %s",
+ strerror(errno));
+ numa_warn(W_nosysfs2,
+ "(cannot open or correctly parse %s)", fn);
+ }
numa_bitmask_setall(mask);
err = -1;
}
--
1.7.9.5
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to numactl in Ubuntu.
https://bugs.launchpad.net/bugs/1358835
Title:
numa_node_of_cpu() returns warning when cpu_index > 79
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1358835/+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 1455985] Re: Merge openstack-pkg-tools 24 (main) from Debian unstable (main)
** Patch added: "ubuntu-ubuntu.debdiff" https://bugs.launchpad.net/ubuntu/+source/openstack-pkg-tools/+bug/1455985/+attachment/4399152/+files/ubuntu-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openstack-pkg-tools in Ubuntu. https://bugs.launchpad.net/bugs/1455985 Title: Merge openstack-pkg-tools 24 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openstack-pkg-tools/+bug/1455985/+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 1455985] [NEW] Merge openstack-pkg-tools 24 (main) from Debian unstable (main)
Public bug reported: openstack-pkg-tools (24) unstable; urgency=medium * Added tooling for sbuild. * Uploading to unstable. -- Thomas Goirand Fri, 17 Apr 2015 10:48:33 +0200 openstack-pkg-tools (23) experimental; urgency=medium * Reviewed long description. * Added build scripts and lots of utilities to automate building of OpenStack packages. -- Thomas Goirand Wed, 25 Feb 2015 21:56:24 +0100 openstack-pkg-tools (22) unstable; urgency=medium * Calls dh_installinit after dh_systemd_enable so that systemd services are started at install time. -- Thomas Goirand Thu, 08 Jan 2015 15:12:13 + ** Affects: openstack-pkg-tools (Ubuntu) Importance: Wishlist Status: Confirmed ** Changed in: openstack-pkg-tools (Ubuntu) Importance: Undecided => Wishlist ** Changed in: openstack-pkg-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openstack-pkg-tools in Ubuntu. https://bugs.launchpad.net/bugs/1455985 Title: Merge openstack-pkg-tools 24 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openstack-pkg-tools/+bug/1455985/+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 1455985] Re: Merge openstack-pkg-tools 24 (main) from Debian unstable (main)
** Patch added: "debian-ubuntu.debdiff" https://bugs.launchpad.net/ubuntu/+source/openstack-pkg-tools/+bug/1455985/+attachment/4399153/+files/debian-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openstack-pkg-tools in Ubuntu. https://bugs.launchpad.net/bugs/1455985 Title: Merge openstack-pkg-tools 24 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openstack-pkg-tools/+bug/1455985/+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 1455984] Re: package postfix 2.11.3-1ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 75
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1455984 Title: package postfix 2.11.3-1ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1455984/+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 1455984] [NEW] package postfix 2.11.3-1ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 75
Public bug reported: I might not choose the adequate configuration option. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: postfix 2.11.3-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 Date: Sun May 17 15:37:14 2015 DuplicateSignature: package:postfix:2.11.3-1ubuntu1:el subproceso instalado el script post-installation devolvió el código de salida de error 75 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 75 EtcMailname: yb-Ubuntu-14.0 Hostname: yb-Ubuntu-14.0 InstallationDate: Installed on 2015-05-11 (6 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) PostconfMydomain: localdomain PostconfMyhostname: yb-Ubuntu-14.0 PostconfMyorigin: /etc/mailname RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 ResolvConf: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.1.1 SourcePackage: postfix Title: package postfix 2.11.3-1ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 75 UpgradeStatus: Upgraded to vivid on 2015-05-11 (5 days ago) ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1455984 Title: package postfix 2.11.3-1ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 75 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1455984/+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 1455921] Re: nginx fails to start during boot or upgrade with hostnames in 'listen' or 'upstream' bind commands.
Unfortunately, this is a (common) race condition between nginx at boot and the system. It is also a common condition even when the system is running. There are cases where nginx fails to resolve hostnames where DNS resolvers don't know the information. It has been witnessed in the past but there is no way to fix it. >From the nginx-devel mailing list where i emailed on this issue with regards to boot-time observation/replication of this problem (http://mailman.nginx.org/pipermail/nginx-devel/2015-May/006944.html): Quote: Maxim Dounin To resolve names during configuration parsing nginx uses gethostbyname() or getaddrinfo() functions. It's up to the OS to provide appropriate service. That is, what you describe looks like a system startup race condition. I'm not really familiar with Debian/Ubuntu, but may be adding $named to Required-Start list in the init script will fix things. This applies to other cases as well when the system is already running and there is a hostname resolution failure due to DNS problems or DNS servers being out of date, or your systems having cached DNS data. An interesting case is when items are defined in /etc/hosts. This tends to 'work', but you lose the advantages of using a DNS server for the resolution. However, this is subject to the same system startup race conditions (observed on my own testing in 1.6.x, 1.7.x, and 1.8.x, and earlier versions of nginx as well.). ** Changed in: nginx (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1455921 Title: nginx fails to start during boot or upgrade with hostnames in 'listen' or 'upstream' bind commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1455921/+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 1455921] [NEW] nginx fails to start during boot or upgrade with hostnames in 'listen' or 'upstream' bind commands.
Public bug reported:
When upgrading nginx packages or booting with nginx configurations that
use `listen` statements or other types of bind locations such as these,
nginx sometimes fails to start because it cannot resolve the hostname:
upstream {
server http://someserver;
}
server {
listen myhostname:80;
# [...]
}
This can prevent package upgrades from working, and can prevent nginx from
loading at boot time.
-
Bug reporter notes: This issue has shown up numerous times both in
Ubuntu and Debian bugs and is consistently an issue on package
updates/upgrades. While we don't have any bugs as such filed here at
the current time that clearly meet this case, it is known that this does
cause some of the package update/upgrade/install bugs if configurations
matching this format exist in the configurations directories.
** Affects: nginx (Ubuntu)
Importance: Medium
Status: Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1455921
Title:
nginx fails to start during boot or upgrade with hostnames in 'listen'
or 'upstream' bind commands.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1455921/+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 1452451] Re: lxc-attach needs to mount a /proc for apparmor's use
Thanks again for opening this bug. A candidate fix has been sent to the lxc-devel mailing list. The workaround is to make sure that the lxc configuration mounts a procfs for the container, using either a lxc.mount.entry or lxc.mount.auto. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1452451 Title: lxc-attach needs to mount a /proc for apparmor's use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452451/+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 1448985] Re: Ubuntu 14.04 LTS, 14.10, 15.04 guests do not boot to Unity from QEMU-KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts
It still does not boot to Unity. If you can imagine black QEMU-KVM window - that is a screenshot. What logs do you want? ** Changed in: qemu (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1448985 Title: Ubuntu 14.04 LTS, 14.10, 15.04 guests do not boot to Unity from QEMU- KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1448985/+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 1448985] Re: Ubuntu 14.04 LTS, 14.10, 15.04 guests do not boot to Unity from QEMU-KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts
** Description changed:
STEPS TO REPRODUCE:
- 1. Install Ubuntu 14.04.2 LTS or Ubuntu 14.10 or Ubuntu 15.04 with all
updates (it is aubu host system).
+ 1. Install Ubuntu 14.04.2 LTS or Ubuntu 14.10 or Ubuntu 15.04 with all
updates (it is a host system).
2. Download one (or all) isos:
* Ubuntu 14.0.4.2 i386 iso (ubuntu-14.04.2-desktop-i386.iso, MD5SUM =
a8a14f1f92c1ef35dae4966a2ae1a264).
* Ubuntu 14.10 i386 iso (ubuntu-14.10-desktop-i386.iso, MD5SUM =
4a3c4b8421af51c29c84fb6f4b3fe109)
* Ubuntu 15.04 i386 iso (ubuntu-15.04-desktop-i386.iso, MD5SUM =
6ea04093b767ad6778aa245d53625612)
3. Boot one (or all) isos with as QEMU-KVM guest with the following
commands:
* sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso
* sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga std
* sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga vmware
* or from usb-creator-gtk via "Test disk" button
-4. Click on "Try Ubuntu"
+ 4. Click on "Try Ubuntu"
EXPECTED RESULTS:
ISO is booted to Unity desktop, user can test and use it.
ACTUAL RESULTS:
In 14.04 and 14.10 guests can see empty purple desktop or purple desktop
with two shortcuts ("Examples" and "Install Ubuntu ...").
15.10 guest does not boot or boot to safe graphic mode (it is bug 1437740).
This bug should be confirmed and fixed.
Users may want to run Ubuntu in QEMU/KVM, not just VirtualBox.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1448985
Title:
Ubuntu 14.04 LTS, 14.10, 15.04 guests do not boot to Unity from QEMU-
KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1448985/+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
