If you need a 3.13 client, you can compile a fresh 3.13.10 host
installation. Is fun. I did it recently. (Together with a target
compilation for VxWorks 6.9. Even more fun.)
--
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1971737
Title:
EPICS 3.13 clients cannot connect to EPICS 7 or 3.16
Status in EPICS Base:
New
Bug description:
Since commit 95fd255d "rsrv: ignore CA client version older than v4.4"
from Jul 30 2016, EPICS 3.13 clients cannot connect any more, even
though their CA version is V4.8.
The reason is that camessage drops the incoming CA_PROTO_SEARCH
messages because the 3.13 client has not yet sent a CA_PROTO_VERSION
message and thus the code reads client->minor_version_number as 0.
This is a huge hindrance for upgrading 3.14 IOCs to EPICS 7 when there
are still 3.13 IOC (which cannot be upgraded yet) in the network which
need to connect.
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1971737/+subscriptions
- References:
- [Bug 1971737] [NEW] EPICS 3.13 clients cannot connect to EPICS 7 or 3.16 Dirk Zimoch via Core-talk
- Navigate by Date:
- Prev:
[Bug 1971737] Re: EPICS 3.13 clients cannot connect to EPICS 7 or 3.16 mdavidsaver via Core-talk
- Next:
[Bug 1971737] Re: EPICS 3.13 clients cannot connect to EPICS 7 or 3.16 mdavidsaver via Core-talk
- Index:
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:
[Bug 1971737] Re: EPICS 3.13 clients cannot connect to EPICS 7 or 3.16 mdavidsaver via Core-talk
- Next:
[Bug 1971737] Re: EPICS 3.13 clients cannot connect to EPICS 7 or 3.16 mdavidsaver via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
<2022>
2023
2024
|