Skip to content
This repository was archived by the owner on Feb 8, 2021. It is now read-only.
This repository was archived by the owner on Feb 8, 2021. It is now read-only.

restart hyperd service cause running pods disappeared #654

Open

Description

@jiangpengcheng

when restart the hyperd service, running pods will disappear, but if we restart the hyperd again, the disappeared pods will return.

how to reproduce:

  1. start a simpe pod:
[root@localhost hyper]# hyperctl run -d --name test nginx
POD id is test
Time to run a POD is 5782 ms
[root@localhost hyper]# hyperctl list
POD ID              POD Name            VM name             Status
test                test                vm-LTppyMtoxV       running
[root@localhost hyper]#
  1. restart the hyperd, the pod is disappeared:
[root@localhost hyper]# service hyperd restart
[root@localhost hyper]# hyperctl list
POD ID              POD Name            VM name             Status
[root@localhost hyper]#
  1. restart the hyperd service again, and the pod comes back:
[root@localhost hyper]# service hyperd restart
[root@localhost hyper]# hyperctl list
POD ID              POD Name            VM name             Status
test                test                                    failed

The test env is:

OS:  CentOS Linux release 7.2.1511 (Core)
Kernal:  3.10.0-327.el7.x86_64
hyperd: v0.8.1

The error log looks like below:

Aug 20 22:03:40 localhost.localdomain hyperd[3618]: E0820 22:03:40.104639    3618 persistence.go:232] PSB[vm-SinrUrqJaU] cannot load driver context: signal 0 on Qemu process(3479) failed: os: process already finished
Aug 20 22:03:40 localhost.localdomain hyperd[3618]: E0820 22:03:40.105031    3618 vm.go:98] VM[vm-SinrUrqJaU] cannot associate with vm: signal 0 on Qemu process(3479) failed: os: process already finished
Aug 20 22:03:40 localhost.localdomain hyperd[3618]: E0820 22:03:40.105042    3618 provision.go:284] Pod[test] signal 0 on Qemu process(3479) failed: os: process already finished

Activity

  1. gnawux commented on Aug 21, 2017

    @gnawux
    Member

    stop it with SIGHUP instead of SIGTERM

  2. jiangpengcheng commented on Aug 21, 2017

    @jiangpengcheng
    Author

    should this be written to the systemd unit file?

  3. hhkbble commented on Sep 20, 2017

    @hhkbble

    @gnawux i did as you said, but it's not fixed.

  4. gnawux commented on Oct 8, 2017

    @gnawux
    Member

    @haoyixin stop hyperd with kill -HUP, it won't stop the qemu processes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions