Update - We are continuing to monitor for any further issues.
Jun 19, 10:54 AEST
Monitoring - The login node is back online, but Spartan is currently set to DRAIN. Running jobs will continue but new jobs will not start until storage health has stabilised.
Jun 18, 20:17 AEST
Investigating - Spartan is refusing logins, likely due to a networking issue. We are actively investigating.
Jun 18, 09:14 AEST
Login Node   ? Operational
90 days ago
89.83 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Scheduled outage for system upgrades Jul 17, 00:00 - Jul 19, 00:00 AEST
The purpose of this outage is improvement to network hardware, workload manager (Slurm) upgrades, upgrades to the accounts and project management software, and storage upgrades.
Posted on Jun 4, 13:27 AEST
Past Incidents
Jun 24, 2018

No incidents reported today.

Jun 23, 2018

No incidents reported.

Jun 22, 2018

No incidents reported.

Jun 21, 2018

No incidents reported.

Jun 20, 2018

No incidents reported.

Jun 17, 2018

No incidents reported.

Jun 16, 2018

No incidents reported.

Jun 15, 2018
Completed - The scheduled maintenance has been completed.
Jun 15, 16:07 AEST
Scheduled - There will be a system outage from April 4th to 5th for security, storage, kernel, cloud image, etc upgrades.
Feb 27, 11:29 AEDT
Completed - The scheduled maintenance has been completed.
Jun 15, 16:06 AEST
Scheduled - The AAF have an upcoming outage on the 27th March, from 7:30pm to 9:30pm. During this time there may be some disruption to the Discovery Service which may interrupt access to Karaage (our web-based account management tool). There should be no disruption to Spartan during this time.
Mar 26, 10:28 AEDT
Resolved - This incident has been resolved.
Jun 15, 16:06 AEST
Identified - Some users have experienced problems downloading from Spartan's login node.

The root cause is mismatched MTU between spartan physical nodes (which is on 9000) and their VLAN, which is only at 1500. If the download host site is also at 9000 then this mismatch will stop the transmission. The fix will be applied during the next maintenance window.

The workaround in the meantime is to use a proxy i.e run `export http_proxy|https_proxy|ftp_proxy=http://wwwproxy.unimelb.edu.au:8000;` before wget, curl or similar commands.
Jan 16, 11:12 AEDT
Jun 14, 2018

No incidents reported.

Jun 13, 2018

No incidents reported.

Jun 12, 2018

No incidents reported.

Jun 11, 2018

No incidents reported.

Jun 10, 2018

No incidents reported.