After cloning, unable to startup system

thedaemexco's picture
Submitted by thedaemexco on Wed, 11/11/2020 - 10:08 Pro Licensee

Hi there, we are having issues with the latest Cloudmin. We try and clone a system and everything appears fine. When we go to startup the system we get:

qemu-kvm: -monitor tcp:127.0.0.1:40009,server: Failed to bind socket: Address al ready in use qemu-kvm: -monitor tcp:127.0.0.1:40009,server: chardev: opening backend "socket" failed

Why is it using the same socket port even though the cloned server is a different server? When we shut off the original machine and startup the clone it works fine and vice versa but obviously we need to be able to run both. What's going on here? Thanks.

Status: 
Active
Virtualmin version: 
6.09
Webmin version: 
1.942

Comments

Ilia's picture
Submitted by Ilia on Fri, 11/13/2020 - 04:23

Hi,

Why is it using the same socket port even though the cloned server is a different server?

Perhaps, it's a bug?

At first, please upgrade your systems with the latest Webmin, Virtualmin and Cloudmin.

Ilia's picture
Submitted by Ilia on Sat, 11/14/2020 - 11:56

Assigned: Unassigned ยป

I will assign this to Jamie for a comment, as I could also reproduce it after cloning CentOS 8 instance on CentOS 7 Cloudmin master machine.

thedaemexco's picture
Submitted by thedaemexco on Mon, 11/16/2020 - 18:53 Pro Licensee

Ah ok, we can try to upgrade to the latest version but thanks for confirming this also happens on your side. Looking forward to hearing back from you guys :)