Distinct blocks ips:

Submitted by xbeltram on Wed, 11/07/2012 - 12:50

Hello

I've two distinct blocks ips:

Range start Range end Addresses Used Left Host systems
177.1.138.41 177.1.138.46 6 5 1 tchod.tchod.com 187.53.217.192 187.53.217.255 64 1 63 tchod.tchod.com

In smaller block of IPs are configured two virtual machines running smoothly: www.mktconnection.com.br www.shackvirtual.com.br

At this time I created the vm mktnext however has not ping the ip 187.53.217.194 created with the ip address of 187.53.217.193 and ping already have this in my circuit.

I created the vm and came across this error:

Last Ping failed status (Last changed 07/Nov/2012 at 16:02) Detailed status error ssh: connect to host 187.53.217.194 port 22: No route to host

I wonder if there is any further configuration to use this second block of ips.

thank you

Status: 
Active

Comments

Submitted by xbeltram on Wed, 11/07/2012 - 21:57

hello you could answer this ticket thank you

Submitted by JamieCameron on Wed, 11/07/2012 - 23:19

This sounds like a possible routing issue. Is the second IP range 187.53.217.192-187.53.217.255 supposed to be on the same LAN as your primary range?

Submitted by xbeltram on Wed, 11/07/2012 - 23:50

I do not understand your question. I need to install these new vm ips them

You can log in and see the ips it. Were detected by the system occupied and free. Can you tell me what should I do to use these ips on vm?

Submitted by xbeltram on Thu, 11/08/2012 - 08:57

I see that you answered all the posts ... least my ...

Submitted by JamieCameron on Thu, 11/08/2012 - 12:15

You need to tell your system that the IP range 187.53.217.192 is on the same LAN as the system's primary IP, so that it can reach IPs in that range. This doesn't happen automatically, as assigning multiple different IP ranges to the same LAN is a little odd.

This can be done with the following command, run as root :

route add -net 187.53.217.192 netmask 255.255.255.192 dev eth0

Let us know if that helps.

Submitted by xbeltram on Thu, 11/08/2012 - 15:19

I continue with the same problem

Adding DNS entry mktnextcom.cloudmin.tchod.com. for IP address 187.53.217.194 .. .. done

Configuring Xen instance for VNC console access .. .. added on dynamic port

Starting up new Xen instance .. .. failed to start : Xen instance was started, but could not be accessed via SSH after 60 seconds

Fetching current status .. .. status successfully retrieved (Ping failed)

Re-fetching current status of host system tchod.tchod.com .. .. status successfully retrieved (Virtualmin)

Enabling system at host boot time .. .. done

Creating console access user .. .. done

Submitted by JamieCameron on Thu, 11/08/2012 - 15:30

I think the problem is that the VM on that IP range doesn't have a default route setup.

Did your ISP give you a default route IP address for the 187.53.217.192 range?

Submitted by xbeltram on Thu, 11/08/2012 - 15:41

I think the main ip is 187.53.217.193

This ip has ping independent of any configuration vm

What I think should be the ip 187.53.217.192 Gateway

Submitted by JamieCameron on Thu, 11/08/2012 - 15:45

Ok, I see the issue - the default gateway for the .192 address range was set wrong at Host Systems -> IP Addresses -> Common IPv4 Pools. I have fixed that now, and the VM on that range appears OK.

Submitted by JamieCameron on Thu, 11/08/2012 - 16:36

For a new VM, or the one you have already created?

Submitted by xbeltram on Thu, 11/08/2012 - 16:40

For the new vm created with the range we were trying to implement ip 187.53.217.194 vm mktnextcom

Submitted by xbeltram on Thu, 11/08/2012 - 18:08

I just this moment of creating the vm below:

Adding DNS entry mktnext.cloudmin.tchod.com. IP address is 187.53.217.192 .. .. done

Configuring Xen VNC console access for instance .. .. added on dynamic port

Starting up new Xen instance .. .. failed to start: Xen instance was started, but could not be accessed via SSH after 60 seconds

Fetching current status .. .. status successfully retrieved (Ping failed)

Re-fetching current status of host system tchod.tchod.com .. .. status successfully retrieved (Virtualmin)

Enabling host system at boot time .. .. done

Creating user console access .. .. done

Submitted by JamieCameron on Thu, 11/08/2012 - 19:20

This looks like a routing issue .. I am taking a look now.

Submitted by JamieCameron on Thu, 11/08/2012 - 19:49

I tracked down the issue - again it was reverse DNS lookup slowness. The IP range 187.53.217.192 assigned by your ISP does not have reverse DNS working, which causes and SSH connections to machines in that range to fail (or at least take a really long time). This then confuses Cloudmin.

I fixed the issue by creating a reverse DNS zone on the Cloudmin master, at Webmin -> Servers -> BIND DNS Server.

Submitted by xbeltram on Thu, 11/08/2012 - 21:11

Cloudmin jamietest.cloudmin.tchod.com Fully refreshing system status and available packages .. .. done. New status is : Virtualmin - Config errors found

Virtualmin Checking Configuration

The status of your system is being checked to ensure that all enabled features are available, that the mail server is properly configured, and that quotas are active ..

Your system has 512 MB of memory, which is at or above the Virtualmin recommended limit of 256 MB.

BIND DNS server is installed, and the system is configured to use it.

Mail server Postfix is installed and configured.

Apache is installed.

Webalizer is installed.

Apache is configured to host SSL websites.

MySQL is installed and running, but does not have any root password set! This should be changed immediately in the MySQL Database module.

ProFTPd is installed.

Current logrotate configuration is not valid :

error: stat of /var/log/freshclam.log failed: No such file or directory

. This must be fixed, or log file rotation will not be done.

.. your system is not ready for use by Virtualmin.

Submitted by JamieCameron on Fri, 11/09/2012 - 01:35

You can fix that by just running touch /var/log/freshclam.log on the VM.