Chris, can you give us help with apparent problems we are having with
StripTool?
>From a message I got from a colleague of mine (Delphy Nypaver):
"I ran a test this morning and it appears that it is the StripTool that is
causing the memory problem. Every time I run it I get those errors on the
ioc. My theory is that the reason rebooting the Sun caused the problem to
go away is because it killed the StripTool program when it rebooted."
>From a previous message Delphy sent documenting the error messages she gets:
"Attached are the intermittent memory errors we are getting on the ioc. I
would think some of your contacts in the EPICS community would be able to
tell us what these mean, if not what's causing them."
iocA~> 0x1fa2d4 (CA TCP): memPartAlloc: block too big - 11412 in partition
0xafae8.
0x1fa2d4 (CA TCP): CAS: task creation for new client failed because
"S_memLib_NOT_ENOUGH_MEMORY"
0xf0cc4 (CA client): memPartAlloc: block too big - 25072 in partition
0xafae8.
0xf0cc4 (CA client): CAS: unable to init the event facility
iocA~> 0x1fa2d4 (CA TCP): memPartAlloc: block too big - 11412 in partition
0xafae8.
0x1fa2d4 (CA TCP): CAS: task creation for new client failed because
"S_memLib_NOT_ENOUGH_MEMORY"
iocA~> 0xf0cc4 (CA client): memPartAlloc: block too big - 25072 in
partition 0xafae8.
0xf0cc4 (CA client): CAS: unable to init the event facility
0xf0cc4 (CA client): memPartAlloc: block too big - 25072 in partition
0xafae8.
0xf0cc4 (CA client): CAS: unable to init the event facility
0xf0cc4 (CA client): memPartAlloc: block too big - 25072 in partition
0xafae8.
0xf0cc4 (CA client): CAS: unable to init the event facility
iocA~>
iocA~>
iocA~> 0x1fa2d4 (CA TCP): memPartAlloc: block too big - 11412 in partition
0xafae8.
0x1fa2d4 (CA TCP): CAS: task creation for new client failed because
"S_memLib_NOT_ENOUGH_MEMORY"
0xf2bd0 (CA client): memPartAlloc: block too big - 25072 in partition
0xafae8.
0xf2bd0 (CA client): CAS: unable to init the event facility
Have we possibly overlooked something in how we use StripTool?
Again, from one of Delphy's messages:
"There didn't seem to be a relation with the alarm handler, but I'll keep
checking. Error messages also print on the Sun about invalid channels that
aren't invalid unless the StripTool is running."
Any help here with understanding better how channel access works will also
be appreciated.
Regards,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
John K. Munro, Jr., PhD Voice: (423) 574-0635
Development Staff Pager: (423) 417-6585
Instrumentation and Controls Division FAX: (423) 576-8380
Oak Ridge National Laboratory Email: [email protected]
Bldg. 3500, MS 6010, PO Box 2008
Bethel Valley Road
Oak Ridge, TN 37831-6010
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Replies:
- RE: IOC Errors when StripTool is Running Jeff Hill
- Navigate by Date:
- Prev:
Access Fault Dennis M. Reichhold
- Next:
Fwd: alh correction John K Munro Jr
- 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:
RE: Access Fault Jeff Hill
- Next:
RE: IOC Errors when StripTool is Running Jeff Hill
- 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
|