Scheduled maintenance

Hexagon will have a scheduled maintenance on Thursday May. 6th from 12:00.
This is to fix problem with cabinet 7.
The queue have a reservation in place such that only jobs that can complete (according to asked for walltime) before the maintenance will start.
This note will be updated when we have more information.

Update: Maintenance has been moved to Monday May 10th, from 12:00

Update: 10.05, 18:20 Maintenance finished, machine is back online.

Hexagon will have a scheduled maintenance on Monday Feb. 8th from 13:00 to approx. Tuesday late evening Feb. 9th.
The following operations will be performed during maintenance slot:
* Base software upgrade from CLE2.1 to CLE2.2
* Optimization of /work filesystem metadata
* Hardware maintenance
The queue have a reservation in place such that only jobs that can complete (according to asked for walltime) before the maintenance will start.
This note will be updated when we have more information.

NB! Users are encouraged to recompile all binaries after performed maintenance. This is due to a new CLE release.

Update: We will try to start maintenance at 12:30 instead of 13:00 since only few jobs are running.

Update: 09/02/2010 21:25 Maintenance finished. Hexagon is online.
Please remember to recompile all your programs!
Before contacting support please be sure that you have recompiled your code, this will speed up your case processing.

Hexagon will have a scheduled maintenance on Monday Nov. 23rd from 13:00 to approx. 19:00. Some software updates and hardware replacements will be made. The queue have a reservation in place such that only jobs that can complete (according to asked for walltime) before the maintenance will start.
This note will be updated when we have more information.

Update: 19:08 Maintenance finished, system is up and open for users.

Due to a needed security update that requires a reboot we will be forced to do the next maintenance of hexagon earlier than planned. We will therefore have a scheduled maintenance starting on Thursday Sep. 10th at 13:00.

Job-scheduler reservation is now in place so that only jobs that can finish (according to requested walltime) before the scheduled maintenance will be allowed to start.

During the maintenance we will install a security update as well as replacing a few faulty hardware components.

We will update this note when we have more information about expected length or ongoing progress for the maintenance.

As usual, send any questions to support-uib@notur.no.

Update 16:30: Machine is now up again and ready for use.

We will have a scheduled maintenance for fimm cluster on Monday December 15th at 09:00. Estimated downtime is 8 hours. Task is to extend /work and /work2 directories.

Update 15th, 08:15: The login node has been blocked for new connections. It will be made available again as soon as the upgrade has been completed.

Update 16th, 00:10: Fimm is now, after some delay, updated and available for all users. /work and /work2 has been upgraded with more capacity. The queuing system and the scheduler has be upgraded to a newer version. The global file system has also be upgraded together with the latest kernel.
We have also removed the intel compiler from PATH, and replaced it with the pgi compiler. You can however still use the intel compiler, after executing "module swap pgi intel". If you experience any trouble please inform us at support-uib@notur.no.

We will install a 10Gb card on the server providing /migrate and /bcmhsm today at 14:45. The downtime should be minimal.

Update 15:30: The server is now up again. The server connected to the tape robot is not, so /migrate, /bcmhsm files which are on tape will not be available until this has been solved.

Update 16:00: Tape robot is now available. All systems should now be available.

We will have a short scheduled maintenance for hexagon on Monday November 17th at 13:30. Estimated downtime is 1 hour. Task is to apply a patch for a memory bug.

Update Monday 17th 12:15, due to empty queue system and an issue with the batch system scheduler we did the restart early, we are sorry for any inconvenience this may have caused.

Update 12:30, machine is now running again.