I remember I saw this kind of problem a few years ago. I did a search of "EVENTQEMPTY" on my computer. Yes, there was an email sent by one of my colleagues reporting that incident:
A call to 'assert(ev_que->evque[ev_que->putix] == EVENTQEMPTY)'
by thread 'CAS-client' failed in ../dbEvent.c line 701.
EPICS Release EPICS R3.14.12.3-6 $Date: Mon 2012-12-17 14:11:47 -0600$.
Local time is 2019-05-29 00:29:45.524700357 EDT
Please E-mail this message to the author or to tech-talk at aps.anl.gov
Calling epicsThreadSuspendSelf()
Thread CAS-client (0x88c1530) suspended
scanOnce: Ring buffer overflow
On 5/19/21, 4:04 PM, "Core-talk on behalf of mdavidsaver via Core-talk" <core-talk-bounces at aps.anl.gov on behalf of core-talk at aps.anl.gov> wrote:
And again https://epics.anl.gov/tech-talk/2021/msg01039.php
--
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://urldefense.com/v3/__https://bugs.launchpad.net/bugs/541371__;!!P4SdNyxKAPE!UtSLJkcvDf_6zGahOmcA3EUN2RRWWzHVbu-ZWaCiTrbnXbjiWA23NqYHBONC$
Title:
assert (ev_que->evque[ev_que->putix] == EVENTQEMPTY) failed in
dbEvent.c
Status in EPICS Base:
Incomplete
Bug description:
2009-06-04 10:00 iocsrvid2>
CAS-client: A call to "assert (ev_que->evque[ev_que->putix] == EVENTQEMPTY)" failed in ../dbEvent.c at 683 Current time THU JUN 04 2009 10:08:33.581404952.
EPICS Release EPICS R3.14.10-asd1 $R3-14-10$ $2008/10/27 19:39:04$.
Please E-mail this message and the output from "tt (0x13144d0)"
to the author or to tech-talk at aps.anl.gov Thread CAS-client (0x13144d0) suspended
causing all the network buffers to get used up and all network-related
activities to die, e.g:
callbackRequest: cbHigh ring buffer full
NTPTimeSync: NTP requests failing - S_sntpcLib_TIMEOUT DB CA Link Exception: "Virtual circuit unresponsive", context "164.54.2.121:5064"
save_restore:do_seq - '/iocinfo/saverestore/iocsrvid2/ srvid2AutosaveV3.sav' not found. Writing a new one. [090604-101331]
../online_notify.c: CA beacon (send to "164.54.3.255:5065") error was "S_errno_ENOBUFS"
iocsrvid2> tt 0x13144d0
133288 vxTaskEntry +68 : 19290c0 ()
1929118 epicsThreadOnceOsd+168: camsgtask ()
1864ab4 camsgtask +260: camessage ()
1868ba8 camessage +2f0: 1867bb8 ()
1867e3c rsrvFreePutNotify+880: db_post_single_event () 188629c db_post_single_event+38 : 1885f84 () 1886080 db_post_extra_labor+194: epicsAssert ()
1928234 epicsAssert +f8 : epicsThreadSuspendSelf ()
1929274 epicsThreadSuspendSelf+14 : taskSuspend () value = 0 = 0x0
This is a PowerPC running vxWorks 5.5.2 and Base R3.14.10. The IOC
had to be rebooted. This is the second or third time we've seen
ENOBUFS recently, although the engineers didn't see (look for)
assertion failure before this.
Original Mantis Bug: mantis-342
http://www.aps.anl.gov/epics/mantis/view_bug_page.php?f_id=342
To manage notifications about this bug go to:
https://urldefense.com/v3/__https://bugs.launchpad.net/epics-base/*bug/541371/*subscriptions__;Kys!!P4SdNyxKAPE!UtSLJkcvDf_6zGahOmcA3EUN2RRWWzHVbu-ZWaCiTrbnXbjiWA23Nn2NWQXw$
- References:
- [Bug 541371] Re: assert (ev_que->evque[ev_que->putix] == EVENTQEMPTY) failed in dbEvent.c mdavidsaver via Core-talk
- Navigate by Date:
- Prev:
[Bug 541371] Re: assert (ev_que->evque[ev_que->putix] == EVENTQEMPTY) failed in dbEvent.c mdavidsaver via Core-talk
- Next:
Build failed in Jenkins: EPICS-3.14 #1047 Jenkins EPICS PSI via Core-talk
- Index:
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:
[Bug 541371] Re: assert (ev_que->evque[ev_que->putix] == EVENTQEMPTY) failed in dbEvent.c mdavidsaver via Core-talk
- Next:
[Bug 541371] Re: assert (ev_que->evque[ev_que->putix] == EVENTQEMPTY) failed in dbEvent.c mdavidsaver via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
|