Overview and Status
The User Guide menu to the left gives instructions on using the MASSIVE cluster.
The User Guide is structured in steps of complexity. The Getting Started section covers the basics of getting an account and the software required to access the account. The next sections detail basic usage of the cluster (Cluster Instructions), usage of individual software packages installed on the cluster (Software Instructions) and common workflows requiring multiple steps and software packages to achieve a specific goal (Workflow Instructions).
For further help in using these instructions on MASSIVE please email firstname.lastname@example.org with the details of the problem you are experiencing.
Current System Status
M3 (Monash University) - m3-login1 and m3-login2 (ONLINE)
M2 (Monash University) - m2-login1 and m2-login2 (ONLINE)
M1 (Australian Synchrotron) - m1-login1 and m1-login2 (ONLINE)
IMPORTANT - UNSCHEDULED Outage - M3 - 14th May
M3 login1 and login2 are currently non-responsive. We are working to determine the cause and return M3 to full operation. We will issue an email update at 3pm today.
IMPORTANT - RESOLVED Outage - M1 and M2 - 6th April
We are pleased to announce that M1 (Synchrotron) and M2 (Monash) are now accepting jobs following yesterday's unscheduled outage. The following services are back online:
- Strudel connections to M1 (Synchrotron) and M2 (Monash)
- Strudel Web connections to M1 (Synchrotron) and M2 (Monash)
- SLURM scheduler M1 (Synchrotron) and M2 (Monash)
-- This includes sinteractive
Jobs that ran at any time within the past 24 hours are likely to have failed with IO errors. We strongly recommend that you examine the output of these jobs very carefully to determine if there is any useful output. Where possible, resubmission of jobs to the queue is the best course of action. We are in the process of contacting users that have had jobs fail as a result of this outage.
Thank you for your patience while we worked to resolve these issues, and we apologise for any inconvenience they may have caused. If you have any questions regarding recent events, please contact us at email@example.com