assert(status == epicsMutexLockOK) in dbEvent.c lines 477 & 493

Bug #1762543 reported by Andrew Johnson
This bug report is a duplicate of:  Bug #1730982: Race in db_close_events(). Edit Remove
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
EPICS Base
Triaged
Undecided
mdavidsaver

Bug Description

Oleg Makarov reported:

yesterday EPICS PVs updates stalled on one of our IOCs. IOC reboot solve the problem.
I am posting log messages from IOC console below. EPICS version is 3.15.5.

Should some corrections to the CAS be made, so that erroneous request does not cause suspended threads?

Oleg

CAS: request from 164.54.103.102:38866 => CAS: Missaligned protocol rejected
CAS: Request from 164.54.103.102:38866 => cmmd=29797 cid=0x73000000 type=29793 count=29813 postsiz
e=29267
CAS: Request from 164.54.103.102:38866 => available=0x0 N=2 paddr=0x0
CAS: invalid (damaged?) UDP request from 164.54.103.102:38866 ?
CAS: message received at 2018-03-22 20:18:21

CAS: request from 164.54.103.102:54641 => CAS: Missaligned protocol rejected
CAS: Request from 164.54.103.102:54641 => cmmd=29797 cid=0x73000000 type=29793 count=29813 postsiz
e=29267
CAS: Request from 164.54.103.102:54641 => available=0x0 N=2 paddr=0x0
CAS: invalid (damaged?) UDP request from 164.54.103.102:54641 ?
CAS: message received at 2018-03-31 13:36:44

A call to 'assert(status == epicsMutexLockOK)'
    by thread 'CAS-client' failed in ../../../src/ioc/db/dbEvent.c line 493.
EPICS Release EPICS R3.15.5.
Local time is 2018-04-07 19:59:10.227314800 CST/CDT
Please E-mail this message to the author or to <email address hidden>
Calling epicsThreadSuspendSelf()
Thread CAS-client (0x492c090) suspended

A call to 'assert(status == epicsMutexLockOK)'
    by thread 'CAS-client' failed in ../../../src/ioc/db/dbEvent.c line 477.
EPICS Release EPICS R3.15.5.
Local time is 2018-04-08 08:04:00.242762000 CST/CDT
Please E-mail this message to the author or to <email address hidden>
Calling epicsThreadSuspendSelf()
Thread CAS-client (0x4c573d0) suspended

A call to 'assert(status == epicsMutexLockOK)'
    by thread 'CAS-client' failed in ../../../src/ioc/db/dbEvent.c line 477.
EPICS Release EPICS R3.15.5.
Local time is 2018-04-08 08:06:45.226095334 CST/CDT
Please E-mail this message to the author or to <email address hidden>
Calling epicsThreadSuspendSelf()
Thread CAS-client (0x4b810a0) suspended

A call to 'assert(status == epicsMutexLockOK)'
    by thread 'CAS-client' failed in ../../../src/ioc/db/dbEvent.c line 493.
EPICS Release EPICS R3.15.5.
Local time is 2018-04-08 08:11:10.776095352 CST/CDT
Please E-mail this message to the author or to <email address hidden>
Calling epicsThreadSuspendSelf()
Thread CAS-client (0x4962b00) suspended

A call to 'assert(status == epicsMutexLockOK)'
    by thread 'CAS-client' failed in ../../../src/ioc/db/dbEvent.c line 477.
EPICS Release EPICS R3.15.5.
Local time is 2018-04-08 08:13:56.288060135 CST/CDT
Please E-mail this message to the author or to <email address hidden>
Calling epicsThreadSuspendSelf()
Thread CAS-client (0x4b8bf40) suspended

A call to 'assert(status == epicsMutexLockOK)'
    by thread 'CAS-client' failed in ../../../src/ioc/db/dbEvent.c line 477.
EPICS Release EPICS R3.15.5.
Local time is 2018-04-08 08:17:01.421393463 CST/CDT
Please E-mail this message to the author or to <email address hidden>
Calling epicsThreadSuspendSelf()
Thread CAS-client (0x4bfbbc0) suspended

A call to 'assert(status == epicsMutexLockOK)'
    by thread 'CAS-client' failed in ../../../src/ioc/db/dbEvent.c line 477.
EPICS Release EPICS R3.15.5.
Local time is 2018-04-08 08:19:30.938060149 CST/CDT
Please E-mail this message to the author or to <email address hidden>
Calling epicsThreadSuspendSelf()
Thread CAS-client (0x25d37f0) suspended

A call to 'assert(status == epicsMutexLockOK)'
    by thread 'CAS-client' failed in ../../../src/ioc/db/dbEvent.c line 477.
EPICS Release EPICS R3.15.5.
Local time is 2018-04-08 08:22:36.554726791 CST/CDT
Please E-mail this message to the author or to <email address hidden>
Calling epicsThreadSuspendSelf()
Thread CAS-client (0x4c40d70) suspended

A call to 'assert(status == epicsMutexLockOK)'
    by thread 'CAS-client' failed in ../../../src/ioc/db/dbEvent.c line 477.
EPICS Release EPICS R3.15.5.
Local time is 2018-04-08 08:23:58.421393463 CST/CDT
Please E-mail this message to the author or to <email address hidden>
Calling epicsThreadSuspendSelf()
Thread CAS-client (0x4c4a810) suspended

A call to 'assert(status == epicsMutexLockOK)'
    by thread 'CAS-client' failed in ../../../src/ioc/db/dbEvent.c line 477.
EPICS Release EPICS R3.15.5.
Local time is 2018-04-08 08:28:55.938060149 CST/CDT
Please E-mail this message to the author or to <email address hidden>
Calling epicsThreadSuspendSelf()
Thread CAS-client (0x4c85be0) suspended

A call to 'assert(status == epicsMutexLockOK)'
    by thread 'CAS-client' failed in ../../../src/ioc/db/dbEvent.c line 477.
EPICS Release EPICS R3.15.5.
Local time is 2018-04-08 08:40:05.300141941 CST/CDT
Please E-mail this message to the author or to <email address hidden>
Calling epicsThreadSuspendSelf()
Thread CAS-client (0x4c90690) suspended

23i:ioc2>
23i:ioc2>
23i:ioc2> reboot

Revision history for this message
mdavidsaver (mdavidsaver) wrote :

This seems to me to be related, if not the same as, #1762543

Revision history for this message
mdavidsaver (mdavidsaver) wrote :

oops. copy paste in the wrong tab. Meant to say that lp:1773373 is probably a the issue as this ticket.

Revision history for this message
Andrew Johnson (anj) wrote :

MD: If this is the same as the other please adjust bug status.

Changed in epics-base:
assignee: nobody → mdavidsaver (mdavidsaver)
milestone: none → 3.14.12.8
status: New → Triaged
Revision history for this message
mdavidsaver (mdavidsaver) wrote :

I no longer think these are the same issues. The fix for lp:1773373 is present in Base 3.15.5

Revision history for this message
Ralph Lange (ralph-lange) wrote :
Revision history for this message
mdavidsaver (mdavidsaver) wrote :

Fair point. Then the relevant issue is lp:1730982.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.