Folks,
I learned today that it appears that caRepeater has been crashing on this system. I don't know for sure that this problem happens when caRepeater has died, but that seems likely. The next time it happens we will look to see if caRepeater is still running.
Meanwhile, we have found that there are caRepeater stackdump files, containing the following:
Exception: STATUS_ACCESS_VIOLATION at eip=610B9F69
eax=00000000 ebx=00000001 ecx=00000000 edx=0014C6F0 esi=00000000 edi=011DCCD8
ebp=011DCB14 esp=011DCAEC program=C:\Program Files\EPICS WIN32 Extensions\caRepeater.exe, pid 2152, thread unknown (0xC44)
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
011DCB14 610B9F69 (00000000, 00000000, 00000000, 00000000)
011DCC24 610BA905 (00000000, 00000000, 00000000, 00000000)
011DCCE4 610BB67A (FFFFFFFF, FFFFFFFF, 00000000, 00000000)
011DCD34 61027DE2 (00000002, 011DCE64, 00000002, 011DCE00)
011DCDC8 7C87655C (00000002, 011DCE00, 7C8763C0, 00000002)
End of stack trace
Has anyone else seen such stackdumps from caRepeater? This is the version of caRepeater.exe that is included in the most recent (Nov. 2, 2007) APS "EPICS Win32 Extensions" package.
Thanks,
Mark
________________________________
From: Mark Rivers
Sent: Wed 10/13/2010 11:14 AM
To: tech-talk; 'Jeff Hill'
Cc: Antonio Lanzirotti
Subject: EPICS CA problems
Folks,
We are having trouble with a Windows IOC at NSLS. Here are the symptoms:
- The IOC is running fine
- The PC running the IOC has 2 local CA clients connected to the IOC, medm and IDL. Occassionally (1-2 times per day) one of these clients loses its connection to the IOC. Medm screens go white, IDL says it cannot find a PV, etc. This happens when the client was running fine. It typically only happens to one or the other client, not to both.
- Restarting the client fixes the problem.
- The same 2 clients are running on another PC connected to the same IOC. Those clients are always fine, they do not lose connection when a client on the PC with the IOC does.
- Looking at the resources on the Windows machine (CPU, virtual and physical memory usage) does not indicate any problems.
How do we go about figuring out what is wrong?
Thanks,
Mark
- Replies:
- RE: EPICS CA problems Jeff Hill
- References:
- EPICS CA problems Mark Rivers
- Navigate by Date:
- Prev:
Re: Manipulating time in records Andrew Johnson
- Next:
Re: Epics C# Library - questions Alain Bertrand
- 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: EPICS CA problems Jeff Hill
- Next:
RE: EPICS CA problems 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
|