...
Area | Problem | Comments | Resolution |
---|---|---|---|
Monitoring | Comparing Histograms | It is not currently possible to compare the same histogram from different runs |
|
Login | Login in GLAST data portal | One user was not registered in the glast user database, several users had missing SLAC username's | Fixed |
Tomcat | alarms summary doesn't work | Connection broken between IIS and server. Not a crash | The tomcat server was restarted. A page has been created for tracking similar outages http://confluence.slac.stanford.edu/x/qQFV |
Data Monitoring | Alarm summary still not working | User gave no useful info in message | Ignored |
ASP | overlapping bars in ASP flares |
| Fixed |
Glast Ground | Menu item for shifts had not been updated since Ops Sim 1 |
| Fixed |
Data Monitoring | Problems with Alarm documentation |
|
|
Data Access | skimming on single runids gives bad files | It is currently not easy to skim OpsSim2 data because of multiple versions of the same files. |
|
Data Access | Problems using download manager with CAL files | Cal files are getting negative file sizes. Download managed chokes on these. | Several JIRA's created: GDCB-49@JIRA DATASERV-104@JIRA |
Data Monitoring | plot not showing the value that triggered the alert? |
|
|
Data Access | Data processing files inaccessible | A tomcat server was down. | The server was restarted and the error recorded at http://confluence.slac.stanford.edu/x/qQFV |
| missing plots |
|
|
Tomcat | Monitoring seems to be down again... | Not reproducible |
|
ASP | Problem with GCN notices |
|
|
Documentation | Who is on shift in Confluence | Link in confluence page was broken | Fixed |
ASP | ASP Start time and End time |
|
|
| Can not access page directly |
|
|
| TowerCalLayerCalColumnCalXFace plots not being displayed |
|
|
ASP | Source Monitoring | User was using wrong tool | User instructed to use http://glast-ground.slac.stanford.edu/ASPDataViewer |
Pipeline | GLAST PIpeline II PAge | Request to make it easier to identfy failed runs | JIRA created: PFE-156@JIRA |