OpenVZ Forum


Home » General » Support » Can´t access the created VE
Can´t access the created VE [message #33099] Mon, 22 September 2008 15:58 Go to next message
ralphw is currently offline  ralphw
Messages: 29
Registered: September 2008
Location: Celle
Junior Member
Hi to all of you,

I´m stucked now in the following situation.

I´ve installed a Debian.etch server with opnVZ an webVZ.
Ev´rything did work, but if I tried to access the VE via Putty and trie to run apt-get update, it did not work. Wget was´nt even known in the VE.

All IP-Adresses where pingable, the nameservers where set to
### Hetzner Online AG installimage
# nameserver config
nameserver 213.133.98.98
nameserver 213.133.99.99
nameserver 213.133.100.100

Ev´rything worked fine, there where just the described problem.
So I worked on it the hole last night, whitout any results.

Today I set up the hole thing again.
But this time I could´nt even access the VE.
Ive createt a new user in webvz, gave him a password and tried to access via Putty. It tells me´, that the key has changed and ask me, to accept it,´what I did.
Asking for the password, I put in the one I gave in webvz. It was denied, also my root password. What ever I´ve tried, nothing works.
Login with my main-IP, I can start the VE whithout problems

server1:~# vzctl start 177
VE is already running
server1:~# vzctl restart 177
Restarting VE
Stopping VE ...
VE was stopped
VE is unmounted
Starting VE ...
VE is mounted
Adding IP address(es): 78.46.254.177
Setting CPU units: 1000
Configure meminfo: 65536
File resolv.conf was modified
VE start in progress...
server1:~#

Also I can ping all IP´s.


server1:~# ping 78.46.79.2
PING 78.46.79.2 (78.46.79.2) 56(84) bytes of data.
64 bytes from 78.46.79.2: icmp_seq=1 ttl=64 time=0.092 ms
64 bytes from 78.46.79.2: icmp_seq=2 ttl=64 time=0.037 ms
64 bytes from 78.46.79.2: icmp_seq=3 ttl=64 time=0.036 ms

--- 78.46.79.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.036/0.055/0.092/0.026 ms
server1:~# ping 78.46.254.177
PING 78.46.254.177 (78.46.254.177) 56(84) bytes of data.
64 bytes from 78.46.254.177: icmp_seq=1 ttl=64 time=0.098 ms
64 bytes from 78.46.254.177: icmp_seq=2 ttl=64 time=0.045 ms
64 bytes from 78.46.254.177: icmp_seq=3 ttl=64 time=0.049 ms

--- 78.46.254.177 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.045/0.064/0.098/0.024 ms
server1:~# ping 78.46.254.178
PING 78.46.254.178 (78.46.254.178) 56(84) bytes of data.
64 bytes from 78.46.254.178: icmp_seq=1 ttl=64 time=0.086 ms
64 bytes from 78.46.254.178: icmp_seq=2 ttl=64 time=0.040 ms
64 bytes from 78.46.254.178: icmp_seq=3 ttl=64 time=0.039 ms

--- 78.46.254.178 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.039/0.055/0.086/0.021 ms
server1:~# ping 78.46.254.179
PING 78.46.254.179 (78.46.254.179) 56(84) bytes of data.
64 bytes from 78.46.254.179: icmp_seq=1 ttl=64 time=0.095 ms
64 bytes from 78.46.254.179: icmp_seq=2 ttl=64 time=0.040 ms

--- 78.46.254.179 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.040/0.067/0.095/0.028 ms
server1:~# ping 78.46.254.180
PING 78.46.254.180 (78.46.254.180) 56(84) bytes of data.
64 bytes from 78.46.254.180: icmp_seq=1 ttl=64 time=0.085 ms
64 bytes from 78.46.254.180: icmp_seq=2 ttl=64 time=0.042 ms
64 bytes from 78.46.254.180: icmp_seq=3 ttl=64 time=0.043 ms

--- 78.46.254.180 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.042/0.056/0.085/0.021 ms
server1:~# ping 78.46.254.181
PING 78.46.254.181 (78.46.254.181) 56(84) bytes of data.
64 bytes from 78.46.254.181: icmp_seq=1 ttl=64 time=0.083 ms
64 bytes from 78.46.254.181: icmp_seq=2 ttl=64 time=0.038 ms

--- 78.46.254.181 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.038/0.060/0.083/0.023 ms
server1:~# ping 78.46.254.182
PING 78.46.254.182 (78.46.254.182) 56(84) bytes of data.
64 bytes from 78.46.254.182: icmp_seq=1 ttl=64 time=0.088 ms
64 bytes from 78.46.254.182: icmp_seq=2 ttl=64 time=0.044 ms
64 bytes from 78.46.254.182: icmp_seq=3 ttl=64 time=0.044 ms

--- 78.46.254.182 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.044/0.058/0.088/0.022 ms
server1:~#

It´s also possible to stop, start and restart the Container from inside WebVZ.
I looked around a lot, but can´t find a solution.

Has ther anyone an idea, what´s going on and what I should do?
Would be great

Thanks for your help in advance.

regards

Ralph

Here comes the rest of what you maybe need.

server1:~# ip route list table all
78.46.254.177 dev venet0 scope link
78.46.254.176/29 dev eth0 proto kernel scope link src 78.46.254.177
78.46.79.0/27 via 78.46.79.1 dev eth0
78.46.79.0/27 dev eth0 proto kernel scope link src 78.46.79.2
default via 78.46.79.1 dev eth0
local 78.46.254.179 dev eth0 table 255 proto kernel scope host src 78.46.254 .177
local 78.46.254.178 dev eth0 table 255 proto kernel scope host src 78.46.254 .177
local 78.46.79.2 dev eth0 table 255 proto kernel scope host src 78.46.79.2
broadcast 127.255.255.255 dev lo table 255 proto kernel scope link src 127.0 .0.1
local 78.46.254.177 dev eth0 table 255 proto kernel scope host src 78.46.254 .177
broadcast 78.46.254.176 dev eth0 table 255 proto kernel scope link src 78.46 .254.177
broadcast 78.46.79.0 dev eth0 table 255 proto kernel scope link src 78.46.79 .2
broadcast 78.46.254.183 dev eth0 table 255 proto kernel scope link src 78.46 .254.177
local 78.46.254.182 dev eth0 table 255 proto kernel scope host src 78.46.254 .177
local 78.46.254.181 dev eth0 table 255 proto kernel scope host src 78.46.254 .177
local 78.46.254.180 dev eth0 table 255 proto kernel scope host src 78.46.254 .177
broadcast 78.46.79.31 dev eth0 table 255 proto kernel scope link src 78.46.7 9.2
broadcast 127.0.0.0 dev lo table 255 proto kernel scope link src 127.0.0.1
local 127.0.0.1 dev lo table 255 proto kernel scope host src 127.0.0.1
local 127.0.0.0/8 dev lo table 255 proto kernel scope host src 127.0.0.1
local ::1 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 4 294967295
local fe80::21d:92ff:feb6:cadf via :: dev lo proto none metric 0 mtu 16436 ad vmss 16376 hoplimit 4294967295
fe80::/64 dev eth0 metric 256 expires 2133243sec mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev eth0 metric 256 expires 2133243sec mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo proto none metric -1 error -101 hoplimit 255
server1:~#


server1:~# arp -n
Address HWtype HWaddress Flags Mask Iface
78.46.79.1 ether 00:02:85:0C:10:80 C eth0
78.46.254.177 * <from_interface> MP eth0
server1:~#


server1:~# ip rule list
0: from all lookup 255
32766: from all lookup main
32767: from all lookup default
server1:~#


server1:~# iptables -t nat -L && iptables -t filter -L && iptables -t mangle -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain PREROUTING (policy ACCEPT)
target prot opt source destination

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
server1:~#


### Hetzner Online AG - installimage
# Loopback device:
auto lo
iface lo inet loopback

# device: eth0
auto eth0
iface eth0 inet static
address 78.46.79.2
broadcast 78.46.79.31
netmask 255.255.255.224
gateway 78.46.79.1
pointopoint 78.46.79.1

# * zusätzliche IP-Adressen
up ip addr add 78.46.254.177/29 dev eth0
up ip addr add 78.46.254.178/29 dev eth0
up ip addr add 78.46.254.179/29 dev eth0
up ip addr add 78.46.254.180/29 dev eth0
up ip addr add 78.46.254.181/29 dev eth0
up ip addr add 78.46.254.182/29 dev eth0

# default route to access subnet
up route add -net 78.46.79.0 netmask 255.255.255.224 gw 78.46.79.1 eth0

up sysctl -w net.ipv4.conf.eth0.proxy_arp=100
pre-down sysctl -w net.ipv4.conf.eth0.proxy_arp=0

...



AMD Athlon 64 X2 6000+
Dual Core
6 GB DDR2 RAM
2 x 750 GB
SATA II
1 GBit OnBoard

[Updated on: Mon, 22 September 2008 21:20]

Report message to a moderator

Re: Can´t access the createt VE [message #33102 is a reply to message #33099] Mon, 22 September 2008 19:52 Go to previous message
curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany
Senior Member

Hi Ralph,

why add your extra ip to your hostnode and to your containers ?

container #177
---8<---
server1:~# vzctl start 177
[...]
Adding IP address(es): 78.46.254.177 <----------*
[...]
--->8---

hostnode
---8<---
output from /etc/network/interfaces:
[...]
# device: eth0
auto eth0
iface eth0 inet static
address 78.46.79.2
[...]
up ip addr add 78.46.254.177/29 dev eth0 <----------*
[...]
--->8---

Previous Topic: SOLVED: Destination Host Unreachable from VE on Public IP
Next Topic: Where can we download the "vzstat" source code?
Goto Forum:
  


Current Time: Thu May 02 22:44:58 GMT 2024

Total time taken to generate the page: 0.02748 seconds