can confirm that with
## EPICS R3.16.1-DEV
this problem has been fixed.
Heinz
> On 08 Jun 2017, at 14:26, Michael Davidsaver <[email protected]> wrote:
>
> Heinz,
>
>> ## EPICS R3.16.0.1-DEV-fhi
>
> Seeing the '-DEV', which revision are you building from? I think this
> has been fixed already. For me this works with 3.16.1.
>
> Michael
>
>
> On 06/08/2017 10:27 AM, Heinz Junkes wrote:
>> Hi,
>>
>> when I try to run an ioc on a system (linux-x86_64) where still some other ioc’s are running (standard Port in use) I see
>>
>> ############################################################################
>> ## EPICS R3.16.0.1-DEV-fhi
>> ## EPICS Base built Jun 8 2017
>> ############################################################################
>> xWidth = 100, yHeight = 100
>> cas warning: Configured TCP port was unavailable.
>> cas warning: Using dynamically assigned TCP port 36485,
>> cas warning: but now two or more servers share the same UDP port.
>> cas warning: Depending on your IP kernel this server may not be
>> cas warning: reachable with UDP unicast (a host's IP in EPICS_CA_ADDR_LIST)
>> tryBind (Addr: 0xa141e01, Port: 5064) <————————— my debug output Addr 10.20.30.1, just bevor tryBind
>> tryBind failed (Addr: 0xa141e01, Port: 5064) < ———————————— my debug output, tryBind failed (line 133 src/ioc/rsrv/caservertask.c)
>> CAS: No TCP server started
>> Thread _main_ (0x19c3f50) can't proceed, suspending.
>> Dumping a stack trace of thread '_main_':
>> [ 0x7ff760d43303]: /home/rtems/EPICS/add-rtems-4.12-api/lib/linux-x86_64/libCom.so.3.16.0(epicsStackTrace+0x73)
>> [ 0x7ff760d32c05]: /home/rtems/EPICS/add-rtems-4.12-api/lib/linux-x86_64/libCom.so.3.16.0(cantProceed+0xc5)
>> [ 0x7ff75fa2801a]: /home/rtems/EPICS/add-rtems-4.12-api/lib/linux-x86_64/libdbCore.so.3.16.0(rsrv_init+0x104a)
>> [ 0x7ff75fa24bfb]: /home/rtems/EPICS/add-rtems-4.12-api/lib/linux-x86_64/libdbCore.so.3.16.0(iocBuild+0x2b)
>> [ 0x7ff75fa24d89]: /home/rtems/EPICS/add-rtems-4.12-api/lib/linux-x86_64/libdbCore.so.3.16.0(iocInit+0x9)
>> [ 0x7ff760d2d4e7]: /home/rtems/EPICS/add-rtems-4.12-api/lib/linux-x86_64/libCom.so.3.16.0(iocshBody+0xc17)
>> [ 0x409b92]: ../../bin/linux-x86_64/IOCCryvisil(main+0x12)
>> [ 0x7ff75ed84830]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)
>> [ 0x409be9]: ../../bin/linux-x86_64/IOCCryvisil(_start+0x29)
>>
>>
>> Defining
>> epicsEnvSet("EPICS_CAS_SERVER_PORT","5066”)
>> in st.cmd solves the problem :
>>
>> Starting iocInit
>> ############################################################################
>> ## EPICS R3.16.0.1-DEV-fhi
>> ## EPICS Base built Jun 8 2017
>> ############################################################################
>> xWidth = 100, yHeight = 100
>> tryBind (Addr: 0xa141e01, Port: 5066)
>> iocRun: All initialization complete
>> ## Start any sequence programs
>> #seq(sncxxx, "user=rtems")
>> #startPVAServer
>> epics>
>>
>>
>> I am not using the actual src/ioc/rsrv/caservertask.c with the “autoMaxBytes” extension.
>>
>> Heinz
>>
>>
>>
>
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- References:
- binding trouble if Port is already in use, src/ioc/rsrv/caservertask.c Heinz Junkes
- Re: binding trouble if Port is already in use, src/ioc/rsrv/caservertask.c Michael Davidsaver
- Navigate by Date:
- Prev:
Re: Arbitrary limit on timeouts? Andrew Johnson
- Next:
startPVAServer takes 15 seconds Mark Rivers
- 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:
Re: binding trouble if Port is already in use, src/ioc/rsrv/caservertask.c Heinz Junkes
- Next:
Build failed in Jenkins: epics-base-3.15-mac-test #128 APS Jenkins
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
|