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 {
--- 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
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:
** 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
** 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
Public bug reported:
openstack-pkg-tools (24) unstable; urgency=medium
* Added tooling for sbuild.
* Uploading to unstable.
-- Thomas Goirand z...@debian.org Fri, 17 Apr 2015 10:48:33 +0200
openstack-pkg-tools (23) experimental; urgency=medium
* Reviewed long description.
* Added
** 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
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
** 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)
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-5.6 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
This bug was fixed in the package python-saharaclient - 0.8.0-1
Sponsored for Artur Rona (ari-tczew)
---
python-saharaclient (0.8.0-1) unstable; urgency=medium
* New upstream release.
* Uploading to unstable.
* Reviewed (build-)depends for this release.
-- Thomas Goirand
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
13 matches
Mail list logo
