Ralph Lange wrote:
>
> Dear Gurus,
>
> since Friday we're observing an unpleasant behaviour on one of our
> IOCs:
> Occasionally (approx. every 20 to 30 minutes at normal load) the
> scanOnce task gets suspended due to an Access Fault. After a couple of
> seconds, the dbCaLink task follows after writing "rngBufPut overflow in
> scanOnce" to the log. After that there is no more ca based record
> processing, i.e. no more ca links and operator access.
Request are made to scanOnce by putting a request into a ring buffer.
thus when scanOnce crashes the ring buffer ultimately fills up. This is
what
you are seeing.
Note that NO epics tasks are automatically restarted when they crash.
Sounds nice but can cause more problems than it solves.
> So - who the hell is calling scanOnce() with a junk record pointer
> (this is the way we think dbScanLock gets called)?
Good question. Answer should solve problem!!
> We inserted a patch in scanOnce to check the precord argument for
> validity and start a tt() to see which task is the bad guy here. Another
> advantage of that patch is that we won't process the record and therefore
> extend the IOC's uptime.
So what did you find?
If you get a stack trace of crashed scanOnce task it should help.
Marty
- Replies:
- Re: IOC hangs (scanOnce crashes) Ralph Lange
- References:
- IOC hangs (scanOnce crashes) Ralph Lange
- Navigate by Date:
- Prev:
IOC hangs (scanOnce crashes) Ralph Lange
- Next:
Re: IOC hangs (scanOnce crashes) Ralph Lange
- 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:
IOC hangs (scanOnce crashes) Ralph Lange
- Next:
Re: IOC hangs (scanOnce crashes) Ralph Lange
- 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
|