Page 1 of 1
Unable to Update License
Posted: Thu Sep 29, 2011 12:22 am
by KrazyBob
We have a container on a hardware node that is attempting to update as it is supposed to. We can ping ka.swsoft.com but it almost always goes to one of our other servers before the gateway and then to swsoft. I don't know what the problem is or how to fix it. I do know that the license is graced.
Code: Select all
[root@hw003 etc]# traceroute ka.swsoft.com
traceroute to ka.swsoft.com (64.131.90.38), 30 hops max, 46 byte packets
1 65.44.220.11 (65.44.220.11) 0.133 ms 0.101 ms 0.101 ms
2 65.44.220.1 (65.44.220.1) 0.381 ms 0.212 ms 0.376 ms
3 ip65-46-16-65.z16-46-65.customer.algx.net (65.46.16.65) 0.719 ms 0.385 ms 0.380 ms
4 ge11-1-4d0.mcr1.la-ca.us.xo.net (216.156.11.45) 2.159 ms 2.398 ms 2.271 ms
5 vb1400.rar3.la-ca.us.xo.net (216.156.0.113) 4.491 ms 4.503 ms 3.729 ms
6 207.88.14.218.ptr.us.xo.net (207.88.14.218) 2.342 ms 2.355 ms 2.347 ms
7 ge-11-2-1.mpr1.lax12.us.above.net (64.125.13.17) 2.352 ms 2.354 ms 2.349 ms
8 xe-2-3-0.cr1.lax112.us.above.net (64.125.31.190) 2.553 ms 2.551 ms 2.542 ms
MPLS Label=791026 CoS=0 TTL=85 S=0
9 xe-2-0-0.cr1.iah1.us.above.net (64.125.25.46) 46.927 ms 37.889 ms 37.891 ms
MPLS Label=575101 CoS=0 TTL=85 S=0
10 xe-2-1-0.cr1.dca2.us.above.net (64.125.25.113) 65.966 ms 85.232 ms 65.762 ms
MPLS Label=713014 CoS=0 TTL=85 S=0
11 xe-1-1-0.mpr3.iad1.us.above.net (64.125.31.113) 66.362 ms 66.369 ms 66.162 ms
MPLS Label=380431 CoS=0 TTL=85 S=0
12 xe-0-0-0.mpr4.iad1.us.above.net (64.125.31.106) 66.172 ms 66.153 ms 66.095 ms
MPLS Label=367480 CoS=0 TTL=85 S=0
13 xe-1-1-0.mpr4.iad2.us.above.net (64.125.31.133) 67.130 ms 67.902 ms 67.168 ms
14 64.125.195.222.t00883-02.above.net (64.125.195.222) 66.842 ms 66.991 ms 67.109 ms
15 dl1-si-dc.swsoft.net (64.131.87.10) 68.728 ms 68.937 ms 68.180 ms
16 ix7-si-dc.swsoft.net (64.131.90.221) 67.750 ms 67.930 ms 67.192 ms
There is no reason that I am aware of why we are going to hw001 first. I've checked resolv.conf - okay. I've checked network - okay. I've also checked route and the arp table show .11 listed. Not sure why.
An help would be appreciated.
Re: Unable to Update License
Posted: Thu Sep 29, 2011 12:26 pm
by hostingguy
Re: Unable to Update License
Posted: Thu Sep 29, 2011 4:34 pm
by KrazyBob
Hmm. Maybe I didn't explain it right. I have one server out of more than 25 that all have the same nameservers. 4.2.2.1 and 4.2.2.2. Only one machine is having issues. It is trying to get to Parallels by going to our 10th virtuozzo server at .11 and then it hits the gateway of .1. All other servers hit the gateway at .1 and straight to ka.swsoft.com.
Thank you for the recourses but I am not getting that message. Actually, the server did update last night.
The question remains why it is trying to hit another server of ours before going outside no matter where.
Code: Select all
[root@hw003 ~]# ping yahoo.com
PING yahoo.com (98.139.180.149) 56(84) bytes of data.
From 65.44.220.11: icmp_seq=0 Redirect Host(New nexthop: 65.44.220.1)
64 bytes from ir1.fp.vip.bf1.yahoo.com (98.139.180.149): icmp_seq=0 ttl=49 time=89.6 ms
From 65.44.220.11: icmp_seq=1 Redirect Host(New nexthop: 65.44.220.1)
64 bytes from ir1.fp.vip.bf1.yahoo.com (98.139.180.149): icmp_seq=1 ttl=49 time=96.7 ms
From 65.44.220.11: icmp_seq=2 Redirect Host(New nexthop: 65.44.220.1)
64 bytes from ir1.fp.vip.bf1.yahoo.com (98.139.180.149): icmp_seq=2 ttl=48 time=100 ms
From 65.44.220.11: icmp_seq=3 Redirect Host(New nexthop: 65.44.220.1)
64 bytes from ir1.fp.vip.bf1.yahoo.com (98.139.180.149): icmp_seq=3 ttl=48 time=93.5 ms
From 65.44.220.11: icmp_seq=4 Redirect Host(New nexthop: 65.44.220.1)
64 bytes from ir1.fp.vip.bf1.yahoo.com (98.139.180.149): icmp_seq=4 ttl=49 time=88.0 ms
Re: Unable to Update License
Posted: Thu Sep 29, 2011 4:38 pm
by hostingguy
Does it have a wierd route?
# route -N
Re: Unable to Update License
Posted: Thu Sep 29, 2011 4:44 pm
by KrazyBob
Changing DNS to OpenDNS in resolve.conf still runs the same route. As to your question I tried that. This is a dedicated server with three Plesk servers on one hardware node. Powerful server.
Code: Select all
[root@hw003 etc]# route -N
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
65.44.220.191 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.137 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.138 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.129 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.131 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.130 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.133 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.132 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.135 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.134 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.235 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.238 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.236 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.237 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.210 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.209 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.208 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.203 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.202 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.201 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.200 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.207 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.206 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.205 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.204 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.195 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.194 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.193 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.192 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.199 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.198 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.197 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.196 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.60 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.56 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.57 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.58 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.221.62 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.221.63 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.221.37 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.221.38 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.221.32 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.221.33 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.221.40 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.221.28 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.221.27 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.127 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.124 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.125 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.122 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.123 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.120 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
65.44.220.121 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
192.168.220.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
65.44.220.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 65.44.221.1 0.0.0.0 UG 0 0 0 eth0
Re: Unable to Update License
Posted: Thu Sep 29, 2011 4:48 pm
by hostingguy
only thing I can think of is removing the 169.254.0.0 route and adding NOZEROCONF=yes into /etc/sysconfig/network (and maybe restart network service).
Re: Unable to Update License
Posted: Thu Sep 29, 2011 7:05 pm
by KrazyBob
What is 169.254.0.0 used for? It's on all of my hardware nodes and I assumed associated with Plesk or Virtuozzo. Only this server is having the issue of convoluted DNS routing.
Re: Unable to Update License
Posted: Thu Sep 29, 2011 10:44 pm
by hostingguy
Its a default non routable ip that gets auto assigned when dhcp cant assign an ip
Re: Unable to Update License
Posted: Thu Sep 29, 2011 11:58 pm
by KrazyBob
I looked it up and understand. But we don't use DHCP. Each server has a dedicated public IP.
Re: Unable to Update License
Posted: Fri Sep 30, 2011 12:56 am
by hostingguy
Either way it should be safe to remove