Open Problems

Data Quality Monitoring Unresponsive

Symptoms

The DataQualityMonitoring application is unresponsive: No page is returned and the browser keeps on waiting for a response.
Probe is also unresponsive.

Cause

This seems to be due to some threads losing a socket connection with xrootd when trying to fetch root files to display histograms.
Looking at the log files for the DataQualityMonitoring application there is a proliferation of messages like:

WARNING: Waiting for response for 12 secs stat[wain019.slac.stanford.edu/172.23.2.19:1094:anonymous]
Jun 25, 2008 10:25:00 AM org.glast.base.application.web.filter.ApplicationFilter doFilter

As probe is unresponsive to look at the log files you have to log-in glast-tomcat07, cd tomcat/BASE55/glastlnx09/logs and tail the most recent DataQualityMonitoring log file.

Solution

Restart glast-tomcat07 : from the ServerMonitoring application restart the glast-tomcat07 server by clicking on the recycle icon. If you don't see this icon it means you need to be added to the administrators list.

History and Exceptions

Follow this link for a History of the Exceptions

OpsLog, DataQualityMonitoring, TelemetryTrending losing sessions

Symptoms

There are many symptoms linked to this problem. All seem to be due to the fact that the session is expired.

The very strange thing is that these problems seem to be correlated across applications.