EPICS Controls Argonne National Laboratory

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  <20212022  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  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: EPICS stopped
From: "Tagger, Jueri via Tech-talk" <tech-talk at aps.anl.gov>
To: Mark Rivers <rivers at cars.uchicago.edu>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Wed, 19 May 2021 16:15:07 +0000

No effect from ^C whatsoever. Typed epicsMutexShowAll 1

3 times to blank screen – no response

 

 

From: Mark Rivers <rivers at cars.uchicago.edu>
Sent: Wednesday, May 19, 2021 12:12 PM
To: Tagger, Jueri <jtagger at bnl.gov>
Cc: tech-talk at aps.anl.gov
Subject: RE: EPICS stopped

 

Can you type ^C to abort the casr command?  It could be a deadlock.  If that works then type

 

epicsMutexShowAll 1

 

several times and see if the same mutexes are always locked.   That is the symptom of a deadlock.

 

Mark

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Tagger, Jueri via Tech-talk
Sent: Wednesday, May 19, 2021 11:04 AM
To: tech-talk at aps.anl.gov
Subject: EPICS stopped

 

Hi,

We have suddenly situation we can no longer connect to ca channels, (while the existing connections are served)

casr 4

181888 bytes allocated

       Send Lock:

           epicsMutexId 0x7f3978036420 source ../../../src/ioc/rsrv/caservertask.c line 1231

       Put Notify Lock:

           epicsMutexId 0x7f3978036450 source ../../../src/ioc/rsrv/caservertask.c line 1232

       Address Queue Lock:

           epicsMutexId 0x7f3978036480 source ../../../src/ioc/rsrv/caservertask.c line 1233

       Event Queue Lock:

           epicsMutexId 0x7f39780364b0 source ../../../src/ioc/rsrv/caservertask.c line 1234

       Block Semaphore:

           epicsEvent 0x7f3978010c90: full

    pthread_mutex = 0x7f3978010c90, pthread_cond = 0x7f3978010cb8

    TCP client at 10.0.153.12:54302 'box64-3':

       User 'rose', V4.13, Priority = 0, 75 Channels

       Task Id = 0x7f397803c750, Socket FD = 44

       2262.05 secs since last send, 2262.04 secs since last receive

       Unprocessed request bytes = 424, Undelivered response bytes = 0

       State = up

 

Then the output stopped …. no response any more on the console

 

EPICS_BASE=base-3.15.8

 

Any ideas?

 

J. Tagger

NSLS-II=


Replies:
RE: EPICS stopped Mark Rivers via Tech-talk
References:
EPICS stopped Tagger, Jueri via Tech-talk
RE: EPICS stopped Mark Rivers via Tech-talk

Navigate by Date:
Prev: RE: EPICS stopped Mark Rivers via Tech-talk
Next: RE: EPICS stopped Mark Rivers 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  <20212022  2023  2024 
Navigate by Thread:
Prev: RE: EPICS stopped Mark Rivers via Tech-talk
Next: RE: EPICS stopped Mark Rivers 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  <20212022  2023  2024 
ANJ, 19 May 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·