Re: pvget -m timeout after first value

[Michael Davidsaver <mdavidsaver@gmail.com>]

Can you update pvDataCPP and pvAccessCPP, then retest?

use branch 'structformatter' in https://github.com/mdavidsaver/pvDataCPP

use branch 'pvtoolsrework' in https://github.com/mdavidsaver/pvAccessCPP


cf. https://github.com/epics-base/pvAccessCPP/pull/129


On 10/26/18 12:13 PM, Kasemir, Kay via Core-talk wrote:
> Hi:
> 
> I'm using EPICS base 7.0.1.1 with either the result of
> 
> makeBaseApp.pl -t example example;  makeBaseApp.pl -i -t example example
> 
> or with the neutrons demo from
> 
> git clone https://github.com/kasemir/EPICSV4Sandbox.git
> cd EPICSV4Sandbox/neutronsDemoServer
> make
> bin/$EPICS_HOST_ARCH/neutronServerMain
> 
> 
> Using `pvget` always works fine, printing one value and then quitting.
> 
> But `pvget -m` will sometimes only show one value, and then print "Timeout" and quit:
> 
> pvget –m training:ai1
> training:ai1                   4
> Timeout
> 
> pvget –m -r 'field(time_of_flight, pixel)' neutrons
> neutrons
> structure 
>     epics:nt/NTScalarArray:1.0 time_of_flight
>         uint[] value [11561,11561,11561,11561,11561,11561,11561,11561,11561,11561]
>     epics:nt/NTScalarArray:1.0 pixel
>         uint[] value [115610,115610,115610,115610,115610,115610,115610,115610,115610,115610]
> Timeout
> 
> 
> It seems to take about 3 seconds, and indeed using the `-w` options allows to extend the time:
> 
> $ pvget -w 60 –m -r 'field(time_of_flight, pixel)' neutrons
> neutrons
> structure 
>     epics:nt/NTScalarArray:1.0 time_of_flight
>         uint[] value [52612,52612,52612,52612,52612,52612,52612,52612,52612,52612]
>     epics:nt/NTScalarArray:1.0 pixel
>         uint[] value [526120,526120,526120,526120,526120,526120,526120,526120,526120,526120]
> <.. 60 seconds ..>
> Timeout
> 
> 
> The only clue:
> This is in a Linux VM.
> All's fine when directly in the VM, i.e. in VirtualBox.
> But when I ssh into the VM from the host, I get these timeouts about half the time.
> 
> Note I'm not talking about pvget from the host to an IOC in the VM.
> The IOC, custom PVA server and pvget are all inside the VM.
> EPICS_PVA_ADDR_LIST=10.0.2.15
> EPICS_PVA_AUTO_ADDR_LIST=NO 
> 
> At times where ssh-into-the-VM and then 'pvget -m' time out,
> the same 'pvget -m' works fine in a terminal within the VM.
> 
> I understand that the UDP connection could be iffy,
> but once it connects and gets the first value via TCP, why then timeout?
> -Kay
>