Re-creating virtual server.. failed!

Submitted by Tomtreas on Fri, 11/21/2014 - 09:13 Pro Licensee

could not work out the default IP address .. failed! See the progress output above

Gentlemen,

How do I get past this? I've got two servers down, I'm trying to resurrect two virtual machines that were transferred in the past to my current host. There are a couple of new domains in my S3 backup that have been added since I moved to that host. I have both VM's updated and am restoring from my S3 bucket. Whether or not I check to continue on errors, it still doesn't create these new virtual host servers so that I may go in and change the IP on them and move on.

I have yet to change the DNS to these two new machines because right now they are in a sandbox and will be RAR'ed and then transferred to another of my hosting providers sites in another city. I'm hoping to get all of the virtual hosts in place from the most recent backup, change the IP addresses on them via the console to the new IP in their new home, RAR them and send them to the hosting provider. Please help! I've been down for going on 3 days now.

Thanks!

Status: 
Closed (fixed)

Comments

Submitted by andreychek on Fri, 11/21/2014 - 09:20

Howdy -- hmm, if you go into System Settings -> Re-Check Config, does that work properly?

It sounds like it may be having a tough time figuring out what interface contains your primary IP address.

You may want to take a peek in System Settings -> Virtualmin Config -> Network Settings.

There, you can take a peek at "Network interface for virtual addresses", "Default virtual server IPv4 address", and "Default IP address for DNS records".

If you aren't sure of the issue after looking at those, feel free to post a screenshot of that Network Settings screen, along with the output of the command "/sbin/ifconfig".

We can use that information to to determine how it should be setup.

Submitted by Tomtreas on Fri, 11/21/2014 - 09:39 Pro Licensee

Thanks I think I found it. One the one server the default was set to eth0 when in the interface was actually eth1. I set it to detect automatically in hopes that I won't have to change it again once I zip it up and send it my hosting provider. The second server I've yet to catch it just right that the initial scan of what will be restored connection doesn't time out before I tell it to restore. Very slow prociess. I wish I could select backups to restore from the Amazone S3 buckets section. I could get the more critical ones done and get the thing back online and then do the rest at the datacenter instead of here on my lowly DSL connection.

Submitted by Tomtreas on Fri, 11/21/2014 - 09:40 Pro Licensee

I'm correct that I can change all of the IP address information on one of these servers to a new IP before it is actually on that IP right? or should I leave that alone and just change the interface IP to the new before zipping, then connect to Virtualmin when it is online at the new IP and then convert the virtual servers to the new IP?

Submitted by JamieCameron on Fri, 11/21/2014 - 15:36

I'd recomment the second option - set the IP correctly to match what the system has now, and then change the IP later. Virtualmin should prompt you to update all domains to the new IP on the system information page if it detects that the main IP has changed.

Submitted by Tomtreas on Fri, 11/21/2014 - 21:32 Pro Licensee

Thanks you guys! Server is back online waiting for DNS propogation. Now for numero duo! Jamie, I did actually go ahead and try to pre-configure the new IP from the console on the box but messed it up.. so in effect, I ended up doing it the way you suggested anyway! =) Just followed the buttons in sysinfo.

Thanks again!