Hello. There are a few old postings on this topic but the suggested fixes are don't have any effect. Hopefully some of this is new info. Essentially, the container behaves as though there is firewall blocking TCP over IPv4 in one particular container. The following commands do work as expected: ssh localhost // this connects successfully through the IPv6 loopback address ping 127.0.0.1 // ping replies normally on the IPv4 address and is observable with tcpdump This does not work: ssh 127.0.0.1 Tcpdump shows the IPv4 SYN packets but there is no inbound traffic at all. This is not peculiar to ssh, anything trying to communicate TCP over the IPv4 loopback does not work. Sniffing ssh to the IPv6 address shows the expected traffic. I've not tried UDP. Based on other posts, the ip_forward was set to 1 with no effect. Another post had 127.0.0.1 assigned to multiple interfaces - this is not the case here. iptables is not running. Other containers on the same host do not have this problem and appear to be configured identically to the broken one. For what it's worth, the process we run in the container crashed and management software restarted the container. After the restart, we have this loopback problem. Are there any logging or diagnostics that can be enabled in this area? There are no obvious messages in /var/log/messages. Any other suggestions? Thanks. Tom
on what ip addresses services are listening to? is container have ipv4 address or only ipv6? please also report HN os, kernel and openvz tools versions. please report container os and version. please show netstat -an, ifconfig -a output from the container.
We see the same problem on some containers. The host is running CentOS6, kernel 2.6.32-042stab108.2. The host is newly setup (2 days ago) with the latest tools. There is nothing in the logs. Look at previous posts on the forum, this seems to be an old problem that has either come back or never been resolved.
We see this issue from time to time as well, seems to be related to the number of containers on a node. No failcnt is triggered. Loopback connections (127.0.0.1) randomly time out and we don't see a reason in the logs. We can confirm this problem in kernel 042stab108.8