Reports until 20:42, Tuesday 22 September 2015
H1 General
peter.shawhan@LIGO.ORG - posted 20:42, Tuesday 22 September 2015 - last comment - 16:27, Wednesday 23 September 2015(21824)
GWIstat fixed 
Cheryl and Jeff brought to my attention that GWIstat was reporting incorrect information today.  It turns out that the ~gstlalcbc home directory at Caltech was moved to a new filesystem today; GWIstat gets its information from a process running under that account, and apparently got into a funny state.  I have now restarted it.  For the rest of the current observing segment it will report the duration only from the time I restarted it, about 3:32 UTC.  I apologize for the problem!
Comments related to this report
peter.shawhan@LIGO.ORG - 06:15, Wednesday 23 September 2015 (21836)
Link 

I see this morning that GWIstat is not showing the correct duration for the current observing segment.  The log file on ldas-grid.ligo.caltech.edu, where it is now running, shows that it was restarted twice during the night for no obvious reason, and it is reporting the duration only since it was restarted.  I'll ask the Caltech computing folks to look into this.  New hardware for ldas-grid was put into use yesterday, and maybe they were still shaking it down last night.
peter.shawhan@LIGO.ORG - 16:27, Wednesday 23 September 2015 (21866)
Link 

Stuart Anderson told me this is a known problem that seems to have arisen from a condor configuration change.  They know how to fix it but will need to restart condor.  Until they do that, gwistat should indicate status correctly (except for momentary outages) but may sometimes display the wrong duration for the current state.