OpenVZ Forum


Home » General » Support » BUG: "prlctl destroy <UUID>" autostarts containers
Re: BUG: "prlctl destroy <UUID>" autostarts containers [message #53711 is a reply to message #53710] Thu, 19 November 2020 07:09 Go to previous message
khorenko is currently offline  khorenko
Messages: 533
Registered: January 2006
Location: Moscow, Russia
Senior Member
Hi Michael,

i failed to reproduce the issue in an easy way:
[root@sbf7 ~]# prlctl list --info|grep Autostart
Autostart: off
Autostart: off
Autostart: off
Autostart: off
Autostart: off
Autostart: off
Autostart: off
Autostart: off
Autostart: off

[root@sbf7 ~]# prlctl list -a
UUID                                    STATUS       IP_ADDR         T  NAME
{e184beed-db92-4b07-971d-e8a4c9bff9f2}  stopped      -               CT 100
{49bd6422-d6e7-4777-baaa-baa908e93f91}  stopped      -               CT 101
{99b797a2-9b50-4a60-a9d7-30d3268c8ed9}  stopped      -               CT 102
{863f365c-bcf0-45b0-84e8-229fac815129}  stopped      -               CT 1024
{e0860e37-19f1-4c97-9374-343244f476fa}  stopped      -               CT 200
{24f9c50f-f9a4-4784-b9da-4975363665fd}  stopped      192.169.9.89    CT 300
{a6fb4d5a-2adb-443c-a01b-c12b12becb29}  stopped      192.169.9.90    CT 301
{bd7900ba-a98d-47ae-b232-4ffd0e12e3b0}  stopped      -               CT 302
{fbb33119-82a4-40a7-9d4e-dd28c3a3ee3e}  stopped      -               CT 500

[root@sbf7 ~]# prlctl destroy fbb33119-82a4-40a7-9d4e-dd28c3a3ee3e
Removing the CT...
The CT has been successfully removed.

[root@sbf7 ~]# prlctl list -a
UUID                                    STATUS       IP_ADDR         T  NAME
{e184beed-db92-4b07-971d-e8a4c9bff9f2}  stopped      -               CT 100
{49bd6422-d6e7-4777-baaa-baa908e93f91}  stopped      -               CT 101
{99b797a2-9b50-4a60-a9d7-30d3268c8ed9}  stopped      -               CT 102
{863f365c-bcf0-45b0-84e8-229fac815129}  stopped      -               CT 1024
{e0860e37-19f1-4c97-9374-343244f476fa}  stopped      -               CT 200
{24f9c50f-f9a4-4784-b9da-4975363665fd}  stopped      192.169.9.89    CT 300
{a6fb4d5a-2adb-443c-a01b-c12b12becb29}  stopped      192.169.9.90    CT 301
{bd7900ba-a98d-47ae-b232-4ffd0e12e3b0}  stopped      -               CT 302


So please file a bug at bugs.openvz.org and provide full logs: vzctl.log and prl* logs.


If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
 
Read Message
Read Message
Previous Topic: OpenVZ 7 OOM killing systemd in containers
Next Topic: Installing CentOS 7 packages on OpenVZ 7
Goto Forum:
  


Current Time: Fri Apr 26 18:34:20 GMT 2024

Total time taken to generate the page: 0.01661 seconds