Ok, that was weird
I rebooted my system, and all is well, but I'm wondering if anybody else had any problems with host41 last night, or if it was something died on my linode itself?
12 Replies
There were other people in IRC with the same problem, and taking the eht0 interface down and bringing it back up also fixed it.
I guess we'll get an explanation when daylight breaks in Texas or Florida :-)
In the end I rebooted it so I'd get the upgrade to 80M of RAM, but I did wonder if bouncing the ethernet interface would fix it.
It's a bit worrying that this seems to have affected different hosts with the same problem. I hope Caker can get to the bottom of this.
/etc/init.d/networking restart
fixed everything.
root@linode:~# netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 70.85.16.41:80 137.203.140.95:1371 SYN_RECV
tcp 0 0 70.85.16.41:80 137.203.140.95:1373 SYN_RECV
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 70.85.16.41:22 137.203.143.138:3318 SYN_RECV
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN
tcp 0 0 70.85.16.41:25 209.79.220.26:47299 SYN_RECV
tcp 0 0 70.85.16.41:25 195.121.6.174:28183 SYN_RECV
tcp 0 0 70.85.16.41:25 81.228.11.98:40643 SYN_RECV
tcp 0 0 70.85.16.41:25 200.221.4.129:45199 SYN_RECV
tcp 0 0 70.85.16.41:25 195.110.126.63:2362 SYN_RECV
tcp 0 0 70.85.16.41:25 213.134.38.68:13845 SYN_RECV
tcp 0 0 70.85.16.41:25 195.6.202.253:41413 SYN_RECV
tcp 0 0 70.85.16.41:25 194.83.112.9:34206 SYN_RECV
tcp 0 0 70.85.16.41:25 207.115.20.47:57167 SYN_RECV
tcp 0 0 70.85.16.41:25 193.109.255.35:54714 SYN_RECV
tcp 0 0 70.85.16.41:25 66.118.64.16:46311 SYN_RECV
tcp 0 0 70.85.16.41:25 62.79.79.29:58677 SYN_RECV
tcp 0 0 70.85.16.41:25 149.155.202.2:35862 SYN_RECV
tcp 0 0 70.85.16.41:25 195.6.202.218:41413 SYN_RECV
tcp 0 0 70.85.16.41:25 206.131.246.136:36753 SYN_RECV
tcp 0 0 70.85.16.41:25 203.12.160.101:36642 SYN_RECV
tcp 0 0 70.85.16.41:25 71.36.29.90:4281 SYN_RECV
tcp 0 0 70.85.16.41:25 195.188.213.9:27615 SYN_RECV
tcp 0 0 :::22 :::* LISTEN
udp 1700 0 0.0.0.0:68 0.0.0.0:*
"/etc/init.d/networking restart" command on Debian from lish fixed it.
Went down around 1030 GMT
@drware:
"/etc/init.d/networking restart" command on Debian from lish fixed it.
If you're using Gentoo, as I am, this is the command to use:
/etc/init.d/net.eth0 restart
(This is from host45)
root@overbeck:~#
root@overbeck:~# arp -a
? (70.85.129.1) at 00:00:0C:07:AC:07 [ether] on eth0
root@overbeck:~# arp -d 70.85.129.1
root@overbeck:~# arp -a
gateway12.linode.com (70.85.129.1) at
root@overbeck:~# arp -a
gateway12.linode.com (70.85.129.1) at 00:00:0C:07:AC:01 [ether] on eth0
Simple fix: flush the arp table entry for your gateway. (you don't have to cycle the interface, just fix the arp table.)
It fixed itself after about 10 min.
- Robbert