Suddenly Unable to Create Virtual Server

9 posts / 0 new
Topic locked
Last post
#1 Tue, 03/20/2012 - 15:36
whenisayjump

Suddenly Unable to Create Virtual Server

Today I came to load virtualmin, and I was unable to. I logged into my server as root, and manually restarted VM. When I was able to log in, it gave me a message about the OS being not what it expected. So I updated it.

Now when I try to create a VS I get the following message:

Failed to create virtual server : New virtual server has no IP address! Perhaps Virtualmin could not work out the system's default IP.

Could anyone help me please? I'm really stumped.

Thanks, James

Tue, 03/20/2012 - 17:58
andreychek

Howdy,

Well, what output do you receive if you run the command "/sbin/ifconfig"?

Also, are you using a dedicated server, or a VPS?

-Eric

Wed, 03/21/2012 - 04:20 (Reply to #2)
whenisayjump

Hello Eric,

I get the following output:

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3891 errors:0 dropped:0 overruns:0 frame:0 TX packets:3891 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:352738 (344.4 KiB) TX bytes:352738 (344.4 KiB)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:1271292 errors:0 dropped:0 overruns:0 frame:0 TX packets:1141225 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:400196965 (381.6 MiB) TX bytes:251062522 (239.4 MiB)

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:95.154.192.129 P-t-P:95.154.192.129 Bcast:95.154.192.129 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

venet0:1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.154.192.129 P-t-P:10.154.192.129 Bcast:10.154.192.129 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

venet0:2 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:95.154.192.135 P-t-P:95.154.192.135 Bcast:95.154.192.135 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

I'm on a VPS

Thanks, James

Wed, 03/21/2012 - 09:03
andreychek

Howdy,

Ah, I think I see.

So, if you look in System Settings -> Virtualmin Config -> Network Settings, what is "Network interface for virtual addresses" set to?

Based on the output I see above, it looks like that should be "venet0:0".

-Eric

Wed, 03/21/2012 - 10:14
whenisayjump

Ah, thanks. I get a little further now.

When I try to create a new VS the following happens:

Creating administration group stuart2 .. .. done

Creating administration user stuart2 .. .. done

Failed to create virtual server :

Then nothing :/

Regards, James

Wed, 03/21/2012 - 10:29
Locutus

Considering the initial problem message you received, I suppose something bigger must have changed in your server? Messages about wrong OS version and not being able to log in and then IP address issues and stuff don't happen just like that. :)

My suggestion would be trying to find out what had happened when the problems started, otherwise trying to fix specific symptoms might lead to nothing, or even worse you could be changing settings that just make things worse.

So, what OS are you using, what hosting system, and what exactly was done before and after the problems started?

Wed, 03/21/2012 - 11:29 (Reply to #6)
whenisayjump

Yeah, that's probably a good idea. I suspected that may be the case myself.

I have checked my cron, and it's running a daily rpm (which I didn't realise). Looking at the yum logs the following seem to have been updated on the 20th (this was when I noticed that the troubles had begun).

Mar 20 23:06:30 Updated: sendmail-8.13.8-8.1.el5_7.x86_64 Mar 20 23:06:31 Updated: sendmail-doc-8.13.8-8.1.el5_7.x86_64 Mar 20 23:06:32 Updated: sendmail-cf-8.13.8-8.1.el5_7.x86_64 Mar 20 23:06:32 sendmail-doc: ts_done name in te is sendmail should be sendmail-doc Mar 20 23:06:32 sendmail-cf: ts_done name in te is sendmail-doc should be sendmail-cf Mar 20 23:06:38 Updated: 30:bind-libs-9.3.6-20.P1.el5.x86_64 Mar 20 23:06:38 Updated: 30:bind-9.3.6-20.P1.el5.x86_64 Mar 20 23:06:39 Updated: 30:caching-nameserver-9.3.6-20.P1.el5.x86_64 Mar 20 23:06:39 Updated: 30:bind-utils-9.3.6-20.P1.el5.x86_64 Mar 20 23:06:39 bind-utils: ts_done name in te is caching-nameserver should be bind-utils Mar 20 23:06:49 Updated: python-libs-2.4.3-46.el5.x86_64 Mar 20 23:06:49 Updated: python-2.4.3-46.el5.x86_64 Mar 20 23:06:58 Updated: ruby-libs-1.8.5-24.el5.x86_64 Mar 20 23:06:58 Updated: ruby-libs-1.8.5-24.el5.i386 Mar 20 23:06:58 Updated: ruby-1.8.5-24.el5.x86_64 Mar 20 23:06:58 Updated: ruby-irb-1.8.5-24.el5.x86_64 Mar 20 23:06:59 Updated: ruby-rdoc-1.8.5-24.el5.x86_64 Mar 20 23:06:59 Updated: ruby-devel-1.8.5-24.el5.i386 Mar 20 23:06:59 Updated: ruby-devel-1.8.5-24.el5.x86_64 Mar 20 23:07:06 Updated: openssl-0.9.8e-22.el5.x86_64 Mar 20 23:07:06 Updated: openssl-0.9.8e-22.el5.i686 Mar 20 23:07:07 Updated: openssl-devel-0.9.8e-22.el5.x86_64 Mar 20 23:07:07 openssl-devel: ts_done name in te is openssl should be openssl-devel Mar 20 23:07:07 openssl: ts_done name in te is openssl-devel should be openssl Mar 20 23:07:23 Installed: 4:perl-5.8.8-32.el5_7.6.i386 Mar 20 23:07:26 Updated: 4:perl-5.8.8-38.el5.x86_64

Thanks! James

Tue, 12/26/2017 - 17:52
reinhart

here is how to fix it, Virtualmin->System Settings->Virtualmin Configuration->Network Settings-> Default IP address for DNS records >> change it to "Same as virtual server IP"

hope it help :D

Wed, 08/14/2019 - 15:31
mugenhatch

Had this issue on my Debian 10 server and was able to fix it with the following:

System Settings - Virtualmin Configuration - Network Settings - Default Virtual Server IPv4 Address - 192.168.1.XXX (Internal IPv4 Address)

Hope this helps.

Topic locked