| *SOLVED* Unable to access VPS from network or network from VPS [message #3428] |
Fri, 26 May 2006 23:42  |
illc0mm
Messages: 8
Registered: January 2006
|
Junior Member |
|
|
Here's the situation: I just upgraded both the kernel and the vzctl/vzctl-lib/vzquota to the most recent stable versions.
Host OS is CentOS 4.2
VPS OS is CentOS 4.3
kernel is 2.6.8-022stab077.1-smp via binary RPM
vzctl is 3.0.0-8
vzctl-lib is 3.0.0-8
vzquota is 3.0.0-7
I have 3 active VPSs
101
103
104
VPS 103 and 104 work fine, IPs load, ifconfig and route show contents, I can access all resources on those VPSs from inside the hardware node and on the network.
VPS101, however, does not work properly.
"vzctl --verbose start 101" shows that it assigns the IP addresses and appears to start properly, however ifconfig or route inside VPS 101 return nothing at all. And I can not ping any of the IPs assigned to that VPS or ping the hardware node or any other network resources from insidethat VPS. vzlist shows the IP assigned to that VPS.
FWIW, I created a new VPS (106) and copied 101.conf over 106.conf and it started and ran fine, this leads me to believe that there is something wrong inside the VPS, but I'm not sure where to start. I checked that iproute and ifconfig were the same versions as in the other vps'. I also stopped all services from loading for now in the suspect VPS to eliminate other issues.
Output of various commands from hardware node:
# sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1
# iptables --list
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
# vzctl --verbose start 101
Unable to open /usr/lib/vzctl/modules/: No such file or directory
Starting VPS ...
Running: /usr/sbin/vzquota show 101
Running: /usr/sbin/vzquota on 101 -r 0 -b 94371940 -B 125829220 -i 800100 -I 880100 -e 0 -n 0 -s 0
Mounting root: /vz/root/101 /vz/private/101
VPS is mounted
Adding IP address(es): 172.16.228.132 172.16.228.133 172.16.228.134 172.16.228.135 172.16.228.136 172.16.228.137 172.16.228.138 10.254.254.21
Running: /usr/lib/vzctl/scripts/vps-net_add
Running VPS script: /etc/sysconfig/vz-scripts/dists/scripts/redhat-add_ip.sh
Setting CPU units: 1000
Set hostname: vps-101.dal1.bsius.com
Running VPS script: /etc/sysconfig/vz-scripts/dists/scripts/redhat-set_hostname.sh
Running VPS script: /etc/sysconfig/vz-scripts/dists/scripts/set_dns.sh
File resolv.conf was modified
Running: /usr/sbin/vzquota stat 101 -f
Running: vzquota setlimit 101 -b 94371840 -B 125829120 -i 800000 -I 880000 -e 0 -n 0
VPS start in progress...
# vzlist -a
VPSID NPROC STATUS IP_ADDR HOSTNAME
101 5 running 172.16.228.132 vps-101.local
103 24 running 172.16.228.139 crm.local
104 76 running 172.16.228.142 scalix.local
#
Output of various commands from VPS:
# vzctl enter 101
entered into VPS 101
-bash-3.00# ifconfig
-bash-3.00# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
-bash-3.00# iptables --list
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
-bash-3.00#
Config for that VPS:
ONBOOT="yes"
# UBC parameters (in form of barrier:limit)
# Primary parameters
AVNUMPROC="80:80"
NUMPROC="150:150"
NUMTCPSOCK="120:120"
NUMOTHERSOCK="200:200"
VMGUARPAGES="6144:2147483647"
# Secondary parameters
KMEMSIZE="9830400:10485760"
TCPSNDBUF="12201847:28585847"
TCPRCVBUF="12201847:28585847"
OTHERSOCKBUF="12201847:28585847"
DGRAMRCVBUF="132096:132096"
OOMGUARPAGES="6144:2147483647"
# Auxiliary parameters
LOCKEDPAGES="32:32"
SHMPAGES="16800:16800"
PRIVVMPAGES="393216:428600"
NUMFILE="2560:2560"
NUMFLOCK="100:110"
NUMPTY="16:16"
NUMSIGINFO="256:256"
DCACHESIZE="625851:983040"
PHYSPAGES="0:2147483647"
NUMIPTENT="128:128"
# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="94371840:125829120"
DISKINODES="800000:880000"
QUOTATIME="0"
# CPU fair sheduler parameter
CPUUNITS="1000"
VE_ROOT="/vz/root/$VEID"
VE_PRIVATE="/vz/private/$VEID"
OSTEMPLATE="centos-4-i386-default"
ORIGIN_SAMPLE="vps.basic"
HOSTNAME="vps-101.dal1.bsius.com"
#IP_ADDRESS="172.16.228.132"
IP_ADDRESS="172.16.228.132 172.16.228.133 172.16.228.134 172.16.228.135 172.16.228.136 172.16.228.137 172.16.228.138 10.254.254.21"
NAMESERVER="66.101.58.2 66.101.58.3"
IPTABLES="iptable_filter iptable_mangle ipt_limit ipt_REJECT ipt_length ip_conntrack ipt_state iptable_nat"
[Updated on: Sat, 27 May 2006 11:10] by Moderator Report message to a moderator |
|
|
|
| Re: SOLVED! Unable to access VPS from network or network from VPS [message #3429 is a reply to message #3428] |
Sat, 27 May 2006 00:07  |
illc0mm
Messages: 8
Registered: January 2006
|
Junior Member |
|
|
I'm an idiot.
Somehow my network script was removed from the VPS init. So /etc/init.d/network was never being called. Not sure how this happened, but running "chkconfig network on" fixed it. WOW!
I'm not sure what would have caused this, I'm positive I did not turn off "network". But this isn't really an OpenVZ issue.
Sorry for the post, but I'll leave it in case anyone else runs across this. The blank ifconfig should have been my first clue, but for some reason I didn't check that. ugh!
[Updated on: Sat, 27 May 2006 00:08] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
