Project

General

Profile

Running DAQ Interface » History » Version 62

John Freeman, 11/21/2014 10:50 AM

1 58 John Freeman
{{toc}}
2 58 John Freeman
3 49 Erik Blaufuss
h1. Getting help
4 1 John Freeman
5 49 Erik Blaufuss
If you run into issues, or have questions, please contact:
6 49 Erik Blaufuss
* DAQInterface
7 49 Erik Blaufuss
** John Freeman - jcfree@fnal.gov
8 62 John Freeman
* RunControl
9 49 Erik Blaufuss
** Erik Blaufuss - blaufuss@icecube.umd.edu
10 1 John Freeman
11 49 Erik Blaufuss
h1. Starting DAQInterface and Run Control
12 49 Erik Blaufuss
13 49 Erik Blaufuss
DAQInterface is designed to be run, along with rest of the run control code, on lbne35t-gateway01.fnal.gov, using the lbnedaq account.  These instructions will focus the use of DAQInterface on the gateway node.  If you need access to the lbnedaq@lbne35t-gateway01.fnal.gov account, please contact one of us.
14 49 Erik Blaufuss
The DAQInterface and RunControl software can also be run on the lbnedaqtest01 VM machine, please contact John Freeman at jcfree@fnal.gov, for more details.
15 49 Erik Blaufuss
16 49 Erik Blaufuss
The installed code is located at /data/lbnedaq/scratch/DAQInterface/lbnerc. To get started, login and first setup the environment:
17 49 Erik Blaufuss
18 30 John Freeman
<pre>
19 49 Erik Blaufuss
ssh lbnedaq@lbne35t-gateway01.fnal.gov
20 33 John Freeman
cd /data/lbnedaq/scratch/DAQInterface
21 1 John Freeman
source fireup
22 1 John Freeman
</pre>
23 1 John Freeman
24 61 John Freeman
This will take you into the /data/lbnedaq/scratch/DAQInterface/lbnerc directory. It's a good idea to check whether lbnecontrol (the RunControl application), DAQInterface (the component which intermediates between run control, the configuration manager, and the artdaq processes) and the configuration manager are already running; if they aren't, the instructions below won't work. To check for RunControl and DAQInterface, you can try:
25 1 John Freeman
26 1 John Freeman
<pre>
27 49 Erik Blaufuss
lbnecmd check
28 1 John Freeman
</pre>
29 1 John Freeman
30 61 John Freeman
This will display the current state of DAQInterface and RunControl. The example below shows that both RunControl and DAQInterface are running, but the DAQ run is in the stopped state:
31 49 Erik Blaufuss
<pre>
32 49 Erik Blaufuss
(env)[lbnedaq@lbne35t-gateway01 lbnerc]$ lbnecmd check
33 49 Erik Blaufuss
lbnecontrol: running
34 49 Erik Blaufuss
daqint@localhost:5770 (synchronous): stopped
35 49 Erik Blaufuss
</pre>
36 1 John Freeman
37 49 Erik Blaufuss
If RunControl is not running, you'll see something like:
38 1 John Freeman
<pre>
39 49 Erik Blaufuss
(env)[lbnedaq@lbne35t-gateway01 lbnerc]$ lbnecmd check
40 49 Erik Blaufuss
check failed: '[Errno 111] Connection refused'.  Is lbnecontrol running?
41 1 John Freeman
</pre>
42 1 John Freeman
43 61 John Freeman
To check whether the configuration manager is running, you can simply use Linux commands:
44 61 John Freeman
45 61 John Freeman
<pre>
46 61 John Freeman
ps aux | grep -v grep | grep CfgMgrApp
47 61 John Freeman
</pre>
48 61 John Freeman
49 61 John Freeman
This will either return info on the CfgMgrApp process, or print nothing if it's not running. 
50 61 John Freeman
51 1 John Freeman
h3. Starting RunControl
52 49 Erik Blaufuss
53 49 Erik Blaufuss
To start RunControl (after loading environment as above):
54 60 John Freeman
<pre>
55 49 Erik Blaufuss
rm /tmp/lbnecontrol.pid
56 49 Erik Blaufuss
lbnecmd launch
57 49 Erik Blaufuss
</pre>
58 1 John Freeman
59 1 John Freeman
h3. Starting DAQInterface
60 1 John Freeman
61 61 John Freeman
To start DAQInterface (after loading environment as above), the basic command is:
62 1 John Freeman
<pre>
63 61 John Freeman
daqinterface -n daqint -r 5570 -c localhost -H localhost &
64 61 John Freeman
</pre>
65 61 John Freeman
However, particularly if multiple users with different terminals wish to check the DAQ output, it is recommended to try:
66 61 John Freeman
<pre>
67 49 Erik Blaufuss
stdbuf -oL daqinterface -n daqint -r 5570 -c localhost -H localhost >>~/DI.log 2>&1 &
68 1 John Freeman
</pre>
69 1 John Freeman
This will launch daqinterface in the background, with all messages being collected (appended to the bottom of...) in the file ~/DI.log  (The stdbuf -oL prevents and buffering of output to the file)
70 1 John Freeman
Here, the "daqint" argument is arbitrary, and is the name you'll give the DAQInterface process in RunControl; the "5570" argument is the port off of which DAQInterface will run. 
71 1 John Freeman
72 62 John Freeman
h3. Starting the configuration manager
73 62 John Freeman
Please see Jon Paley's documentation here: https://cdcvs.fnal.gov/redmine/projects/fhicl_cfgmgr/wiki
74 62 John Freeman
75 61 John Freeman
h3. Forcing cleanup: performing a hard reset of RunControl, DAQInterface and the configuration manager
76 49 Erik Blaufuss
77 1 John Freeman
If needed, you can track down the process names and kill them explicitly to get a clean reset:
78 1 John Freeman
<pre>
79 49 Erik Blaufuss
ps aux | grep -v grep | grep lbnecontrol
80 49 Erik Blaufuss
ps aux | grep -v grep | grep daqinterface
81 61 John Freeman
ps aux | grep -v grep | grep CfgMgrApp
82 49 Erik Blaufuss
</pre>
83 61 John Freeman
If these processes are running, it either means that someone else is using the DAQ, or that someone else who's done using it forgot to clean up. As the 9th and 10th fields of the row of variables "ps aux" returns concern how long the program has been running, you can use these values as well as your best judgement, then, before deciding these processes are not in active use and killing them.   To kill them, the second field returned from "ps aux" is the process id (PID), use:
84 1 John Freeman
<pre>
85 1 John Freeman
kill <PID>
86 1 John Freeman
</pre>
87 49 Erik Blaufuss
88 1 John Freeman
h1. Configuring and starting Runs
89 1 John Freeman
90 61 John Freeman
All of these steps assume that the configuration manager process is running.  To start this, please see the documentation here: https://cdcvs.fnal.gov/redmine/projects/fhicl_cfgmgr/wiki
91 1 John Freeman
92 61 John Freeman
Now, you can take the DAQ system through the standard transitions to start a DAQ run.  At all stages, you can use the "lbnecmd check" command to see what state DAQInterface is in; note that you'll want to wait for a transition to complete before issuing another one, otherwise you'll receive a warning and the transition request will be ignored. DAQInterface will also report to its log file when transitions are complete:
93 49 Erik Blaufuss
<pre>
94 49 Erik Blaufuss
Initialize transition complete; if running DAQInterface in the background, can press <enter> to return to shell prompt
95 61 John Freeman
</pre>
96 1 John Freeman
Note that if a high "debug level" has been set (see below for more on this), this message can get buried in a set of output messages; in this case "lbnecmd check" may be the easiest way to determine what state the system is in. 
97 1 John Freeman
98 62 John Freeman
h2.  Selecting a configuration and DAQ components
99 49 Erik Blaufuss
100 1 John Freeman
*Before initializing or starting a DAQ run*, a configuration and set of DAQComponents must be selected.  This is done via RunControl.
101 1 John Freeman
102 49 Erik Blaufuss
h3. List and select a configuration:
103 1 John Freeman
104 62 John Freeman
To see the list of available configurations (queried from the configuration manager):
105 49 Erik Blaufuss
<pre>
106 49 Erik Blaufuss
lbnecmd listconfigs
107 1 John Freeman
</pre>
108 49 Erik Blaufuss
Will return a list of configs:
109 49 Erik Blaufuss
<pre>
110 49 Erik Blaufuss
Available configs (Name : description)
111 1 John Freeman
112 49 Erik Blaufuss
demo : Pithy description
113 49 Erik Blaufuss
tmp1 : Pithy description
114 49 Erik Blaufuss
...
115 30 John Freeman
116 49 Erik Blaufuss
Current selected config: No Config
117 49 Erik Blaufuss
</pre>
118 49 Erik Blaufuss
This lists all available configs, as well as the current selected config (Note, default config is "No Config").  You can then select a configuration:
119 49 Erik Blaufuss
<pre> 
120 49 Erik Blaufuss
lbnecmd setconfig demo
121 1 John Freeman
</pre>
122 1 John Freeman
This will return "OK" if successful (at "listconfigs" will show this as the current config).  If the specified configuration is not known, an error is returned.
123 1 John Freeman
124 49 Erik Blaufuss
h3. List and select DAQ components.
125 1 John Freeman
126 62 John Freeman
You can select which portions of the LBNE DAQ setup you want to use in the upcoming run.  These are mapped generally to the ArtDAQ BoardReaderMain processes
127 62 John Freeman
that read them out.   As an operator, you need to ensure that there are configuration files available in the configuration manager for the DAQ Components that you select here,
128 1 John Freeman
or DAQInterface will return an error.
129 38 John Freeman
130 1 John Freeman
To see the list of available DAQ components:
131 49 Erik Blaufuss
<pre>
132 1 John Freeman
lbnecmd listdaqcomps
133 49 Erik Blaufuss
</pre>
134 62 John Freeman
Will return a list of components available and selected (*Default* is ALL available components), e.g.:
135 1 John Freeman
<pre>
136 49 Erik Blaufuss
{'available': {'component02': ['lbnedaq2', '5206'], 'component01': ['lbnedaq2', '5205']}}
137 49 Erik Blaufuss
{'selected': {'component02': ['lbnedaq2', '5206'], 'component01': ['lbnedaq2', '5205']}}
138 49 Erik Blaufuss
</pre>
139 62 John Freeman
Shown are the available components by name, along with the requested host/port to run the BoardReaderMain process on. You can then select a list of DAQ components to use in the run:
140 49 Erik Blaufuss
<pre>
141 49 Erik Blaufuss
lbnecmd setdaqcomps component01 component02
142 49 Erik Blaufuss
</pre>
143 62 John Freeman
This will return "OK" if successful ("lbnecmd listdaqcomps" will show this in the "selected" row of components).  If the specified compnents are not known, an error is returned.
144 49 Erik Blaufuss
To change the list of available components, see below.
145 29 John Freeman
146 49 Erik Blaufuss
h2. Configuring, starting, stopping and terminating a Run
147 1 John Freeman
148 49 Erik Blaufuss
For each of these transitions, please recall that while "lbnecmd <cmd>" returns very quickly, the actual command can take several seconds or minutes to happen.  Before issuing another command, be sure that the transition is complete by using the check command:
149 1 John Freeman
<pre>
150 49 Erik Blaufuss
lbnecmd check
151 1 John Freeman
</pre>
152 62 John Freeman
For example, before issuing the "start" transition, you can use this command to ensure that the DAQ is in the "ready" state and not still in the "initializing" stage.
153 1 John Freeman
154 49 Erik Blaufuss
First, take DAQInterface from the "stopped" to the "ready" state; this will create the artdaq processes on the hosts you selected (DAQ components), and initialize them with the FHiCL configuration:
155 1 John Freeman
<pre>
156 1 John Freeman
lbnecmd init daq
157 1 John Freeman
</pre>
158 1 John Freeman
159 49 Erik Blaufuss
Take DAQInterface from the "ready" to the "running" state, in order to begin taking data:
160 29 John Freeman
<pre>
161 1 John Freeman
lbnecmd start daq
162 29 John Freeman
</pre>
163 49 Erik Blaufuss
Note: the current run number is displayed when DAQ is in the running state using the "lbnecmd check" command:
164 49 Erik Blaufuss
<pre>
165 49 Erik Blaufuss
lbnecmd check
166 49 Erik Blaufuss
lbnecontrol: running
167 49 Erik Blaufuss
Run number: 207
168 49 Erik Blaufuss
Run configuration: demo
169 1 John Freeman
170 49 Erik Blaufuss
daqint@localhost:5570 (synchronous): running
171 49 Erik Blaufuss
</pre>
172 49 Erik Blaufuss
173 49 Erik Blaufuss
Pause the running of the DAQ, putting DAQInterface into the "paused" state.  This will cause the current open output file to be closed and given a name reflecting the current run number:
174 22 John Freeman
<pre>
175 21 John Freeman
lbnecmd pause daq
176 42 John Freeman
</pre>
177 41 John Freeman
178 1 John Freeman
Resume the running of the DAQ, putting returning to the "running" state.  This will restart data taking to a new output file:
179 48 John Freeman
<pre>
180 48 John Freeman
lbnecmd resume daq
181 48 John Freeman
</pre>
182 48 John Freeman
183 48 John Freeman
Halt the running of the DAQ, returning DAQInterface to the "ready" state from the "running" state:
184 48 John Freeman
<pre>
185 48 John Freeman
lbnecmd stop daq
186 49 Erik Blaufuss
</pre>
187 49 Erik Blaufuss
From the ready state, you can start a new run with the same configuration and DAQ components you originally selected. 
188 62 John Freeman
*NOTE* To select a new configuration or DAQ component set, you must kill all ArtDAQ processes and return DAQInterface to its "stopped" state with the "terminate" command:
189 1 John Freeman
190 1 John Freeman
<pre>
191 1 John Freeman
lbnecmd terminate daq
192 1 John Freeman
</pre>
193 1 John Freeman
194 49 Erik Blaufuss
h2. After your DAQ run.
195 1 John Freeman
196 49 Erik Blaufuss
Once you've completed your run, there are a few things you can look at. 
197 48 John Freeman
198 49 Erik Blaufuss
* A record of the DAQ's output will be saved in the subdirectory pmt/ relative to where you specified the output logfiles; thus in the example config.txt below, you'd find the output in /data/lbnedaq/daqlogs/pmt/. 
199 51 John Freeman
* Also, a record of the FHiCL documents sent to the artdaq processes and the docs/config.txt file will have been saved; as of this writing (11/12/14) the directory in which this can be found defaults to /data/lbnedaq/scratch/jcfree/TemporarySaveArea/<run number>, although as you might imagine the plan is to eventually change this directory. 
200 51 John Freeman
** PLEASE NOTE that there may be slight differences between the saved FHiCL documents and the FHiCL documents specified in config.txt and/or provided by the choice of configuration. The saved FHiCL document name is standardized to <processtype>_<host>_<port>_r<run number>.fcl, so, e.g, "Aggregator_lbnedaq2_5266_r192.fcl" would be the saved name of /data/lbnedaq/fcl/Aggregator_lbnedaq2_2.fcl, listed in the example config.txt file above, assuming datataking was performed in run 192. 
201 49 Erik Blaufuss
** More importantly, the FHiCL document actually sent to the artdaq process may be slightly different than the FHiCL document provided for DAQInterface; this is because DAQInterface performs some bookkeeping on FHiCL variables which account for things such as the number of processes of a given type (note that it makes no changes which would affect the physics). It is this post-bookkeeping FHiCL document which actually gets sent to the processes which gets saved to the output directory. 
202 52 John Freeman
* Output of the Art modules. Various Art modules may create various types of output. In particular, it's standard for one of the two AggregatorMains running in an artdaq-based DAQ to use Art's RootOutput module, which will save the assembled raw event in an Art-readable *.root file. The location of this output can be found in the FHiCL code used to control RootOutput. The other AggregatorMain typically will run other RootOutput modules designed to create plots, diagnostic printouts, etc.; the nature of the output here is too varied to neatly summarize, but checking the FHiCL code used to control these Art modules should reveal their output location.
203 1 John Freeman
204 49 Erik Blaufuss
h1. Configuring DAQInterface
205 49 Erik Blaufuss
206 52 John Freeman
DAQInterface has some key information stored in a local configuration file (location and ports for EventBuilders, Aggregators, location of artDAQ, log level, etc). These can be changed while DAQInterface is not running,  It's expected that for normal operations, these should not need to changed too often. Assuming the processes aren't running, before getting started, take a look at the configuration file, found in docs/config.txt (relative to /data/lbnedaq/scratch/DAQInterface/lbnerc). 
207 49 Erik Blaufuss
It should look something like the following:
208 1 John Freeman
<pre>
209 49 Erik Blaufuss
lbne-artdaq: /data/lbnedaq/scratch/DAQInterface/build_lbne-artdaq
210 1 John Freeman
211 49 Erik Blaufuss
PMT host: lbnedaq3
212 49 Erik Blaufuss
213 49 Erik Blaufuss
pause before initialization: 5
214 49 Erik Blaufuss
215 49 Erik Blaufuss
# debug level can range from 0 to 3 (increasing order of verbosity)
216 49 Erik Blaufuss
debug level: 1
217 49 Erik Blaufuss
218 49 Erik Blaufuss
log directory:   /data/lbnedaq/daqlogs
219 49 Erik Blaufuss
220 49 Erik Blaufuss
record directory: /data/lbnedaq/scratch/jcfree/TemporarySaveArea/
221 49 Erik Blaufuss
222 1 John Freeman
 EventBuilder host: lbnedaq2
