|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
23 Jun 2023, Gennaro Tortone, Bug Report, deferred stop transition
|
23 Jun 2023, Stefan Ritt, Bug Report, deferred stop transition
|
23 Jun 2023, Gennaro Tortone, Bug Report, deferred stop transition
|
23 Jun 2023, Stefan Ritt, Bug Report, deferred stop transition
|
26 Jun 2023, Gennaro Tortone, Bug Report, deferred stop transition
|
26 Jun 2023, Stefan Ritt, Bug Report, deferred stop transition
|
|
Message ID: 2544
Entry time: 23 Jun 2023
Reply to this: 2545
|
Author: |
Gennaro Tortone |
Topic: |
Bug Report |
Subject: |
deferred stop transition |
|
|
Hi,
I'm facing some issues with 'stop' deferred transition and I suspect of
a MIDAS bug regarding this...
to reproduce the issue I use the 'deferredfe' MIDAS example (develop branch),
changing only the equipment name from 'Deferred' to 'Deferred%02d' in order
to be able to run multiple 'deferredfe' instances;
I run *three* 'deferredfe' frontends using:
./deferredfe -i 0
./deferredfe -i 2
./deferredfe -i 3
Everything goes fine on MIDAS web page and 'deferredfe' frontends are initialized
and ready to run; issues occour after 'start' when I stop the frontends: sometimes
at first shot and sometimes at next 'start'/'stop' the deferred 'stop' transition
seems to be handled in wrong way... and often one frontend goes in 'segmentation fault'
The odd thing is when I run *two* instances: in this case no issues are reported...
Thanks in advance,
Gennaro |