Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A second cause for this problem can be that the calib-dir is not mounted on the mon-nodes anymore. ami will look for the pedestal files here, so it will take a long time until int times out and will start, but w/o the detectors. You can check if that is the case by looking at an ami log file (e.g. for ami0-0) or ssh to a moomon-node in use and  check check if you can see the pedestals files in /reg/d/psdm/<hutch>/<expname>/calib/<dettype>/.... At this point, please call your on-call ECS person who will escalate it or work around it.If the calib directory is not visible from the mon-nodes, a temporary solution is to use a local version of the calib folder. To do so, copy the calib directory into ~<xxxopr>/tmp_calibdir/<hutch>/<exp>/. This can usually be done from a psana node as <xxxopr>. Then in the <hutch>.cnf file, edit the ami-opts:

Comment the following lines:

if slow_readout_mode != 1:
ami_opts = '-a only -R -L '+plugin_path+'/libtimetooldbd.so -E '+expname
else:
ami_opts = '-a only -L '+plugin_path+'/libtimetooldbd.so -E '+expname

And uncomment:

#ami_opts = '-a only -L '+plugin_path+'/libtimetooldbd.so -E '+expname+' -c /cds/home/opr/xppopr/tmp_calibdir'

Note that this is a temporary solution. Notify the ECS point of contact who will escalate or resolve the calib mount issue.

The DAQ shows "NO CONNECT" in procStat: 

...