system news

Batch queue malfunction on Kebnekaise

  • Posted on: 24 February 2017
  • By: zao

During a routine upgrade of the batch system SLURM on Kebnekaise intended to improve the amount of usable memory on the large memory nodes, we encountered an unexpected malfunction.

This discarded all running and scheduled jobs.

We're working on restoring functionality and will update this system news entry.

Update 2017-02-24 15:42 CET:
The new version of SLURM misbehaves greatly and the commands to interact with it are very slow or not responding at all. You may consider the Kebnekaise cluster down for all practical purposes for now.

Emacs on Kebnekaise

  • Posted on: 23 February 2017
  • By: zao

We have resolved a long-standing problem with Emacs on the kebnekaise login node. If you had any form of X forwarding enabled invoking emacs would result in a segmentation fault which necessitated a workaround by starting it with the argument -nw.

This is no longer necessary as we have patched the offending library, so now you get a properly working graphical Emacs if you have X forwarding. If you wish to run a textual Emacs in such an environment the argument -nw still exists and works as intended.

Network problems on Abisko, 2017-02-07

  • Posted on: 7 February 2017
  • By: bbrydsoe

We have been having some network problems on Abisko since late Sunday (2017-02-05) evening. These are mostly solved, but there are still some remaining issues which we are investigating. There is a risk that this may affect a small number of running jobs.

In addition, this means that a number of nodes have temporarily been taken out of production. This means there are fewer available nodes, which may affect the queue time negatively on Abisko.

This system news will be updated when there is more information.

Kebnekaise - removing toolchains intel 2015b,2016a, and 2016b

  • Posted on: 22 November 2016
  • By: ake

Due to bugs in the compiler we are removing the following toolchains:

intel/2015b, intel/2016a, and intel/2016b

We are going to do a switchover to a new build, using intel/2017.01 instead of the above toolchains.

The switchover will be disruptive in sofar as all jobs using the old toolchains will fail.

This is unfortunate but necessary. However, since the machine is lightly loaded at the moment there should be no problem catching up on the production for everyone.

Pages

Updated: 2024-04-17, 14:47