This bug was fixed in the package autopkgtest - 3.19.1
---
autopkgtest (3.19.1) unstable; urgency=medium
* adt-virt-qemu: If the executed command exits with 255, translate that to
253 in the auxverb wrapper, as 255 is the exit code for failures of the
auxverb itself. This
Public bug reported:
When logging on using a regular account with a non-encrypted home
directory vsftpd fails with the following lines written to the syslog:
Jan 13 11:00:31 shusaku vsftpd: pam_ecryptfs: Passphrase file wrapped
Jan 13 11:00:31 shusaku vsftpd: pam_ecryptfs: Unable to rewrap
what about Wily Werewolf?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1204530
Title:
yppasswd results in a segmentation fault when run on clients or server
To manage notifications
"This bug was fixed in the package nis - 3.17-34ubuntu3"
510 mirko@soppalco[12:41:19]:~$ dpkg -l nis
+++-==---=
ii nis3.17-32ubunt amd64clients and daemons for the Netwo
511 mirko@soppalco[12:42:19]:~$ sudo
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vlock in Ubuntu.
https://bugs.launchpad.net/bugs/1533621
Title:
package vlock 2.2.2-5 failed to install/upgrade: el subproceso
instalado el
Default Comment by Bridge
** Attachment added: "Console log from post-install boot on host nulp1"
https://bugs.launchpad.net/bugs/1526984/+attachment/4549221/+files/nulp1.boot.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
First of all thanks for checking the fix. and yes so far it is only
released for Xenial (16.04).
Given the time it was open and the amount of feedback we have got I
assumed it wouldn't be worth an SRU -
https://wiki.ubuntu.com/StableReleaseUpdates.
I'm still not sure if it is worth an SRU given
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1533679
Title:
package apache2 2.4.7-1ubuntu4.8 failed to install/upgrade: subprocess
> and then killing the system due to memory starvation
Actually I think tmpfs is limited to 50% of system RAM or something by
default, but that brings up another issue. By doing this we're severely
limiting the available disk in /tmp. Or does that not matter in the
cloud image case because / is
> * Performance - much faster read/write access to data in /tmp
Is this really true? Writes to /tmp will go to the page cache, which I
believe is an identical path whether /tmp is backed by disk or by tmpfs.
Similarly reads from /tmp will come from the page cache except where
pages have been
Public bug reported:
Hi,
I've an issue with ssh X11 forwarding while launching Java applications, it's a
critical issue because I'm working with my laptop(with Ubuntu 15.10) for a
customer and is impossible to dispatch all the requests.
This is what I do step by step:
1- ssh -X
I'd also add that the cloud image build process isn't the right place to
make such a change, I don't think. It should be cloud-init or some
system boot script that is shipped by a package in the archive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Public bug reported:
do-release-upgrade from 12.04 to 14.04 died
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: apache2 2.4.7-1ubuntu4.8
ProcVersionSignature: Ubuntu 3.2.0-89.127-generic 3.2.69
Uname: Linux 3.2.0-89-generic x86_64
Apache2ConfdDirListing: False
Apache2Modules:
Error:
Public bug reported:
dpkg: error al procesar el paquete vlock (--configure):
el subproceso instalado el script post-installation devolvió el código de
salida de error 1
Se encontraron errores al procesar:
vlock
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
You have been subscribed to a public bug by Ben Howard (utlemming):
In Ubuntu, we clear /tmp on every boot.
As such, on servers, by default /tmp should actually be a tmpfs entirely
in RAM.
This has several advantages, mainly:
* Performance - much faster read/write access to data in /tmp
*
** Summary changed:
- package apache2 2.4.7-1ubuntu4.8 failed to install/upgrade: aliprosessi
komentotiedosto post-installation asennettu palautti virhetilakoodin 1
+ package apache2 2.4.7-1ubuntu4.8 failed to install/upgrade: subprocess
post-installation script returned exit status 1
**
I looked into it more in detail - It is actually a bigger change than just
reusing what we did for Xenial.
Since for Xenial we did a lot of cleanup regarding upstart we can't just
"reuse" what we have for trusty.
--
You received this bug notification because you are a member of Ubuntu
Server
Never mind then!
https://twitter.com/zeevs/status/687241123467767808
...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1522422
Title:
Update to php 7.0
To manage notifications
Hello Masaki, or anyone else affected,
Accepted python-oslo.log into wily-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/python-
oslo.log/1.11.0-1ubuntu0 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Xenial, and vivid already have the solution for this.
Here is the debdiff with the solution for trusty.
I also took the liberty of uploading a build with this debdiff here in the
hopes that I might get some additional testing.
https://launchpad.net/~chiluk/+archive/ubuntu/1484696
** Patch
Public bug reported:
Server running ubuntu wily, kvm and a few virtual machines
Today installed security updates which contained a libvirt update. After
finishing the updates i found al my virtual machines were shutdown.
Previous libvirt updates did not shutdown running virtual machines.
**
** Changed in: irqbalance (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1454273
Title:
irqbalance should not run in container - add systemd
** Description changed:
- I have a set of servers that were transferred over to another maas
- servers so that the power credentials were no longer valid when back on
- our maas server. While to trying to get them working, I would see that
- check power state hangs because of the credentials
** Changed in: apache2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
Unable to connect to: ws://:/MAAS/ws
To manage
Tested that the apache fix appears to resolve the issue even after
removing the workaround from wolsen.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
Unable to
I checkd back that the message during update did not state that. In my
humble opinion it would be better if it would drop a note on that.
I only have the update text in german:
Veraltete Version 9.4
│
│ Die PostgreSQL-Version 9.4 ist veraltet, aber die Server-oder
│ Client-Pakete sind noch
Blueprint changed by Kick In:
Work items changed:
Work items for ubuntu-15.11:
[serge-hallyn] etckeeper: DONE
[paelzer] NIS merge: DONE
Work items for ubuntu-15.12:
[raharper] : tgt merge (bug 1524982): DONE
[racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
** Also affects: apache2 (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
Unable to connect to:
** Also affects: libvirt (Ubuntu Wily)
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/1531564
Title:
missing apparmor rule to read
Public bug reported:
I'n trying to get (unpriviliged) lxc containers to run on wily. I
create a container like this:
> lxc-create -t download -n u1 -- -d ubuntu -r wily -a amd64
that works. However, starting the container fails:
> lxc-start -n u1
** Changed in: openssh (Ubuntu Trusty)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: shadow (Ubuntu Trusty)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server
** Also affects: cinder (Juju Charms Collection)
Importance: Undecided
Status: New
** Also affects: glance (Ubuntu)
Importance: Undecided
Status: New
** Also affects: heat (Ubuntu)
Importance: Undecided
Status: New
** Also affects: neutron-openvswitch (Ubuntu)
systemd should be updated to know about the pids cgroup
** Also affects: lxc (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
**
(Note this should be properly handled in xenial, but needs fixing in
wily)
--
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/1533833
Title:
unprivileged lxc containers won't start
To
Public bug reported:
fix tests on s390x
** Affects: mysql-5.6 (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: New
** Tags: s390x
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1533992
Title:
package libnss3 2:3.19.2.1-0ubuntu0.14.04.1 failed to install/upgrade:
cannot copy
Public bug reported:
When starting Ubuntu a series of pop-up messages with:
"Sorry, Ubuntu 14.04 has experienced an internal error."
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libnss3 2:3.19.2.1-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.19.0-43.49~14.04.1-generic
Updated dep3 header information per arges' review.
** Patch removed: "lp1484696.trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1484696/+attachment/4549491/+files/lp1484696.trusty.debdiff
** Patch added: "lp1484696.trusty.debdiff"
Thanks Joe. I'll set this to Invalid accordingly.
** Changed in: strongswan (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to strongswan in Ubuntu.
https://bugs.launchpad.net/bugs/1357098
Any news on that one?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1357424
Title:
Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main)
To manage notifications about
@Joe, as mentioned by Robie, the ESP packets are generated by your
kernel using the key information provided and negociated by Strongswan.
There can be many reasons for the remote node to not reply to your ESP
packets. Most of the time, IPsec issues boil down to configuration/setup
problems.
You're using a newer kernel which provides the 'pids' cgroup. Systemd doesn't
know about that one and so doesn't create a cgroup for you that you own. Lxc
in turn (in wily) doesn't yet know how to handle that.
You can work around this several ways. The simplest is to do
sudo cgm create pids
@blake-rouse
After this fix is committed the maas team should strongly reconsider their
stance to disable the apache proxy on port 80.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
Thank you Simon and Robie. This is definitely a kernel issue. I didn't
realize that I was using a non-standard kernel, and when I switched to
hardware that used an Ubuntu supported kernel, everything worked fine.
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: juju-mongodb (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1271770
Title:
apply test fixes and run c++ unit tests
This bug was fixed in the package freeipmi - 1.4.11-1ubuntu1
---
freeipmi (1.4.11-1ubuntu1) xenial; urgency=low
* Merge from Debian unstable (LP: #1527685). Remaining changes:
- debian/rules: Build with "-pie,-bindnow"
- Use dh-autoreconf to update libtool for ppc64el.
This doesn't sound like a good idea to me, given the prevalence of
running Ubuntu on virtual machines with less than 4GB of RAM. I'm
thinking specifically of hosting providers like Linode, AWS,
DigitalOcean, etc., as well as tools like Vagrant, all of which are
extremely popular right now. Using
I'll work on getting the usptream fix SRU'd.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1484696
Title:
Unable to connect to: ws://:/MAAS/ws
To manage notifications about this
Public bug reported:
I try to create an external snapshot of a running VM to be able to
backup the machine.
I do the following:
virsh snapshot-create-as --domain Windows10Pro Snapshot3 --diskspec
hda,file=/data/snapshots/Windows10ProSnapshot3 --disk-only --atomic --quiesce
--no-metadata
** Changed in: corosync (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: corosync (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: corosync (Ubuntu Trusty)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
** Changed in: corosync (Ubuntu)
Assignee:
Those fixes are already included in corosync v2.3.4:
$ git tag --contains cc80c8567d6eec1d136f9e85d2f8dfb957337eef
v2.3.4
v2.3.5
$ git tag --contains 384760cb670836dc37e243f594612c6e68f44351
v2.3.4
v2.3.5
$ git tag --contains dfaca4b10a005681230a81e229384b6cd239b4f6
v2.3.4
v2.3.5
Waiting for the BUG to be sponsored.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1530837
Title:
Logsys file leaks in /dev/shm after sigabrt, sigsegv and when
BTW,
I provided a public PPA:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1530837
If anyone suffering from this is interested in having a hotfix while SRU
isn't ready.
Thank you
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Fix for Trusty.
** Patch added: "trusty_corosync_2.3.3-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+attachment/4549322/+files/trusty_corosync_2.3.3-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Attachment removed: "VarLogDistupgradeScreenlog0.gz"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1533679/+attachment/4549270/+files/VarLogDistupgradeScreenlog0.gz
** Attachment removed: "VarLogDistupgradeMainlog.gz"
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1530837
Title:
Logsys file leaks in /dev/shm
** Description changed:
+ [Impact]
+
+ * corosync has a memory leak problem with multiple calls to corosync -v
+ * corosync has a memory leak problem by not properly handling signals
+
+ [Test Case]
+
+ * run "corosync -v" multiple times
+ * some cloud tools do that
+
+ [Regression
> The big disadvantage of a tmpfs /tmp is that it cannot be paged out
My mistake, this is untrue if you have swap enabled (and enough swap
available). I was thinking of ramfs. I still wonder what any performance
gain would be, though. Using tmpfs will still limit size to available
RAM + available
Can we publish some test images? Instead of guessing at this, we can
benchmark this.
In general swapping ram-based for what is almost always disk-based is
going to impact applications/deployments using tmp and expecting enough
space there. It's not uncommon for large ISO or other image
** Bug watch added: Debian Bug tracker #803232
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803232
** Also affects: irqbalance (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803232
Importance: Unknown
Status: Unknown
--
You received this bug notification
Reported this upstream
https://github.com/Irqbalance/irqbalance/issues/27 - couldn't link it so
LP could track it though, don't know why.
** Also affects: irqbalance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Jeremy, have you had a chance to test the updated version(s)?
Thanks,
Nish
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1318317
Title:
openipmi startup script removes kernel
62 matches
Mail list logo
