Checkbox "Only remove server from Virtualmin's control" missing

Submitted by Locutus on Fri, 11/05/2010 - 20:47

I just performed the upgrade from 3.81 GPL to 3.82 Pro on my experimental server, and one thing that I noticed is that in the function Disable and Delete -> Delete Virtual Server the checkbox "Only remove server from Virtualmin's control, and leave website, users and databases untouched" is missing.

Was that option maybe moved somewhere else? Or is it no longer available in 3.82 / Pro?

Interesting is that when I use the Search function, the checkbox's caption is still found, apparently in the function where it was before.

I should note that during the upgrade, I noticed a few error messages in the log window about "Webmin not having created a new PID file" and later about "incorrect PID"... Unfortunately I did not copy the exact text away before continuing.

After the upgrade, the Webmin PID was indeed seemingly damaged. The miniserv did not react to requests anymore, /etc/init.d/webmin status said that Webmin is not running, but there still were Webmin processes present. After a system reboot Webmin started up correctly again though.

Of course I cannot rule out the possibility that on this experimental server some configuration was already a little battered. If necessary, I can sure repeat the test with a fresh virtual machine.

Status: 
Closed (works as designed)

Comments

Submitted by JamieCameron on Sat, 11/06/2010 - 00:35

That "only remove from Virtualmin's control" option is actually intentionally disabled in Pro version to prevent customers from exceeding their domain limits by creating domains, removing them (which would lower the licenced domains count) and then adding more.

I really don't recommend ever using it anyway actually .. it was implemented a long time ago, and I can't remember why!

Submitted by Locutus on Sat, 11/06/2010 - 04:47

Okay, both very valid points. And I agree... Also from a Computer Science point of view, having leftover config and data float around that is no longer under control of the management software feels quite "icky"... like a database inconsistency. :)

I'll test the upgrade procedure on a fresh system again today and report if I witness any error messages again.

Submitted by Locutus on Sat, 11/06/2010 - 10:42

I tested the upgrade procedure again on a fresh VM, and encountered no errors whatsoever. The Webmin process also continued to run fine... So this issue can be closed. :)