Experimental Physics and
Industrial Control System

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	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
<== Date ==>		<== Thread ==>

Subject:	RE: CAS-client thread issues in areaDetector IOC
From:	Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
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>
Date:	Mon, 27 Jan 2020 16:32:06 +0000

Hi Jakub,

Is this error consistent or intermittent?

I have an Ubuntu 18.04 system running 7.0.3.1 and simDetector works fine for me.

Mark

From: Wlodek, Jakub <jwlodek at bnl.gov>
Sent: Monday, January 27, 2020 9:46 AM
To: Michael Davidsaver <mdavidsaver at gmail.com>
Cc: Mark Rivers <rivers at cars.uchicago.edu>; tech-talk at aps.anl.gov
Subject: Re: CAS-client thread issues in areaDetector IOC

Hi all,

I swapped the R7.0.3 for R7.0.3.1, and rebuilt, and the error reappeared (the path still has R7-0-3 since I swapped it in place to ensure using the same sources for modules/drivers):

epicsEventTrigger: pthread_mutex_unlock failed: Invalid argument

epicsEventMustTriggerThread CAS-client (0x7f3144042b40) can't proceed, suspending.

Dumping a stack trace of thread 'CAS-client':

[ 0x556aabd70b73]: /epics/src-7-0-3/support/areaDetector/ADUVC/iocs/adUVCIOC/bin/linux-x86_64/adUVCApp(epicsStackTrace+0x73)

[ 0x556aabd615a5]: /epics/src-7-0-3/support/areaDetector/ADUVC/iocs/adUVCIOC/bin/linux-x86_64/adUVCApp(cantProceed+0xc5)

[ 0x556aabcea793]: /epics/src-7-0-3/support/areaDetector/ADUVC/iocs/adUVCIOC/bin/linux-x86_64/adUVCApp(db_close_events+0x33)

[ 0x556aabd120bf]: /epics/src-7-0-3/support/areaDetector/ADUVC/iocs/adUVCIOC/bin/linux-x86_64/adUVCApp(destroy_tcp_client+0x8f)

[ 0x556aabd12cdd]: /epics/src-7-0-3/support/areaDetector/ADUVC/iocs/adUVCIOC/bin/linux-x86_64/adUVCApp(camsgtask+0x13d)

[ 0x556aabd6bfa8]: /epics/src-7-0-3/support/areaDetector/ADUVC/iocs/adUVCIOC/bin/linux-x86_64/adUVCApp(start_routine+0xf8)

[ 0x7f325539c6db]: /lib/x86_64-linux-gnu/libpthread.so.0(start_thread+0xdb)

[ 0x7f325413188f]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)

Thread CAS-client (0x7f3144042b40) suspended

However, I copied these sources onto a different machine and recompiled and I couldn't reproduce the error (The first machine is ubuntu 18.04, the second is debian 9),

so I'm guessing this issue is most likely tied to something on my local machine. Below are the non 'ok' tests from make runtests for base R7.0.3.1 on the ubuntu machine:

dbServerTest.t ............. 1/25 dbRegisterServer: Can't redefine 'one'.

dbRegisterServer: Bad server name 'bad name'

dbRegisterServer: Ignoring 'disabled', per environment

dbUnregisterServer: Servers still active!

dbUnregisterServer: 'toolate' not registered.

dbUnregisterServer: 'no-routines' has no stop() method.

In addition, the following tests showed some error message, but were seemingly re-run successfully:

iocshTest.t ................... 1/19 Command no_such_command not found.

iocsh Error: Break

Can't open no_such_file.cmd: No such file or directory

iocshTest.t ................... ok

chfPluginTest.t ............ 1/1433 chfConfigParseStart: plugin pvt alloc failed
chfPluginTest.t ............ ok

netget.t ................ 1/3 **** The executable "caRepeater" couldn't be located

**** because of errno = "No such file or directory".

**** You may need to modify your PATH environment variable.

**** Unable to start "CA Repeater" process.

netget.t ................ ok

There were also several tests that listed json parsing errors.

Regards,

Jakub

From: Michael Davidsaver <mdavidsaver at gmail.com>
Sent: Friday, January 24, 2020 4:52 PM
To: Wlodek, Jakub <jwlodek at bnl.gov>
Cc: Mark Rivers <rivers at cars.uchicago.edu>; tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: CAS-client thread issues in areaDetector IOC

On 1/24/20 10:15 AM, Mark Rivers wrote:
> Ø Could it be that there is a problem with something in the newest release of epics-base?
...
> You are running 7.0.3 now. If you go back to 7.0.3.1 does the problem re-appear?

If the assert() failure does re-appear, could you run the base unittests and report any which don't pass?

> make runtests

References:: CAS-client thread issues in areaDetector IOC Wlodek, Jakub via Tech-talk; RE: CAS-client thread issues in areaDetector IOC Mark Rivers via Tech-talk; Re: CAS-client thread issues in areaDetector IOC Wlodek, Jakub via Tech-talk; Re: CAS-client thread issues in areaDetector IOC Michael Davidsaver via Tech-talk; Re: CAS-client thread issues in areaDetector IOC Wlodek, Jakub via Tech-talk; RE: CAS-client thread issues in areaDetector IOC Mark Rivers via Tech-talk; Re: CAS-client thread issues in areaDetector IOC Michael Davidsaver via Tech-talk; Re: CAS-client thread issues in areaDetector IOC Wlodek, Jakub via Tech-talk

Navigate by Date:: Prev: Re: CAS-client thread issues in areaDetector IOC Wlodek, Jakub via Tech-talk; Next: Re: XSPRESS3 hdf5 problems John Dobbins via Tech-talk; 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
Navigate by Thread:: Prev: Re: CAS-client thread issues in areaDetector IOC Wlodek, Jakub via Tech-talk; Next: Re: CAS-client thread issues in areaDetector IOC Michael Davidsaver via Tech-talk; 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

ANJ, 27 Jan 2020

· Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System