The failure of a routine maintenance procedure resulted in an outage.
Category Archives: Uncategorized
Unscheduled Outage: password.emu.edu unavailable
password.emu.edu is unavailable for password resets.
Scheduled: Upgrade Moodle to v3.7
We will be upgrading Moodle to version 3.7 on Monday, July 15th from 5:00 PM to 9:00 PM.
For more details about Moodle 3.7 please refer to the new features tour or the version release notes. There is also a series of videos that describe new version 3.7 features.
Please contact the Helpdesk with questions or comments: helpdesk@emu.edu or 540.432.4357 (x4357 on the Harrisonburg campus).
Update 2019-07-15 6:41 PM: The upgrade is complete. Moodle is once again available.
Scheduled: Major core upgrade; significant outage
Update: at 11:35 am the update and related tasks were completed successfully, ahead of schedule.
On Saturday, August 3, we will be taking a core network component offline for a software upgrade. This will result in a complete outage of all technology and telecommunications services in Harrisonburg , Lancaster, and Washington (WCSC) as well as most web and internet services EMU provides to off-campus audiences. We plan to maintain availability of the main website, www.emu.edu, to external audiences by using cloud technology. All other services will be unavailable (including telephone service). The procedure will begin before 8 am and if all goes well, should be complete by noon, though it is anticipated that an outage of this magnitude will have some unintended consequences that will need to be addressed after the main procedure.
If you have any questions, please contact the helpdesk, helpdesk@emu.edu or 540-432-4557.
Unscheduled: major data storage system failure
Due to multiple problems occurring simultaneously, a data storage system failed and was very troublesome to restore. Not all problems are as yet resolved, but services have been restored. A large number of services were affected, including but not limited to Jenzabar J1, all web servers, and mapped drives.
Unscheduled: Internet connectivity issues
We are experiencing some anomalies with our internet connectivity. The cause and resolution is still being investigated.
Update: as of 6 pm, we believe all factors contributing to the issues have been identified and resolved. We do not expect further connectivity problems.
Scheduled: CashNET
CashNET
System Downtime during failover to Azure Saturday, June 8, 3:00 PM – 3:30 PM ET
AZURE TESTING WINDOW Saturday, June 8, 3:30 PM – 5:30 PM ET
SYSTEM DOWNTIME DURING FAIL-BACK TO AWS Saturday, June 8, 5:30 PM – 6:00 PM ET
This maintenance is part of CashNET’s effort to create a Disaster Recovery site hosted on the Microsoft Azure cloud.
The test will be a failover test where we will completely switch the connectivity of all Transact payments powered by Cashnet services in both Train and Production from the AWS infrastructure to the Azure DR infrastructure.
During the testing window, EMU will test some of these interfaces used by Transact payments:
Lookup
Transaction Posting
Status Posting
Single Sign-On
G/L Validation
eMarket Checkout/Gateway Requests
eMarket Merchant Notifications
Web Services
4:48 PM Update: Online donation processing and online payment of student accounts have been down since 3PM. I am not expecting that these services will be restored until 6PM.
Unscheduled: Lancaster network and phone service
Due to a device malfunction, network and phone service are unavailable at the Lancaster office. Restoration efforts are under way.
Update: as of 10:35 am the issue has been resolved.
Scheduled: myEMU
As a follow up to the problems experienced March 18, Jenzabar needs to do additional work on the myEMU server. That will be done between 6:00 AM and 6:20 AM on March 19. myEMU will be inaccessible during a portion of that time.
6:13 AM: Maintenance work is complete
Unscheduled: myEMU
On March 18, 2019 EMU experienced difficulty communicating between the myEMU server and the J1 database server. This resulted in people being unable to lookup account balances, run PDF reports (including unofficial transcripts) using myEMU.
To resolve this issue Jenzabar restarted the myEMU server. My EMU was unavailable from 3:35 to 4:43 PM.