Page Comparison

This is a reverse-chronological log of all work done in the platform AWS account. 

Deploy fix for staging portal v 1.5.4 by Mat on 2012/08/07

1. Upload .war file using SynapseDeployer
2. Deploy
3. Smoke test
   1. Login with openID, logout
   2. Login with correct Synapse user/pwd
   3. Verify fix for PLFM-1417 

Setup prodA as staging by Matt and Xa on 2012/07/31

...

1. Stop prodBSearchUpdater
2. Drop and re-create prodB schema
3. 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...
4. Start migration from Prod to ProdB
   • Migration took about 1.5hr
   • Put repo in RO mode
5. 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
6. Restart App for portal and auth
   • No change
7. 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)
8. Put repo back in RW mode

...