Category: Outages

At about 12:15, the Moodle outage was resolved. For the moment, we have removed two of the nodes from the cluster, which will cause a slight performance hit. We will add them back as quickly as we can.

Moodle is currently unavailable. ITS is working to diagnose and resolve the issue.

As of 7:50PM, the Moodle authentication issue has been resolved. The root cause was the failure of a supporting application login that happens as part of the Moodle login process.

Moodle is not currently accepting new logins. People who are already logged in are fine. ITS is working to diagnose the issue.

The Registrar’s Office will be manually restoring add/drop data over this weekend. The Hub will remain unavailable to students, faculty, and staff until after this weekend’s data recovery work is completed. We have identified the cause of this problem; next week we will be adding additional protections against a recurrence. We are sorry for the inconvenience and are grateful for your patience and support. 

We are currently working to restore the data to the state it was in at 9:30PM on Wednesday, March 31st and are working with campus departments to determine which data entry since then can be recovered and which will need to be reentered. We will send another update in a few hours.

We are experiencing a critical issue with Colleague this morning and have deactivated The Hub and Colleague. We know your rosters and schedules will be inaccurate this morning, and we are working to restore them.

At approximately 10AM this morning Moodle became very sluggish, with long load times which resulted in login failures for some users. ITS allocated additional server resources to Moodle, which has…

Login pages for Reason-hosted sites are working again. A disk had run out of free space, causing the issue. The outage lasted from approximately 8:25AM until…

There is a problem with the login page for Reason-hosted sites (apps.carleton.edu pages). Most people see the login screen reload after entering their login info. Our team is aware of and working on the issue, though there is currently no estimated time to resolution.