Following recent incidents we would like to remind you as well as stress that our terminal servers plimpy.ethz.ch and plompy.ethz.ch must not be used for long running or resource demanding computation jobs. Please use our computation node plumpy.ethz.ch instead.
(more…)

Our terminal server plimpy (uptime: 47 days) is slowly clogging up with runaway processes, eating up memory and CPU. Since we cannot tell apart good processes from bad ones, we schedule a maintenance reboot for the Weekend, Saturday night June 19th in order to give the system a fresh start. We ask all users to save their data and log out of their thin clients.

BTW: Users of second generation thin clients (named tc00xx) are kindly invited to test our new ubuntu based terminal server plompy. If you're interested to give it a try, please let us know and we will configure your client.

In order to relieve our Terminal Server plimpy of some of its computational burden, we assigned it a new sidekick specifically targeted at number crunching tasks: plumpy.ethz.ch

So if you've been using plimpy to perform calculations in the past, please ssh into plumpy from now on and do your work there. This should make both you and the plimpy users happy. Thank you.

Our terminal server plimpy (uptime: 80 days) is slowly clogging up with runaway processes, eating up memory and CPU. Since we cannot tell apart good processes from bad ones, we schedule a maintenance reboot for tomorrow, Wednesday February 24 at 18:00 in order to give the system a fresh start. We ask all users to save their data and log out of their thin clients. Update, 18:45: Plimpy is up and running again.

Today at 16:41 a process on our terminal server plimpy freaked out and consumed all memory + swap, causing a complete halt of all other processes. We had to reboot the machine. We're currently looking into ways to prevent this problem from appearing again in the future. Sorry for your inconvenience.

Today around 14:20 the D-PHYS network started acting up. After about 20 minutes the problem could be tracked down to a machine running amok. Unfortunately, the terminal server plimpy did not survive the downtime and had to be rebooted at 16:10. We apologize for any inconvenience.

On Wednesday, April 8, starting around 0730 we will upgrade the RAM in plimpy, our LTSP terminal server. This will cause a downtime of about 5 min and the loss of all open sessions. Please make sure to have all your data saved by Tue evening if you're working on a thin client.

Update Wed 0800: plimpy now has 16 gigs.