MonMW Server Error 500 on Browse and Sites

This topic has 2 replies, 2 voices, and was last updated 2021-10-18 at 4:47 PM by Anthony Aufdenkampe.

Viewing 2 reply threads

Author

Posts
- 2021-10-18 at 3:39 PM #16064
  Anthony Aufdenkampe
  Participant
  Hi All,
  
  The Monitor My Watershed development team is working on a fix for today’s error with accessing any site information or data. It started last night and is connected to an issue that surfaced early this summer.
  
  We implemented a short-term fix, but that’s not sticking.
  
  We know what the long-term fix is, but it’s a bit more complicated to implement. We should have that done by this evening. It may fail on and off a few times until then.
  
  We’re tracking progress on GitHub here: https://github.com/ODM2/ODM2DataSharingPortal/issues/509
  
  Our team has been actively working this summer on a migration to cloud hosting on Amazon Web Services (AWS), and this kind of issue will no longer be possible once that happens.
  
  We’re targeting release 0.12 on AWS for December 1. Track our progress with these Milestones:
  - v0.12-beta: Port Full MonitorMW Web App to Staging on AWS
  - v0.12-release: Live Production MonitorMW Web App on AWS
- 2021-10-18 at 4:18 PM #16065
  Dave Bressler
  Participant
  Thank you @aufdenkampe! Very helpful and informative update.
- 2021-10-18 at 4:47 PM #16066
  Anthony Aufdenkampe
  Participant
  We think we’ve got it resolved (thanks @ptomasula!).
  
  The main MMW site is back up and data looks to be flowing to the database server again.
  
  We’re rebuilding the tsa_catalog now, so there might be some short term glitches with interactions to TSA capabilities and sparkline plots.
  
  Unfortunately, some data was lost last night, before were able to address any of this.
Author

Posts