Displaying report 1-1 of 1.
Reports until 09:54, Monday 04 August 2014
H1 CDS
jeffrey.kissel@LIGO.ORG - posted 09:54, Monday 04 August 2014 - last comment - 13:31, Monday 04 August 2014(13179)
H1ISIETMX Model Restart Kills Streamers on h1sush2b, h1oaf, and h1lsc
J. Kissel, J. Batch,

Jim informed me this morning that other front-end models, seemingly unconnected to my h1isietmx model restart, had their framebuilder data corrupted immediately following my restart. Hence all frame data from these computers has been hosed since 2014-07-31 22:45 UTC. See Jim's complementary log here.

The corruption is a result of an mxstream glitch sent out by h1isietmx upon restart, that was sent across the ethernet connection to other computers on the same ethernet network (i.e. h1sush2b, h1oaf, h1pemmy, h1pemmx, h1susey and h1lsc). This is a known problem at least by Jim (who will subsequently write a bugzilla report).

To identify the problem:
- Open CDS_OVERVIEW screen
- Look for models / computers that have *both* the DAQ (Data AQuisition system) and the DDC (Daq Data Concentrator) showing red status in their CDS STATE WORD, (e.g H1:FEC-103_STATE_WORD).

To solve the problem:
- Log into corrupted front-end
- run /etc/start_streamers.sh
This reboots the mxstream process, occasionally glitches the framewriting PSL front end (?!), presumably fixes the problem, and restores the STATE WORD to green.
Comments related to this report
keith.thorne@LIGO.ORG - 13:31, Monday 04 August 2014 (13193)CDS
The old /etc/start_streamers.sh command may not be the best way.  Instead use "sudo/etc/init.d/mx_stream stop", "sudo/etc/init.d/mx_stream start" so it starts the mx_stream on the correct 'mx' slot for the data concentrators's Myricom card
 - Of course, LHO may have been cleverer than I and re-wrote /etc/start_streamers.sh to do this
Displaying report 1-1 of 1.