Submitted by mcordas on Fri, 12/10/2010 - 04:58 Pro Licensee
Hello,
We just added a new physical KVM host on Cloudmin Pro. When we try to create a new KVM VM, we get this error message :
".. creation failed : LVM logical volume creation failed : Remote Webmin error"
The physical host runs webmin 1.530.
The Cloudmin Master runs webmin 1.520. Could that be the source of the problem ?
Status:
Closed (fixed)
Comments
Submitted by mcordas on Fri, 12/10/2010 - 07:36 Pro Licensee Comment #1
I updated webmin, and it still does the same
Submitted by JamieCameron on Fri, 12/10/2010 - 10:39 Comment #2
Does the remote host perhaps have ports 10001 to 10010 blocked by a firewall? I've seen this occasionally, and it can cause RPC errors talking to a remote Webmin server..
Submitted by mcordas on Fri, 12/10/2010 - 12:03 Pro Licensee Comment #3
No, ports 10000-10010 are opened. Portmap is running.
Submitted by JamieCameron on Fri, 12/10/2010 - 12:08 Comment #4
The version mismatch shouldn't matter .. but just in case it does somehow, does downgrading the remote system to 1.520 help?
Submitted by mcordas on Fri, 12/10/2010 - 12:15 Pro Licensee Comment #5
Oops, just updated the cloudmin master to 1.530-1....
Re-tried and i did not help.
I tried to create a Logical Volume on the host from webmin and it worked.
Do you think i should try to downgrade both to 1.520 ?
Submitted by JamieCameron on Fri, 12/10/2010 - 12:45 Comment #6
Try just downgrading the remote system to 1.520.
Alternately, I would be happy to login to your system myself and see what is going wrong.
Submitted by mcordas on Sat, 12/11/2010 - 01:24 Pro Licensee Comment #7
OK, It worked like a charm this time.
I agree it's probably a timeout problem due to the distance between hosts.
I configured the distant host to cache system images to speed up the process.
Thanks !
Submitted by JamieCameron on Sat, 12/11/2010 - 01:26 Comment #8
Yes, there was a Cloudmin bug triggered by the slow image copy time.. it will be fixed in the 5.2 release.
Submitted by Issues on Sat, 12/25/2010 - 04:20 Comment #9
Automatically closed -- issue fixed for 2 weeks with no activity.