This is a reverse-chronological log of all work done in the platform AWS account.
...
- Since the deployment script is broken (see:
), I manually uploaded the war files (Upload in the AWSÂ Web Console has been fixed!):Jira Legacy server JIRA (sagebionetworks.jira.com) serverId ba6fb084-9827-3160-8067-8ac7470f78b2 key PLFM-1351 - services-repository-1.0.1.war
- services-authentication-1.0.1.war
- portal-1.0.2.war
- Deployed the respective wars to Synapse prodA.
- I was unable to run the smoke tests on prod-a due to
.Jira Legacy server JIRA (sagebionetworks.jira.com) serverId ba6fb084-9827-3160-8067-8ac7470f78b2 key PLFM-1352
Update prod to 1.0.0 on stack A by Xa on 6/20
...
- Stop prodBSearchUpdater
- Drop and re-create prodB schema
- Restart App repo-prod-b on AWS
- tables are not being created
- looking at tomcat logs, looks like the app did not terminate in time
- tried restart again but it looks like app not responding
- try rebuild env to force shutdown of tomcat
- had to do it a couple if times, no idea why failed the first time...
- tables are not being created
- Start migration from Prod to ProdB
- Migration took about 1.5hr
- Put repo in RO mode
- Getting 'An error occured trying to load' from portal when trying to display entity (tried 4492, 4494, 4496)
- Does not look like a repo issue, I can get the entities from Python
- Cannot login using Google account (error from auth) or Sage account (says I'm not authenticated)
- Can login from Python
- Restart App for portal and auth
- No change
- Log into auth/portal EC2 to look at logs
- Nothing special in auth
- After getting error msg about load failure, following msg in portal log:
"Cannot find user login data in the cookies using cookie.name=org.sagbionetworks.security.user.login.data" >> Normal since I did not login? - No log entry on login failure
- ~2:30am: Timeouts from repo (maybe connected to instance being removed)
- Put repo back in RW mode
...