'lxc stop ...' hangs and works after second try


#1

The container shutdown does not work with first stop command.
A second stop works after canceled stop.
It is not the first time that this error occurs.

Is there a way to solve this issue?

$ lxc --version
3.8
$ lxd --version
3.8

$ lxc stop vB04-openvpn
Error: User signaled us three times, exiting. The remote operation will keep running
Try `lxc info --show-log vB04-openvpn` for more info

$ lxc info --show-log vB04-openvpn
Name: vB04-openvpn
Location: none
Remote: unix://
Architecture: x86_64
Created: 2018/11/19 22:07 UTC
Status: Running
Type: persistent
Profiles: default
Pid: 5653
Ips:
  lo:	inet	127.0.0.1
  lo:	inet6	::1
Resources:
  Processes: 2
  Disk usage:
    root: 1.08GB
  CPU usage:
    CPU usage (in seconds): 1612
  Memory usage:
    Memory (current): 86.67MB
    Memory (peak): 187.81MB
  Network usage:
    eth0:
      Bytes received: 1.78MB
      Bytes sent: 785.55kB
      Packets received: 13154
      Packets sent: 5581
    lo:
      Bytes received: 624B
      Bytes sent: 624B
      Packets received: 6
      Packets sent: 6

Log:

$ lxc info --show-log vB04-openvpn
Name: vB04-openvpn
Location: none
Remote: unix://
Architecture: x86_64
Created: 2018/11/19 22:07 UTC
Status: Stopped
Type: persistent
Profiles: default

Log:


(Stéphane Graber) #2

That can happen, lxc stop when not passed --force will just send a signal to the init system of the container, the init system may just disregard that signal or require it be sent multiple times, depending on where in the boot sequence you’re at.