Failed to clone virtual server

Submitted by clockwork on Thu, 01/26/2017 - 04:49

If trying to clone a Virtual Server and setting the new username to be an existing username, the clone fails without any useful information.

You just get:

Failed to clone virtual server :

Testing on Debian 7 running Virtualmin 5.05

Status: 
Active

Comments

Submitted by JamieCameron on Thu, 01/26/2017 - 19:05

Can you post the entire output from the cloning page, or was that it?

Submitted by Nico94 on Tue, 03/14/2017 - 09:16

Hello,

I run into the same problem overhere: when trying to clone a VS, I get an almost blank page :

Error
Failed to clone virtual server :

<- Return to previous page

No furter information.

I suspect a bug since one of the latest updates: the cloning function seems to work like a charm on a server that has not been updated for a while.

Moreover, it seems to happen on Debian 6 and 7 systems but not on Debian 8. Here are the tests I made :

  • Debian 6 VM 5.07.gpl -> KO
  • Debian 6 VM 4.18.gpl -> OK
  • Debian 7 VM 5.07.gpl -> KO
  • Debian 8 VM 5.07.gpl -> OK

All the best, Nico

Submitted by JamieCameron on Tue, 03/14/2017 - 12:22

Can you add the line error_stack=1 to /etc/webmin/config , re-try the cloning, and post the new full error message?

Submitted by james.shallcross on Wed, 03/15/2017 - 07:23

I'm having the same issue on CentOS 6

with error_stack=1 set, here is the output :

Failed to clone virtual server :

Call Stack Trace

File Line Function /usr/libexec/webmin/virtual-server/clone.cgi 28 WebminCore::error (eval 46) 6 (eval) /usr/libexec/webmin/miniserv.pl 2402 (eval) /usr/libexec/webmin/miniserv.pl 914 miniserv::handle_request

Submitted by Nico94 on Wed, 03/15/2017 - 16:29

Debian 7, here's the output with error_stack=1 in /etc/webmin/config :

Failed to clone virtual server :

Call Stack Trace

File Line Function

/usr/share/webmin/virtual-server/clone.cgi 28 WebminCore::error

(eval 48) 6 (eval)

/usr/share/webmin/miniserv.pl 2402 (eval)

/usr/share/webmin/miniserv.pl 914 miniserv::handle_request

Submitted by JamieCameron on Wed, 03/15/2017 - 20:01

Ok, what it should be telling you (but due to a bug, is not) is that you didn't enter a password for the newly cloned domain.

Submitted by james.shallcross on Thu, 03/16/2017 - 02:31

I had the "Same as original" option selected for New Password.

Submitted by JamieCameron on Thu, 03/16/2017 - 23:55

Ah ... did the original domain have a password?

Submitted by Nico94 on Sat, 03/18/2017 - 07:00

Same situation here: I also had the "Same as original" option selected and yes, the original domain did have a password.

Submitted by JamieCameron on Sat, 03/18/2017 - 19:20

Ok, turns out this is a Virtualmin bug - the "Same as original" option doesn't work properly.

Until the next release, you need to choose the option to enter a password for the cloned domain.