please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668123
Title:
lxc fails to start with
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (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/1668123
Title:
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668123
Title:
lxc fails to start with cgroup error
To manage notifications about
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
FYI because of other maintenance I had to do on the affected nodes,
after upgrading to linux-generic-lts-xenial 4.4.0-66-generic this
issue didn't show anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> 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
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.
1) It appears that deputy systemd was installed on the machine and subsequently
upgraded:
2017-02-12 01:30:24
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
Bugs, which is subscribed to Ubuntu.
private-fileshare.c.c? or e.g. people.c.c? Or just give me ssh access
into the machine?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668123
Title:
lxc fails to start with cgroup error
To manage
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.
Could you please attach a complete sosreport from the affected system?
You appear to be running an incompatible set of packages and features:
* deputy systemd should not be used by cgmanager
* lxc sould not be using deputy systemd
* deputy systemd on trusty may not be used with stock kernel
*
11 matches
Mail list logo
