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 17:42:46 +0000
> it would be good to start with the latest from github.com for all modules...
Did that. Everything compiles, the makebaseapp example again serves PVA:

$ pvget training:ai1
training:ai1 2018-10-29T13:30:43.942 9 MAJOR DEVICE HIHI 

[training@training tools]$ pvget -m training:ai1
training:ai1 2018-10-29T13:30:47.945 3 MINOR DEVICE LOW 
training:ai1 2018-10-29T13:30:48.943 4 MINOR DEVICE LOW 
Ctrl-C

$ pvget -d training:ai1
2018-10-29T13:37:28.267 Client security plug-in 'ca' installed.
2018-10-29T13:37:28.267 Creating datagram socket from: 0.0.0.0:45470.
2018-10-29T13:37:28.267 Broadcast address #0: 10.0.2.15:5076. (unicast)
2018-10-29T13:37:28.267 Setting up UDP for interface 10.0.2.15/255.255.255.0, broadcast 10.0.2.255, dest <none>.
2018-10-29T13:37:28.267 Creating datagram socket from: 10.0.2.15:5076.
2018-10-29T13:37:28.267 Creating datagram socket from: 10.0.2.255:5076.
2018-10-29T13:37:28.267 Setting up UDP for interface 192.168.122.1/255.255.255.0, broadcast 192.168.122.255, dest <none>.
2018-10-29T13:37:28.267 Creating datagram socket from: 192.168.122.1:5076.
2018-10-29T13:37:28.267 Creating datagram socket from: 192.168.122.255:5076.
2018-10-29T13:37:28.267 Creating datagram socket from: 224.0.0.128:5076.
2018-10-29T13:37:28.267 Local multicast enabled on 127.0.0.1/224.0.0.128:5076.
2018-10-29T13:37:28.267 Sending 58 bytes 0.0.0.0:45470 -> 10.0.2.15:5076.
2018-10-29T13:37:28.267 UDP Rx (58) 10.0.2.15:5076 <- 10.0.2.15:45470
Waiting...
2018-10-29T13:37:28.267 UDP Tx (82) 10.0.2.15:5076 -> 224.0.0.128:5076.
2018-10-29T13:37:28.267 UDP Rx (82) 224.0.0.128:5076 <- 10.0.2.15:5076
2018-10-29T13:37:28.267 UDP Rx (53) 0.0.0.0:45470 <- 10.0.2.15:43452
2018-10-29T13:37:28.267 Connecting to PVA server: 10.0.2.15:48086.
2018-10-29T13:37:28.267 Opening socket to PVA server 10.0.2.15:48086, attempt 1.
2018-10-29T13:37:28.268 Socket connected to PVA server: 10.0.2.15:48086.
2018-10-29T13:37:28.268 Acquiring transport to 10.0.2.15:48086.
2018-10-29T13:37:28.268 Connected to PVA server: 10.0.2.15:48086.
training:ai1 2018-10-29T13:37:27.950 3 MINOR DEVICE LOW 
2018-10-29T13:37:28.268 Releasing TCP transport to 10.0.2.15:48086.
2018-10-29T13:37:28.268 TCP socket to 10.0.2.15:48086 is to be closed.
2018-10-29T13:37:28.268 UDP socket 0.0.0.0:0 closed.
2018-10-29T13:37:28.268 UDP Rx (0) 0.0.0.0:45470 <- 10.0.2.15:43452
2018-10-29T13:37:28.269 UDP socket 10.0.2.15:5076 closed.
2018-10-29T13:37:28.269 UDP Rx (0) 10.0.2.15:5076 <- 10.0.2.15:45470
2018-10-29T13:37:28.269 UDP socket 10.0.2.255:5076 closed.
2018-10-29T13:37:28.269 UDP Rx (0) 10.0.2.255:5076 <- <Ukn Addr Type>
2018-10-29T13:37:28.269 UDP socket 192.168.122.1:5076 closed.
2018-10-29T13:37:28.269 UDP Rx (0) 192.168.122.1:5076 <- <Ukn Addr Type>
2018-10-29T13:37:28.269 UDP socket 192.168.122.255:5076 closed.
2018-10-29T13:37:28.269 UDP Rx (0) 192.168.122.255:5076 <- <Ukn Addr Type>
2018-10-29T13:37:28.269 UDP socket 224.0.0.128:5076 closed.
2018-10-29T13:37:28.269 UDP Rx (0) 224.0.0.128:5076 <- 10.0.2.15:5076
Done



PV Info doesn't work, though:

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

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

As you can see from the -d output, I have EPICS_PVA_ADDR_LIST set to 10.0.2.15, the IP of the VM, which is fine for pvget.
Pvinfo never shows anything:

$ /sbin/ifconfig 
enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
        inet6 fe80::7f29:bd96:809b:6dc9  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:c0:85:fe  txqueuelen 1000  (Ethernet)
        RX packets 98356  bytes 139960542 (133.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 45066  bytes 2757703 (2.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 928  bytes 74967 (73.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 928  bytes 74967 (73.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:09:e8:c5  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


-Kay

Replies:
Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
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

Navigate by Date:
Prev: Re: Which version are you using Re: group PV question Timo Korhonen
Next: Re: pvget -m timeout after first value Kasemir, Kay via Core-talk
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 Kasemir, Kay via Core-talk
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 ·