** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1668123
Title:
lxc fails to start with cgroup error
Statu
I've had this occur on another system, and this time I could debug it a
little more freely. This is an interesting output:
# dpkg --purge --simulate systemd
dpkg: dependency problems prevent removal of systemd:
snapd depends on systemd (>= 204-5ubuntu20.20); however:
Package systemd is to be r
> Sidenote) the 18GB of /var/lib/juju/db (with backups, of backups, of backups)
> was not helpful, I'll need to talk to sosreport people about that. This is
> what made the report so huge.
I did notice that, but I figured getting you all of the data was better than
fiddling around trying to not in
It's uploading slowly to https://private-
fileshare.canonical.com/~bradm/lp1668123/, once you see the .md5 file in
place and the sosreport is 7.7G, it'll be done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubun
I've generated a sosreport, but its 7.7G. How would you like me to get
this to you?
The interesting part is that all this was deployed via juju, so I don't
know how we got into this state. It also appears to be the only node in
this state, so its a bit confusing as to how it got to be this way.
Public bug reported:
After rebooting a KVM instance hosting LXCs, we get the following error:
$ sudo lxc-ls --fancy
lxc: cgmanager.c: lxc_cgmanager_escape: 331 call to
cgmanager_move_pid_abs_sync(name=dsystemd) failed: invalid request
and the LXCs won't start up. In the error logs it showe
I've upgraded systemd across my cluster to 229-4ubuntu6, removed all my
custom tweaks to systemd settings, reloaded the daemon and both rabbitmq
and mysql appear to be working fine on my openstack cluster. I'll be
throwing a bit more load at it, but usually by this point mysql has
fallen over, so
This does indeed appear to work correctly, I've deployed a container
using juju:
ubuntu@apollo:~$ dpkg-query -W lxc
lxc 1.0.8-0ubuntu0.3
ubuntu@apollo:~$ sudo lxc-ls --fancy
NAME STATEIPV4IPV6 AUTOSTART
--
FWIW and a totally expected result, I just downgraded the LXC packages
on these hosts and redeployed, and things came up ok.
$ dpkg-query -W lxc
lxc 1.0.7-0ubuntu0.10
I don't think this changes anything, but just putting it here for
completeness.
--
You received this bug notification becaus
Public bug reported:
I've just tried using juju to deploy to a container with trusty-proposed
repo enabled, and I get an error message about 'failed to retrieve the
template to clone'. The underlying error appears to be:
tar --numeric-owner -xpJf
/var/cache/lxc/cloud-trusty/ubuntu-14.04-serve
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1186662
Title:
isc-dhcp-server fails to renew lease file
Status in isc-dhcp package in
Public bug reported:
/etc/dhcp/dhclient-exit-hooks.d/ntp doesn't check if /etc/ntp.conf has
been updated since the last time dhclient ran. A simple addition of a
check to see if /etc/ntp.conf is newer than /var/lib/ntp/ntp.conf.dhcp,
and if so letting it add the servers would be sufficient.
This
Public bug reported:
When using ssh and managing ssh port forwards with ~C to remove a
forward that doesn't exist, the following occurs:
user@host:~$
ssh> -KD12345
Unkown port forwarding.
ie, the mispelling of the work Unknown as 'Unkown'.
This occurs at least on a server running on trus
13 matches
Mail list logo
