** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
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/1668049
Title:
lxd cannot shutdown container
Status in s
I have no idea.
I changed jobs and have no more access to the infrastructure where this issue
showed up.
Closing or rejecting this ticket is fine with me.
Op maandag 1 juni 2020 18:31:17 CEST schreef Stéphane Graber
<1668...@bugs.launchpad.net>:
Is this still an issue?
--
You recei
Is this still an issue?
--
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/1668049
Title:
lxd cannot shutdown container
Status in systemd package in Ubuntu:
New
Bug descri
Sorry for the long message, I did reply from email and forgot to delete
the old message (actually assumed that only new text would be uploaded
to launchpad).
Frans
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ub
** Bug watch added: LXD bug tracker #2947
https://github.com/lxc/lxd/issues/2947
** Bug watch added: LXC bug tracker #1085
https://github.com/lxc/lxc/issues/1085
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd i
Hi,
"shutdown --halt now" stops the container as does "shutdown now"
If I omit the now part and just do shutdown --halt
I get:
root@D-wan-61-1:~# shutdown --halt
Failed to set wall message, ignoring: Refusing activation, D-Bus is shutting
down.
Failed to call ScheduleShutdown in logind, proceedi
`shutdown now` executes poweroff command which in systemd signals manpage
documented as:
SIGRTMIN+4 Powers off the machine, starts the poweroff.target unit. This is
mostly equivalent to systemctl start poweroff.target.
The logs indicate that lxc is sending
SIGRTMIN+3 Halts the machine, starts th
I don't think systemd changed its shutdown signal as I have other 1604
based containers that stop as expected. To me it seems that systemd
wants to stop a process and hangs waiting for it (whereas shutdown now
does stop the system)
--
You received this bug notification because you are a member of
Note, that since a while LXC is sending SIGRTMIN+3 to systemd. So unless
systemd has changed it's shutdown/halt signal again LXC should send the
right signal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
9 matches
Mail list logo
