OpenVZ Forum


Home » General » Support » no routing - /dev/fd/62: No such file or directory
Re: no routing - /dev/fd/62: No such file or directory [message #12683 is a reply to message #12680] Mon, 07 May 2007 10:25 Go to previous messageGo to previous message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Hello,

I've just tried this template on my OpenVZ node and it works perfectly with network:
[root@localhost ~]# uname -a
Linux localhost.localdomain 2.6.18-ovz028stab031.1-smp #1 SMP Thu Apr 26 20:55:28 MSD 2007 i686 i686 i386 GNU/Linux
[root@localhost ~]# cat /etc/resolv.conf 
search localdomain
nameserver 192.168.1.1
[root@localhost ~]# vzctl --version
vzctl version 3.0.16
[root@localhost ~]# ls -l /vz/template/cache/opensuse-10-i386-default.tar.gz 
-rw-r--r--  1 root root 94704566 May  7 13:59 /vz/template/cache/opensuse-10-i386-default.tar.gz
[root@localhost ~]# vzctl create 300 --ostemplate opensuse-10-i386-default
Creating VE private area (opensuse-10-i386-default)
Performing postcreate actions
VE private area was created
[root@localhost ~]# vzctl set 300 --ipadd 172.0.0.3 --save
Saved parameters for VE 300
[root@localhost ~]# vzctl start 300
Starting VE ...
VE is mounted
Adding IP address(es): 172.0.0.3
Setting CPU units: 1000
VE start in progress...
[root@localhost ~]# vzctl exec 300 ping 172.0.0.2
PING 172.0.0.2 (172.0.0.2) 56(84) bytes of data.
64 bytes from 172.0.0.2: icmp_seq=1 ttl=64 time=0.084 ms
64 bytes from 172.0.0.2: icmp_seq=2 ttl=64 time=0.063 ms

[root@localhost ~]# vzctl enter 300
entered into VE 300
localhost:/ # route -nv
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.0.2.0       0.0.0.0         255.255.255.0   U     0      0        0 venet0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.0.2.1       0.0.0.0         UG    0      0        0 venet0
localhost:/ # /etc/init.d/network restart
Shutting down network interfaces:
    venet0                                                            done
Shutting down service network  .  .  .  .  .  .  .  .  .  .  .  .  .  done
Setting up network interfaces:
    lo        
    lo        IP address: 127.0.0.1/8                                 done
    venet0    
    venet0    IP address: 127.0.0.1/32   
    venet0:0  IP address: 172.0.0.3/                                  done
Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  done
localhost:/ # ping 172.0.0.2
PING 172.0.0.2 (172.0.0.2) 56(84) bytes of data.
64 bytes from 172.0.0.2: icmp_seq=1 ttl=64 time=0.081 ms
64 bytes from 172.0.0.2: icmp_seq=2 ttl=64 time=0.042 ms

--- 172.0.0.2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.042/0.061/0.081/0.021 ms
localhost:/ #

So, the problem is probably relayted to the Debian vzctl package or something else your node specific... I can look at it if you give me an access to your node. Also you can analyze /etc/sysconfig/network/scripts/ifup-route file independently to identify the problem.

Vasily
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: *SOLVED* process count and stable kernel
Next Topic: *CLOSED* Fail to create vps
Goto Forum:
  


Current Time: Fri Aug 16 15:46:05 GMT 2024

Total time taken to generate the page: 0.02906 seconds