A fix [1] in LXC was pushed recently and actually allows systemd daemon-
reexec without the cap sys_admin in a container.
We tested that it totally solved the issue for us.
Would it possible to move this bug report to the LXC project? And to ask for a
backport of such fix to Xenial LXC?
Thanks!
>From our analysis, we indeed agree with the fact that it has nothing to do
>with LXC (hence the report in the systemd tracker).
We believe that only the package is faulty here and should not attempt to
blindly reexec systemd on upgrade.
--
You received this bug notification because you are a
Public bug reported:
Dear all,
Following up the bug report #1713674, when executing systemd in a
hardened LXC context, it might not be suitable to reexec systemd daemon,
that would not be able to perform.
For instance, in our LXC, we drop several capabilities, including
sys_admin and we set
Public bug reported:
Dear all,
When trying to start an LXC container with Xenial on both host and
container, if sys_admin capability is dropped (lxc.cap.drop = sys_admin
in the config file), the container fails to start, because systemd fails
to mount the cgroup filesystem in the container. The
Dear all,
We have also faced such issue while migrating some servers from Ubuntu 14.04.5
to Ubuntu 16.04.3. Are there any plans to get a correct fix so that we can
properly plan our migration to Xenial?
Meanwhile, we used the workaround provided by Brian Candler - thanks! - which
works well.
Public bug reported:
Dear all,
All the G++ shipped with Ubuntu 14.04 (including the latest 4.8 package)
are suffering a bug from G++ in the C++11 implementation. It is not
possible to build code that contains variadic templates with variadic
lambda.
The bug was fixed upstream. Would it be
Public bug reported:
Dear all,
With the upgrade to GCC 4.9 packages that occurred recently on Trusty
(upgrading to 4.9.3-0ubuntu4), Vivid now provides an older GCC 4.9
release (4.9.2-10ubuntu13) [1].
The side effect of that thing is that it's not possible to upgrade from Trusty
to Vivid any
Affected by such bug on Ubuntu 14.04 LTS, which seems to be what the
original author reports in spite of what of the title reads.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1524743
Title:
Lucid
Tested 2.0.0+dfsg-2ubuntu1.18.
Cannot reproduce the issue.
TEST CASE 1:
Attempt several times to copy files on a VDI disk, and couldn't trigger any
corruption (nor deadlock - no regression). Given my test scenario, previously,
I would already have hit the corruption.
TEST CASE 2:
Tested with
Tested 2.0.0+dfsg-2ubuntu1.18.
Cannot reproduce the issue.
TEST CASE 1:
Attempt several times to copy files on a VDI disk, and couldn't trigger any
corruption (nor deadlock - no regression). Given my test scenario, previously,
I would already have hit the corruption.
TEST CASE 2:
Tested with
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1422307
Title:
qemu-nbd corrupts files
To manage notifications
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422307
Title:
qemu-nbd corrupts files
To manage notifications about this bug go
Please find attach a proposed debdiff for fixing the issue in Ubuntu
Trusty by backporting the fix which is now in Wily.
** Description changed:
+ [Impact]
+ A race condition in the VDI block driver of Qemu leads to image (and thus
file system) corruption under certain circumstances.
+ This
Please find attach a proposed debdiff for fixing the issue in Ubuntu
Trusty by backporting the fix which is now in Wily.
** Description changed:
+ [Impact]
+ A race condition in the VDI block driver of Qemu leads to image (and thus
file system) corruption under certain circumstances.
+ This
Public bug reported:
A bug exists in Ubuntu 14.04 LTS which leads qemu-nbd to corrupt image
files that are mounted.
The bug report done for Qemu is here:
https://bugs.launchpad.net/qemu/+bug/1422307
They fixed it with:
Public bug reported:
A bug exists in Ubuntu 14.04 LTS which leads qemu-nbd to corrupt image
files that are mounted.
The bug report done for Qemu is here:
https://bugs.launchpad.net/qemu/+bug/1422307
They fixed it with:
Public bug reported:
Dear all,
In order to be able to upgrade one of our servers to the latest LTS (14.04), we
need that the Samsung SSD 8 series to be blacklisted from the libata for the
TRIM command.
Due to the bug described here [1], not having the SSD blacklisted would lead
to data
As we are anticipating the issue, based on others feedback, we don't
have logs.
And having logs for data corruption sounds highly difficult to obtain.
So, confirming it.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436755
Title:
Memory violation in cf-agent
To manage notifications about this bug go to:
Public bug reported:
Dear all,
In a setup where cf-agent is started by cf-execd and where cf-agent updates its
promises from a remote location, if network connection fails for whatever
reason during the cf-agent run, cf-agent will crash.
I cannot say exactly when though...
Audit always
Public bug reported:
Dear all,
The logrotate configuration script in Trusty is broken.
It uses the following command as postrotate script: invoke-rc.d php5-fpm
reopen-logs /dev/null
Whereas the reopen-logs command isn't supported:
# invoke-rc.d php5-fpm reopen-logs
initctl: invalid command:
*** This bug is a duplicate of bug 1230917 ***
https://bugs.launchpad.net/bugs/1230917
** This bug has been marked a duplicate of bug 1230917
[SRU] php5-fpm logrotate errors after package switched to upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This also affects Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181777
Title:
kvm: freeze a guest with a NIC PCI passthrough
To manage notifications about this bug go to:
This also affects Trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to seabios in Ubuntu.
https://bugs.launchpad.net/bugs/1181777
Title:
kvm: freeze a guest with a NIC PCI passthrough
To manage notifications about this bug go
So, after discussing with the devs, when called from a SVN hook, a leading /
is added to the path and it produces the error.
If removed, it doesn't hit the assert.
So, the bug is that kgb-client should chomp the leadng / if any.
--
You received this bug notification because you are a member of
** Bug watch added: Debian Bug tracker #772735
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772735
** Also affects: kgb-bot (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772735
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
Dear all,
KGB-client is totally broken on Ubuntu 14.04 LTS with SVN repository.
When invoking it as it would be from a hook:
kgb-client --conf /etc/kgb-client/kgb-reactos.conf --repository svn
/srv/svn/reactos/ 65590
given is experimental at /usr/bin/kgb-client line 245.
I also tried with package 1.33-2ubuntu1 (from Vivid), nothing better, still the
same error (less verbose though :-)):
kgb-client --conf /etc/kgb-client/kgb-reactos.conf --repository svn
/srv/svn/reactos/ 65590
perl: /build/buildd/subversion-1.8.8/subversion/libsvn_subr/dirent_uri.c:972:
It's interestingg to note that with the latest package, the assertion
still fails BUT it can display a bit of information: commiter name,
files changed. But it eats the commit message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Disabling SSLv3 is WIP on Debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=765347
** Bug watch added: Debian Bug tracker #765347
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765347
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Disabling SSLv3 is WIP on Debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=765347
** Bug watch added: Debian Bug tracker #765347
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765347
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Unfortunately, I cannot reproduce with the up to date release of php5 on Ubuntu
12.04 LTS. So I guess it's resolved.
Version being now:
# php5 -v
PHP 5.3.10-1ubuntu3.13 with Suhosin-Patch (cli) (built: Jul 7 2014 18:54:55)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2.3.0, Copyright (c)
We cannot unfortunately test upstream kernel due to a regression in
recent kernels we couldn't track yet (in connections bridging).
Furthermore, this crash happened only once in several months in
production. And finally, this is a production server on which we're
pretty not willing doing tests. It
** Changed in: linux (Ubuntu)
Status: Incomplete = New
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352794
Title:
Null pointer
Public bug reported:
Dear all,
We faced a kernel oops on KVM from a null pointer derefence on one of
our hypervisors (running several KVM VMs). This lead us to a serie of
kernel oops affecting all the VMs and finally, the host crash. We
couldn't really establish where from the first oops was
** Description changed:
Dear all,
We faced a kernel oops on KVM from a null pointer derefence on one of
- our hypervisors (running several KVM VMs). This lead us to a serie of
+ our hypervisors (running several KVM VMs). This led us to a serie of
kernel oops affecting all the VMs and
Public bug reported:
Dear all,
We faced a kernel oops on KVM from a null pointer derefence on one of
our hypervisors (running several KVM VMs). This lead us to a serie of
kernel oops affecting all the VMs and finally, the host crash. We
couldn't really establish where from the first oops was
** Description changed:
Dear all,
We faced a kernel oops on KVM from a null pointer derefence on one of
- our hypervisors (running several KVM VMs). This lead us to a serie of
+ our hypervisors (running several KVM VMs). This led us to a serie of
kernel oops affecting all the VMs and
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1352794/+attachment/4170588/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352794
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1352794/+attachment/4170587/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352794
apport information
** Tags added: apport-collected precise
** Description changed:
Dear all,
We faced a kernel oops on KVM from a null pointer derefence on one of
our hypervisors (running several KVM VMs). This led us to a serie of
kernel oops affecting all the VMs and finally, the
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1352794/+attachment/4170590/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352794
Title:
Null
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1352794/+attachment/4170595/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352794
Title:
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1352794/+attachment/4170593/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352794
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1352794/+attachment/4170591/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352794
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1352794/+attachment/4170589/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352794
Title:
Null
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1352794/+attachment/4170592/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1352794/+attachment/4170594/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352794
Title:
We're also affected by this bug here. You can actually see my questioning on
libvirt-users about this:
https://www.redhat.com/archives/libvirt-users/2014-July/msg00134.html
Using rom bar='off'/ fixes it.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This workaround unfortunately appear to totally break the network card
in the VM making it unusable. TG3 driver (which is supposed to handle
it) cannot properly communicate with it.
The kernel outputs the following lines:
Jul 30 13:32:03 carrier-commander kernel: [0.981658] tg3 :00:05.0:
We're also affected by this bug here. You can actually see my questioning on
libvirt-users about this:
https://www.redhat.com/archives/libvirt-users/2014-July/msg00134.html
Using rom bar='off'/ fixes it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This workaround unfortunately appear to totally break the network card
in the VM making it unusable. TG3 driver (which is supposed to handle
it) cannot properly communicate with it.
The kernel outputs the following lines:
Jul 30 13:32:03 carrier-commander kernel: [0.981658] tg3 :00:05.0:
Public bug reported:
By default, Snort sends a daily report by email about events that
occurred during last day.
Unfortunately, even when Snort is configured to watch both IPv4 IPv6
networks, this email only contains IPv4 events.
I could check with Prelude that Snort properly catches IPv6
ii libselinux1 2.1.0-4.1ubuntu1
SELinux runtime shared libraries
ii linux-firmware 1.79.12
Firmware for Linux kernel drivers
ii linux-headers-3.2.0-60 3.2.0-60.91
ii libselinux1 2.1.0-4.1ubuntu1
SELinux runtime shared libraries
ii linux-firmware 1.79.12
Firmware for Linux kernel drivers
ii linux-headers-3.2.0-60 3.2.0-60.91
Well, now that I use the tool above, I don't have the WL issue anylonger
(yeah, I forgot to say it in the first place).
The only issue I could find up to now is WL with vars having '[', ']' in
their names. There's an open bug report on their Google code place. And
even applying the workaround
Well, now that I use the tool above, I don't have the WL issue anylonger
(yeah, I forgot to say it in the first place).
The only issue I could find up to now is WL with vars having '[', ']' in
their names. There's an open bug report on their Google code place. And
even applying the workaround
I've been successfully using nx_utils.py from here:
http://naxsi.googlecode.com/svn/tags/0.50/contrib/nx_util/nx_lib/ with
1.1.19.
--
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/1170585
I've been successfully using nx_utils.py from here:
http://naxsi.googlecode.com/svn/tags/0.50/contrib/nx_util/nx_lib/ with
1.1.19.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170585
Title:
Also affected by this bug with Ubuntu 12.04LTS kvm.
A tracepath in a VM with virtio network card ends with: Resume: pmtu 65535.
While with pcnet or rtl8139 it properly ends with: Resume: pmtu 1500
This is pretty blocking given some servers are failing to communicate
because of the wrong MTU (I've
Also affected by this bug with Ubuntu 12.04LTS kvm.
A tracepath in a VM with virtio network card ends with: Resume: pmtu 65535.
While with pcnet or rtl8139 it properly ends with: Resume: pmtu 1500
This is pretty blocking given some servers are failing to communicate
because of the wrong MTU (I've
Hi,
Deployed with success on our infrastructure. Everything is working fine.
Munin is properly reading status. Web server is properly serving data.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Any potential ETA regarding the fix for Precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170586
Title:
Naxsi package lacking Stub Status
To manage notifications about this bug go to:
Dunno what kind of test case you want, but basically try to start nginx with
this in your config:
server {
listen 127.0.0.1;
server_name localhost;
location /nginx_status {
stub_status on;
access_log off;
allow 127.0.0.1;
Hi,
it will be available through precise-backports?
Any idea about the ETA?
Regards,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232672
Title:
Trigger taking forever
To manage notifications
Well looking at Debian package page (http://packages.debian.org/wheezy
/nginx-naxsi) regarding the first version available (1.2.1-2), it is
providing Stub Status.
Maybe it can help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for your answer, I fully get your point!
Then, in case 1.1.9 never had such module, I'd support for having it in Ubuntu.
Additionnal features it adds are rather limited and harmless. The main purpose
of this module (which has to explicitly be activated through config file) is to
provide
?
With my best regards,
Pierre Schweitzer
** Affects: buildbot (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Hi,
- with the upgrade to 0.8.5 in Ubuntu, it appears that we are facing several
bugs where buildbot waits just forever. Especially on trigger steps
Public bug reported:
Hi,
Using the following config:
# php5 -v
PHP Warning: PHP Startup: Unable to load dynamic library
'/usr/lib/php5/20090626/apc.so' - /usr/lib/php5/20090626/apc.so: cannot open
shared object file: No such file or directory in Unknown on line 0
PHP 5.3.10-1ubuntu3.6 with
Public bug reported:
Hi,
when importing this wl rule into naxsi:
# total_count:2186 (1.37%), peer_count:297 (25.94%) | sql keywords
BasicRule wl:1000 mz:$URL_VAR:cookie;
nginx can't be restarted anylonger and displays the error:
Restarting nginx: nginx: [emerg] Naxsi-Config : Incorrect line
Public bug reported:
Hi,
The nginx-naxsi package provided in Ubuntu 12.04 LTS lacks the Stub
Status module which somehow mandatory in production environment. Plus,
if Ubuntu follows Debian philosophy regarding those packages, it is
supposed to be shipped with in Debian:
Hi,
is there a chance that rkhunter is updated in Precise, as it has not
been in Oneric? This bug also affects it. Which is really annoying for a
LTS used on servers...
Regards,
Pierre S.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
72 matches
Mail list logo
