Newark6 became unresponsive and was rebooted. Linodes on newark6 are being brought back up now.

Mike

I've got a linode on each of these two servers and noticed that both become unresponsive since (moreless) 9:30 GMT on newark11 and (moreless) 10:30 GMT on newark17.

In both case, in the dashboard I've seen 100% CPU activity and no disk I/O.

Even pinging to these linodes was not possible.

I've rebooted both from the dashboard around 11:45 GMT and they've come back fine.

Was there a general problem in this datacenter ?

Benoit

@bgerrienne, no -- the problem is only with newark6.

Newark6 rebooted again a few minutes ago. We're still looking into the cause, but it may be that this machine has some unhappy RAM. I've made a BIOS setting tweak, and we'll see how things go from here. If this continues, we'll queue up migrations onto another server.

Sorry about this,
-Chris

@caker, unfortunately -- dallas56 seems to have suffered something too

The graphs show my linode started using 100% cpu at 7am.
I just noticed this now, and searched the forums for similar cases.

Regards