1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: CAS-client thread issues in areaDetector IOC |
From: | "Wlodek, Jakub via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Mark Rivers <rivers at cars.uchicago.edu>, Michael Davidsaver <mdavidsaver at gmail.com> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Wed, 29 Jan 2020 20:13:13 +0000 |
Hi all,
After testing on another Ubuntu 18 machine, I couldn't reproduce the issue. It seems that it is limited to my original specific machine. I will try updating all of the packages on it,
recompiling, and then I will use a python script to test, as suggested.
If I find the cause of the issue I will further update this thread.
Thanks,
Jakub
From: Mark Rivers <rivers at cars.uchicago.edu>
Sent: Monday, January 27, 2020 1:57 PM To: Wlodek, Jakub <jwlodek at bnl.gov>; Michael Davidsaver <mdavidsaver at gmail.com> Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov> Subject: RE: CAS-client thread issues in areaDetector IOC I suggest using the simDetector and a Python script for testing. Start the simDetector with no plugins enabled, and have Python just press start and stop in a loop. If that does not fail then enable plugins one at a time until you find a minimal configuration is that will generate the error. Then others can try to reproduce.
I just did a lot of clicking on the simDetector with Ubuntu 18.04 and base 7.0.3.1 and cannot make it fail.
Mark
From: Wlodek, Jakub <jwlodek at bnl.gov>
Hi Mark
I observe it every time I start an IOC, but not immediately after startup, it shows up after some time with normal operation (acquire start/stop, enable/disable plugins etc.) I can't seem to nail down a specific series of steps that leads to the error, but it seems consistent. I also re cloned and rebuilt everything again from scratch in a different location to make sure something wasn't messed up in that specific set of sources, and I saw the same issue.
Regards, Jakub From: Michael Davidsaver <mdavidsaver at gmail.com>
On 1/27/20 7:45 AM, Wlodek, Jakub wrote: |