223 48 John Freeman
 EventBuilder port: 5235
224 48 John Freeman
 EventBuilder fhicl: /data/lbnedaq/fcl/EventBuilder_demo1.fcl
225 48 John Freeman
226 48 John Freeman
 EventBuilder host: lbnedaq2
227 48 John Freeman
 EventBuilder port: 5236
228 48 John Freeman
 EventBuilder fhicl: /data/lbnedaq/fcl/EventBuilder_demo2.fcl
229 48 John Freeman
230 48 John Freeman
 Aggregator host: lbnedaq2
231 48 John Freeman
 Aggregator port: 5265
232 41 John Freeman
233 1 John Freeman
 Aggregator host: lbnedaq2
234 21 John Freeman
 Aggregator port: 5266
235 49 Erik Blaufuss
</pre>
236 1 John Freeman
237 49 Erik Blaufuss
The "lbne-artdaq" parameter allows the user to set the directory in which the desired build of lbne-artdaq to use is located, the "PMT host" parameter is the host on which artdaq's process management tool script (pmt.rb, used by DAQInterface to launch and kill the artdaq processes) will run, and "log directory" is the directory to which lbne-artdaq's output will be sent. The "debug level" parameter allows the user to set the verbosity level of the output to the screen; setting it to higher values creates greater verbosity, and as a practical matter, the range of settings is currently 0-3. Loosely speaking, "0" means minimal output (not much beyond simply announcing a transition is complete), "1" includes announcements of progress during transitions, "2" includes these announcements plus the values of certain variables as well as lbne-artdaq output, and "3" is primarily of developer interest. The "pause before initialization" parameter allows the user to set a pause, in seconds, between when the artdaq processes start and when they're initialized; it has been observed that a latency of a few seconds is needed for initialization to proceed correctly (though this is not always the case -- on lbne35t-gateway01, with a high setting for "debug level", a pause is not needed; the reason why "debug level" matters in this context is not yet understood).
238 49 Erik Blaufuss
239 53 John Freeman
After these individual parameters, one defines the EventBuilderMain and AggregatorMain artdaq processes. Specifically, an EventBuilderMain is defined in three lines, where each line should contain "EventBuilder", and define the host and port on which the EventBuilderMain will run (to run an artdaq process on the same host as you're on, use "localhost") as well as the FHiCL document used to initialize the EventBuilderMain. AggregatorMain is defined similarly, using the token "Aggregator", but without the FHiCL document supplied, as this is supplied by the choice of configuration in the configuration manager. Best practice is to place the EventBuilderMain's FHiCL documents in the /data/lbnedaq/fcl directory. Please note that the order of processes matters, and that they should be listed front-end to back-end, i.e., EventBuilders should appear before Aggregators.
240 49 Erik Blaufuss
241 57 John Freeman
h1. Adding new configurations to RunControl
242 57 John Freeman
243 57 John Freeman
Adding a new configuration selectable from RunControl is quite simple. As of 11/20/14, the FHiCL documents associated with a given configuration are stored within the directory
244 57 John Freeman
<pre>
245 57 John Freeman
/data/lbnedaq/config/<named_configuration>
246 57 John Freeman
</pre>
247 57 John Freeman
where "named_configuration" would be the name of the configuration, in this example. Within this directory, the following files are expected:
248 57 John Freeman
* Aggregator1.fcl and Aggregator2.fcl, used to initialize the two AggregatorMain processes in the DAQ system
249 57 John Freeman
* <named_component>_hw_cfg.fcl, used to initialize the BoardReaderMain process running the fragment generator associated with detector component "named_component". Note that there can be any number of such files associated with a configuration, as long as a given component is registered to RunControl (see below, "Adding new DAQ Components to RunControl")
250 57 John Freeman
251 59 John Freeman
There are existing examples of configurations currently within /data/lbnedaq/config which can be studied (and even copied) for further guidance; however, please disregard the "tmp1" and "tmp2" configurations. Note that the FHiCL documents in these directories contain some variables which are set to "PLACEHOLDER", e.g.
252 59 John Freeman
<pre>
253 59 John Freeman
 event_builder_count: PLACEHOLDER
254 59 John Freeman
</pre>
255 59 John Freeman
Note that this is not legal FHiCL, but that DAQInterface will substitute in the appropriate value before using the FHiCL document to initialize an artdaq process; here, for example, it would replace "PLACEHOLDER" with the actual number of EventBuilderMain processes being run. 
256 57 John Freeman
257 57 John Freeman
258 56 Erik Blaufuss
h1. Adding new DAQ Components to RunControl
259 49 Erik Blaufuss
260 49 Erik Blaufuss
The list of available DAQComponents (maps to BoardReader processes) is maintained by RunControl in the file:
261 49 Erik Blaufuss
<pre>
262 49 Erik Blaufuss
/home/lbnedaq/.lbnerc-components
263 18 John Freeman
</pre>
264 55 Erik Blaufuss
Each entry (name: host port) defines:
265 55 Erik Blaufuss
* name - name of the component, maps to a <name>_hw_cfg.fcl in CfgMgr's configuration directory
266 49 Erik Blaufuss
* host - hostname where BoardReader process will be started
267 49 Erik Blaufuss
* port - XMLRPC port to be used, must be unique and used by other processes.
268 18 John Freeman
269 49 Erik Blaufuss
For example:
270 49 Erik Blaufuss
<pre>
271 49 Erik Blaufuss
component01: lbnedaq2 5205
272 49 Erik Blaufuss
component02: lbnedaq2 5206
273 49 Erik Blaufuss
</pre>
274 49 Erik Blaufuss
Has two components (component01 and component02) both running on lbnedaq2 on ports 5205 and 5206.
275 27 John Freeman
276 49 Erik Blaufuss
h1.  Troubleshooting and FAQ
277 28 John Freeman
278 49 Erik Blaufuss
h2.  Common RunControl issues
279 27 John Freeman
280 49 Erik Blaufuss
h3. How can I get a list of all RunControl commands?
281 1 John Freeman
282 49 Erik Blaufuss
<pre>
283 49 Erik Blaufuss
lbnecmd help
284 49 Erik Blaufuss
</pre>
285 50 Erik Blaufuss
will list all available commands for RunControl with some details for help.  
286 50 Erik Blaufuss
 
287 50 Erik Blaufuss
h3.  No real configurations are listed by RunControl
288 45 John Freeman
289 49 Erik Blaufuss
If you run "lbnecmd listconfigs" and see something like:
290 45 John Freeman
<pre>
291 49 Erik Blaufuss
Available configs (Name : description)
292 49 Erik Blaufuss
293 49 Erik Blaufuss
dummy : Dummy description
294 45 John Freeman
</pre>
295 49 Erik Blaufuss
Instead of your expected configurations, RunControl is not able to connect to CfgMgr.  Please make sure it's running (https://cdcvs.fnal.gov/redmine/projects/fhicl_cfgmgr/wiki/Wiki)
296 1 John Freeman
297 49 Erik Blaufuss
h2.  Common DAQInterface issues
298 49 Erik Blaufuss
299 49 Erik Blaufuss
h3.  *Error handling*
300 49 Erik Blaufuss
301 49 Erik Blaufuss
As of this writing (11/14/14) certain potential problems have been anticipated and are handled within DAQInterface. These problems include:
302 49 Erik Blaufuss
# An artdaq process returns an error state after a transition request, or an exception is thrown by the XML-RPC library during the request
303 49 Erik Blaufuss
# During periodic checks, one or more artdaq processes expected to exist are not found
304 49 Erik Blaufuss
305 49 Erik Blaufuss
In either case, an error is reported via 0MQ to RunControl, and the "Recover" transition is automatically triggered. This transition is a fairly blunt instrument: it will kill any remaining artdaq processes and return DAQInterface to its original state of "stopped" (i.e., one in which it requires the "init" transition before anything else is done). 
306 49 Erik Blaufuss
307 49 Erik Blaufuss
h3. *Your change to docs/config.txt or daqinterface.py doesn't seem to do anything*
308 49 Erik Blaufuss
309 1 John Freeman
Make sure you kill the existing daqinterface process and restart it
310 49 Erik Blaufuss
311 54 John Freeman
h3. *On the initial transition ("lbnecmd init daq"), you see "error: [Errno 111] Connection refused"*
312 49 Erik Blaufuss
313 1 John Freeman
If a "Recover" is triggered and you can see via "lbnecmd check" that DAQInterface is in the "stopped" state, try initializing again. If that doesn't work, you can try increasing the value of the "pause before initialization" variable in the docs/config.txt file. Empirically, it appears there needs to be a pause of at least 4 seconds on lbnedaqtest01.fnal.gov before the FHiCL documents can be successfully sent via XML-RPC to the processes; increasing this value may make it less likely that the "Connection refused" error occurs.
314 54 John Freeman
315 49 Erik Blaufuss
h3. *On the initial transition, you see a regularly updating printout saying "Waiting for all processes to be launched"*
316 49 Erik Blaufuss
317 1 John Freeman
Seeing one or two of these is fine. If, after several seconds, something like the following
318 1 John Freeman
<pre>
319 1 John Freeman
Waiting for all processes to be launched; if zombie pmt.rb is running on localhost please kill it and this program (PID 31820)
320 1 John Freeman
</pre>
321 1 John Freeman
keeps getting output to screen, it means there's a problem initializing. In this case, the current (11/12/14) course of action is to externally kill DAQInterface using the PID listed; also, it's possible that there may already be a pmt.rb executable running on the desired host, blocking the launch of a new one due to a port conflict, in which case you should log onto the host (assuming you're not already on it), and run 
322 1 John Freeman
<pre>
323 1 John Freeman
ps aux | grep -v grep | grep pmt.rb 
324 1 John Freeman
</pre>
325 51 John Freeman
to see if this is the case. If it's not and you can't think of what might be wrong (is the configuration manager running? have you double-checked docs/config.txt?), then try increasing the debug level in docs/config.txt for your next run-through, as this will likely shed light on the nature of the problem.