Is this Linux or some other OS?
It looks like you will need to kill the IOC process.
Mark
From: Tagger, Jueri <jtagger at bnl.gov>
Sent: Wednesday, May 19, 2021 11:15 AM
To: Mark Rivers <rivers at cars.uchicago.edu>
Cc: tech-talk at aps.anl.gov
Subject: RE: EPICS stopped
No effect from ^C whatsoever. Typed
epicsMutexShowAll 1
3 times to blank screen – no response
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
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=