We need to perform an emergency shutdown and restart of one of the Fram file system controllers. This might cause instability for the file system on Fram between 12:00 and 18:00 today, Wednesday 12th August
Dear Fram users,
We have to do emergency maintenance on Fram storage system, one of the controller has to be rebooted to eliminate errors, during the maintenance /cluster filesystem speed will be degraded. we will update you here.
11:50 Maintenance is over, controller is rebooted. Filesystem performance is back to normal.
Queueing system on Vilje has crashed. We are working on a fix
There seems to have been a problem with the Fram /cluster file system between 23:50 on Friday and 00:30 on Saturday. Symptoms were error messages like “No space left on device”. Because of this problem lots for compute nodes are drained. we are investigating the problem.
We need to take down Stallo for work on building infrastructure. Downtime will be from Tue June 2nd 12:00 until no later than Thu June 4th 12:00. We apologize for the inconvenience.
Vilje queueing system was unavailable from Sunday 5th 15:30 until monday 6th 08:30, due to a faulty infiniband cable.
We apologize for the inconvenience.
NIRD storage system was crashed and unavailable for short period of time.
Due to this crash, users logged in to NIRD and Fram experienced problemes.
The problem is resolved, NIRD storage system is online now.
Please contact us if you still encounter problems.
Note: The export of NIRD to FRAM does not work currently
2019-11-13-16:15 Fram is up and running again.
One of the cooling units stoped, causing the other to also stop and all compute nodes went down.
Dear Fram User,
Fram is currently down likely due to issues with the cooling distribution unit.
We are currently investigating the issue and working on placing Fram back into production.
Apologies for the inconvenience!
Dear Fram cluster users:
login-1-2 will be reinstalled, and will be removed from DNS temporarily. It will be added back to DNS when reinstallation is over.
Update: 15:12 login-1-2 is reinstalled and added back to the DNS configuration.
The node mentioned above has to be rebooted due to its unresponsiveness. We are sorry for any inconvenience.