On Thu, 18 Nov 1999, Jeff Hill wrote:
> I must admit that we recently saw a very similar situation
> here in one of our systems, and we are still attempting to track
> it down.
>
> We are currently attempting to isolate between:
> o the CA server code
> o the DB CA link code
>
> I have been looking carefully at the CA server and I don't see it. Bob
> has also been looking at the DB CA link code.
>
> > I reset one of the link fields in the record doing the monitoring (it was
> > a Calcout record and had many CA input links from more than one other
> > machine) by writing the the current value of the link to it. This seemed
> > to free things up and all the CA monitored values in that record got set
> > to the current values.
>
> If you poked, on the server side, the input that had a different value than
> what was expected on the client side then it could be either CA or the DB
> CA link code. If you poked, on the server side, some other input whose
> state was properly reflected on the client side and things got better then
> I would expect the DB CA link code (or possibly the CA client library) is
> at fault.
I did the following:
1. I poked a new PV value on the server side and it didn't appear on the
client side.
2. On the client side I changed the input link back to itself.
Specifically, I did:
-> dbpf "mcu:fcalc.INPE","ws:trus_leg_ene:val.VAL NPP NMS"
This had the effect of somehow clearing up all the input links in the
record - none of them had been updating before, and all of them
suddenly updated to current values. Whether they continued to update
properly, I don't know, I didn't have the time to monitor it.
Hence, I decided it had to be either the CA client, or the CA record
support software. Anyway, it was on the client IOC, not the server (dm
screens attached to the server PV's worked fine too).
> > I finally rebooted the IOC to clear everything up.
> >
> what was the functionality that could not be restored without a reboot?
None. It was just that I had isolated the problem to the CA client on a
particular IOC, and so I decided to reboot it in case there were any other
problems - we lost two hours of time to this last night and so I had to be
extra sure that there wasn't any other problems lurking around.
> I will look at this in further detail tomorrow.
Thanks.
Nick Rees
Joint Astronomy Centre Ph: +1 (808) 961-3756
660 N. Aohoku Place Fax: +1 (808) 961-6516
Hilo, HI. 96720 Internet: [email protected]
- References:
- RE: CA LINK's not monitoring. Jeff Hill
- Navigate by Date:
- Prev:
RE: CA LINK's not monitoring. Jeff Hill
- Next:
Re: CA LINK's not monitoring. Bob Dalesio
- 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: CA LINK's not monitoring. Jeff Hill
- Next:
Re: CA LINK's not monitoring. Bob Dalesio
- 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
|