Bad frame number when 'atop' process runs
I open a new issue here on the Lima-camera-eiger plugin to track the problem from ID11. This was previously tracked in https://requests.esrf.fr/plugins/servlet/desk/portal/1/SCHLP-15329
The off-by-one frame number shows up when the atop logging process runs (at higher priority) and this causes the scan to block. We saw many examples in lid11eiger2lima:/var/log/EigerMem.log, usually the errors shows up at multiples of 10 minutes.
This problem should be suppressed by stopping the atop process for now. In the longer term, I am afraid there is an underlying problem that will surface again when the machine sees an increased load.
[2022/05/26 12:40:04.516360] 7f92cd2d1700 *Camera*Eiger::Stream::_ZmqThread::_read_zmq_messages (/bliss/users/blissadm/local/lima.git/camera/eiger/src/EigerStream.cpp:400)-Error: Exception(Error): Bad frame number: 760, expected 759 [thrown]
[2022/05/26 12:40:04.516719] 7f92cd2d1700 *Camera*Eiger::Stream::_ZmqThread::_run_sequence (/bliss/users/blissadm/local/lima.git/camera/eiger/src/EigerStream.cpp:337)-Error: *event=<Event: Severity=Error, Domain=Camera, Code=CamFault: Stream error: Hardware: _read_zmq_messages(/bliss/users/blissadm/local/lima.git/camera/eiger/src/EigerStream.cpp, 400): Error: Bad frame number: 760, expected 759>
[2022/05/26 12:40:04.516742] 7f92cd2d1700 *Control*Control::Event::reportEvent (/bliss/users/blissadm/local/lima.git/control/src/CtEvent.cpp:133)-Error: *event=<Event [5.78013]: Severity=Error, Domain=Camera, Code=CamFault: Stream error: Hardware: _read_zmq_messages(/bliss/users/blissadm/local/lima.git/camera/eiger/src/EigerStream.cpp, 400): Error: Bad frame number: 760, expected 759>