Hi Carl,
> I've seen a similar problem with seq 2.0.2 when the ioc the
> sequencer was running on did not have ca security access to the PV's on the
> other ioc's it needed to connect to. I think it miscounts the disconnects
> when it can't write to the PV's, probably adding a disconnect each time it
> fails. In our situation, just giving write access to the PV's fixed it. It
> looks to me like the sequencer does not implement the client-side api for
> channel access security.
I don't think that's our problem, because we have not implemented channel access security on any of our IOCs. The PVs in the remote IOC are writeable, and in fact the previous version of the sequencer we were using (1.9.2beta12 from R3.13.7) was connecting to the PVs within a minute or so, after initial failures/disconnects. Upgrading the IOC to 3.14.3 and seq-2.0.4 caused the disconnects to be permanent and fatal.
Mark
- Navigate by Date:
- Prev:
Re: [Fwd: Re: Does DISP work for DB OUT links? Related question] Marty Kraimer
- Next:
Re: [Fwd: Re: Does DISP work for DB OUT links? Related question] Marty Kraimer
- 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: Problem with seq 2.0.4 Carl Lionberger
- Next:
RE: Problem with seq 2.0.4 Mark Rivers
- 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
|