Host not responding

[djs52]

Since my VPS came back up after the vm1.unixshell.com outage I haven't been able to get networking going at all. It's got the right IP address but no data seems to be passing. I can only get in using the console. The default route goes to 169.254.1.1 but I assume this is deliberate...

Any ideas? I'm really hoping I haven't made some stupid configuration change!

[djs52]

Err.. okay, forget it. I rebooted and now it's fine. I wonder what happenned, though...

[nsuan]

I seem to be having a similar problem. My VPS will pass traffic fine for a while then stop, and the only way I can get it to work again is to reboot it.

[djs52]

I've been monitoring this for a bit. It seems that networking dies when the OOM killer is activated, and nothing will bring it back after that. I guess I need more memory :-(

[nobaloney]

We have nothing on the server; in fact we just finished installing the new OS and started it.

It wasn't visible on the network.

That was last night.

This morning, after reading more threads, I restarted my virtual server.

It's on the 'net now.

But if it's a memory problem, then 128K isn't enough at all.

Jeff

[dgirgis]

My VPS was in a similar state this morning. Hopefully this problem can get figured out. Had to reboot it to get it to talk again.
Before I rebooted, looked in through the console and checked the memory usage. It is a 64M VPS, the physical memory was used but only about 20M of 128M total swap was being used. This indicates it still had plenty of memory to work with? Also at this stage no iptables rules are running on this particular VPS, hopefully we can figure out what is going on. Was going to migrate virtuozzo vps this weekend, but it might be better to figure this out in a non-production state.

Dave

[matta]

Check the thread in outages, this should be taken care of now.