This is the traceback from the logs in 16.04:
apt.systemd.daily[957]: Traceback (most recent call last):
apt.systemd.daily[957]: File "/usr/bin/unattended-upgrade", line 1473, in
apt.systemd.daily[957]: main(options)
apt.systemd.daily[957]: File "/usr/bin/unattended-upgrade", line 1411,
This still exists in 16.04 and is hitting uns every day.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554365
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
2886: ord
obviously still not. 2016.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/424833
Title:
python-webkit doesn't honor http_proxy anymore
To manage notifications about this bug go to:
https://bugs.laun
Until monday I'd have said: yes, fixed. We have 10.2.3 running for a few
weeks now and it looks good.
However, on monday we've had 2 vms in one night that died with the error
message 'INFO: task jbd2/sda1-8:171_blocked for more than 120 seconds.'
This was during snapshot create/delete times.
Al
Got it. This is the log output that results in the dead kvm process.
2016-08-12 22:29:44.499285 7f6dc700 10 librbd::ImageWatcher: 0x7f6db400b020
C_NotifyAck start: id=234071422725522, handle=140096867143248
2016-08-12 22:29:44.518673 7f6dc700 10 librbd::ImageWatcher: 0x7f6db4003b60
image
Ok, it's logging now for a machine that died 3 times in the last 3 nights.
All deaths followed directly a backup run, where we do this:
1. create a snapshot
2. create a rbd fast-diff between this snapshot and the 24h older one
The log file is growing *very* fast, so let's see if we can afford to
I have added
[client]
debug rbd = 20
log path = /tmp/ceph-$pid.log
to /etc/ceph/ceph.conf
but this seems to have no effect for logging. At least, I can't find anything
relevant below /tmp.
We're using virsh/libvirt for kvm virtualization on a hybrid
configuration (osd hosts == VM hosts). Any hi
Sure - but that's a bit heavy because these are production machines ;)
That'll take some time for a maintenance window.
Would this setting be active as soon as I `virsh restart` the machine?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
@jdillaman nope, there's no such entry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607694
Title:
Exclusive-Lock Issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
We had this again last night. It hit the 14.04 machine again. This bug
seems to prefer this special VM...
librbd/ExclusiveLock.cc: In function 'std::__cxx11::string
librbd::ExclusiveLock::encode_lock_cookie() const [with ImageCtxT =
librbd::ImageCtx; std::__cxx11::string = std::__cxx11::basic_st
We have had this on two VMs in the last 2 days which run on ubuntu 12.04
and 14.04 via virtio-scsi with 8 queues. Just around the time they were
killed, also unattended-upgrades were running on the host.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Affects me too, but forced downgrading destroys python libraries it
seems:
virtualenv -p /usr/bin/python3 env
Running virtualenv with interpreter /usr/bin/python3
Using base prefix '/usr'
New python executable in env/bin/python3
Also creating executable in env/bin/python
Installing setuptools, pip
Regression fix fixes it on 14.04 LTS. Confirmed. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1476662
Title:
lxc-start symlink vulnerabilities may allow guest to read host
filesystem, int
@roman-fiedler
Might point to the same, but we already have relative mount targets:
lxc.mount.entry = proc /var/lib/our_containers/123/rootfs/proc proc
nosuid,nodev,noexec 0 0
So that won't help as suggested in the mail.
--
You received this bug notification because you are a member of Ubuntu
@roman-fiedler
We're using absolute mount targets here, so that might help. Will try this out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1476662
Title:
lxc-start symlink vulnerabilities may allo
The problem lies in the ubuntu patch
http://archive.ubuntu.com/ubuntu/pool/main/l/lxc/lxc_1.0.7-0ubuntu0.5.debian.tar.gz
where this code
+ size_t start = croot ? strlen(croot) : 0;
+ if (strcmp(ws + start, target + start) != 0) {
+ ERROR("Mount onto %s resulted in %s\n"
We're getting
lxc-start: utils.c: safe_mount: 1409 Mount of 'proc' onto
'/usr/lib/x86_64-linux-gnu/lxc//proc' was onto a symlink!
on all containers since we upgraded to 1.0.7-0ubuntu0.5 and they don't
start. No container has /proc as a symlink. Plese tell me what
information is required from me.
17 matches
Mail list logo
