40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  ATF eLog  Not logged in ELOG logo
Entry  Wed Sep 1 02:21:23 2010, rana, Computing, DAQ, some restarts on fb0: too many cooks 
    Reply  Wed Sep 1 04:43:45 2010, Dmass, Computing, DAQ, some restarts on fb0: too many cooks 
    Reply  Fri Sep 3 14:45:20 2010, Dmass, Computing, DAQ, Undocumented change? 
       Reply  Sat Sep 4 00:44:20 2010, Dmass, Computing, DAQ, Undocumented change? 
          Reply  Sat Sep 4 01:49:23 2010, Dmass, Computing, DAQ, Undocumented change? 
             Reply  Sat Sep 4 02:21:46 2010, Frank, Computing, DAQ, Undocumented change? 
                Reply  Sat Sep 4 03:34:42 2010, Dmass, Computing, DAQ, Undocumented change? 
                   Reply  Mon Sep 6 16:23:19 2010, Dmass, Computing, DAQ, SSHD (re?)started 
Message ID: 1018     Entry time: Sat Sep 4 02:21:46 2010     In reply to: 1017     Reply to this: 1019
Author: Frank 
Type: Computing 
Category: DAQ 
Subject: Undocumented change? 

Quote:

Quote:

Quote:

I could not ssh into fb1 from ws2 to run apps (DTT). I checked from the outside world, and same thing. 131. 215.115.216 no longer says hello.

Did someone reconfigure something to disable ssh'ing, or is this a spontaneous change?

 As of 12:40 am Sat morning, I can no longer get data from offsite (my channel list request fails). It was working this afternoon, and seems to have been working 40 minutes ago when I asked it for 2 hours of 256 Hz, but it may have choked on that.

 As of 1:48 AM the error is:
C
Warning: Error number -1 while querying for C2:ATF-DAQ1_GEN2_OUT_DAQ

darkness =

        name: 'C2:ATF-DAQ1_GEN2_OUT_DAQ'
        data: []
        rate: 256
       start: 967625192
    duration: 18

On a get data. Same for other channels.

The only thing I have done to the entire front end set up is add a DAQ channel, and killed the daqdaemon (on fb0).

 i think you have to reload the daq too, otherwise the channel count and datarate of the daq (rt model running) is different from the one of the daqd expects to find. They use a shared memory to exchange data. If think you don't reload the daq the amount and order of data/channels exchanged is different from what the daqd expects to find in the shared memory (and maybe in which order). We should ask alex if this is true..

You can find that button in the upper left corner of the main medm screen for your subsystem.  The last time we had this issue i reloaded the daq, reloaded all filters and coefficients (which both i think are not necessary) and then restarted the daqd by using sudo pkill daqd and everything worked fine.  That's how did this all the time with the psl subsystem and i never had problems with getting data from that...

ELOG V3.1.3-