EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: pvget -m timeout after first value
From: "Kasemir, Kay via Core-talk" <[email protected]>
To: Michael Davidsaver <[email protected]>
Cc: EPICS Core Talk <[email protected]>
Date: Mon, 29 Oct 2018 18:11:34 +0000
>  Yes, something funny is happening.  Below is what 'pvinfo -d' on a machine
> with two NICs should look like.  Note the "Broadcast address #1" which is
> missing in your case.
> From the ordering in your log it looks like somehow at attempt is being
> made to send the GetField message before the TCP connection is created.
> This smells like a race condition.

When I unset EPICS_PVA_ADDR_LIST and EPICS_PVA_AUTO_ADDR_LIST, I also get two addresses listed, but same end result: pvget works, pvinfo doesn't.

$ pvget  training:ai1
training:ai1 2018-10-29T14:09:16.942 2 MAJOR DEVICE LOLO 

$ pvinfo   training:ai1
training:ai1 Error: channel destroyed

$ pvinfo -d  training:ai1
2018-10-29T14:09:22.040 Client security plug-in 'ca' installed.
2018-10-29T14:09:22.040 Creating datagram socket from: 0.0.0.0:34005.
2018-10-29T14:09:22.040 Broadcast address #0: 10.0.2.255:5076. (not unicast)
2018-10-29T14:09:22.040 Broadcast address #1: 192.168.122.255:5076. (not unicast)
2018-10-29T14:09:22.040 Setting up UDP for interface 10.0.2.15/255.255.255.0, broadcast 10.0.2.255, dest <none>.
2018-10-29T14:09:22.040 Creating datagram socket from: 10.0.2.15:5076.
2018-10-29T14:09:22.040 Creating datagram socket from: 10.0.2.255:5076.
2018-10-29T14:09:22.040 Setting up UDP for interface 192.168.122.1/255.255.255.0, broadcast 192.168.122.255, dest <none>.
2018-10-29T14:09:22.040 Creating datagram socket from: 192.168.122.1:5076.
2018-10-29T14:09:22.040 Creating datagram socket from: 192.168.122.255:5076.
2018-10-29T14:09:22.040 Creating datagram socket from: 224.0.0.128:5076.
2018-10-29T14:09:22.040 Local multicast enabled on 127.0.0.1/224.0.0.128:5076.
2018-10-29T14:09:22.040 Sending 58 bytes 0.0.0.0:34005 -> 10.0.2.255:5076.
2018-10-29T14:09:22.040 UDP Rx (58) 10.0.2.255:5076 <- 10.0.2.15:34005
2018-10-29T14:09:22.040 Sending 58 bytes 0.0.0.0:34005 -> 192.168.122.255:5076.
2018-10-29T14:09:22.040 UDP Rx (58) 192.168.122.255:5076 <- 192.168.122.1:34005
2018-10-29T14:09:22.040 UDP Rx (53) 0.0.0.0:34005 <- 10.0.2.15:43452
training:ai1 Error: channel destroyed
2018-10-29T14:09:22.041 UDP socket 0.0.0.0:0 closed.
2018-10-29T14:09:22.041 Connecting to PVA server: 10.0.2.15:48086.
2018-10-29T14:09:22.041 Opening socket to PVA server 10.0.2.15:48086, attempt 1.
2018-10-29T14:09:22.041 Socket connected to PVA server: 10.0.2.15:48086.
2018-10-29T14:09:22.041 Acquiring transport to 10.0.2.15:48086.
2018-10-29T14:09:22.041 Connected to PVA server: 10.0.2.15:48086.
2018-10-29T14:09:22.041 UDP socket 10.0.2.15:5076 closed.
2018-10-29T14:09:22.041 UDP Rx (0) 10.0.2.15:5076 <- <Ukn Addr Type>
2018-10-29T14:09:22.041 UDP socket 10.0.2.255:5076 closed.
2018-10-29T14:09:22.041 UDP Rx (0) 10.0.2.255:5076 <- 10.0.2.15:34005
2018-10-29T14:09:22.041 UDP socket 192.168.122.1:5076 closed.
2018-10-29T14:09:22.041 UDP Rx (0) 192.168.122.1:5076 <- <Ukn Addr Type>
2018-10-29T14:09:22.041 UDP socket 192.168.122.255:5076 closed.
2018-10-29T14:09:22.041 UDP Rx (0) 192.168.122.255:5076 <- 192.168.122.1:34005
2018-10-29T14:09:22.041 UDP socket 224.0.0.128:5076 closed.
2018-10-29T14:09:22.041 UDP Rx (0) 224.0.0.128:5076 <- <Ukn Addr Type>
2018-10-29T14:09:23.153 PVA client context destroyed with 1 transport(s) active.

Replies:
Re: pvget -m timeout after first value Michael Davidsaver
References:
pvget -m timeout after first value Kasemir, Kay via Core-talk
Re: pvget -m timeout after first value Michael Davidsaver
Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
Re: pvget -m timeout after first value Michael Davidsaver
Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
Re: pvget -m timeout after first value Michael Davidsaver
Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
Re: pvget -m timeout after first value Michael Davidsaver
Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
Re: pvget -m timeout after first value Michael Davidsaver
Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
Re: pvget -m timeout after first value Michael Davidsaver

Navigate by Date:
Prev: Re: pvget -m timeout after first value Michael Davidsaver
Next: Re: pvget -m timeout after first value Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: pvget -m timeout after first value Michael Davidsaver
Next: Re: pvget -m timeout after first value Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
ANJ, 29 Oct 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·