I had a problem with pvget today.
I am running an areaDetector IOC that runs qsrv and also the NDPluginPva. The IOC is running 7.0.3, linux-x86_64 on Ubuntu 18.
On this IOC this is the output of pvasr:
epics> pvasr
pvAccess Server v7.0.0
Active configuration (w/ defaults)
EPICS_PVAS_INTF_ADDR_LIST = 0.0.0.0:5075
EPICS_PVAS_BEACON_ADDR_LIST =
EPICS_PVAS_AUTO_BEACON_ADDR_LIST = YES
EPICS_PVAS_BEACON_PERIOD = 15
EPICS_PVAS_BROADCAST_PORT = 5076
EPICS_PVAS_SERVER_PORT = 5075
EPICS_PVAS_PROVIDER_NAMES = QSRV local
I try to access a PV using caget, pvget –p ca, and pvget –p pva. I am using the 7.0.3 versions of all of these. These are running on the same Ubuntu 18 machine as the IOC.
caget works fine.
**************
TahoeU18:/corvette/home/epics/devel/areaDetector/configure> /corvette/usr/local/epics-devel/base-7.0.3/bin/linux-x86_64-ub18/caget 13SP1:cam1:AcquireTime
13SP1:cam1:AcquireTime 0.001
**************
pvget –p ca works fine.
**************
TahoeU18:/corvette/home/epics/devel/areaDetector/configure> /corvette/usr/local/epics-devel/base-7.0.3/bin/linux-x86_64-ub18/pvget -p ca 13SP1:cam1:AcquireTime
13SP1:cam1:AcquireTime 0.001
**************
pvget –p pva prints a timeout message, and then the program hangs. The only way to kill it is with “kill -9” from another terminal.
**************
TahoeU18:/corvette/home/epics/devel/areaDetector/configure> /corvette/usr/local/epics-devel/base-7.0.3/bin/linux-x86_64-ub18/pvget -p pva 13SP1:cam1:AcquireTime
Timeout
^C^C^C^C
Killed
**************
I tried running the pvget –p pva command on another Linux system (Centos 7, base 7.0.3), talking to the same IOC. It also hung up the same way, I had to kill it with -9.
The IOC appeared to be working fine in all other respects.
I then rebooted the IOC and the problem with pvget –p pva is gone.
**************
TahoeU18:/corvette/home/epics/devel/areaDetector/configure> /corvette/usr/local/epics-devel/base-7.0.3/bin/linux-x86_64-ub18/pvget -p pva 13SP1:cam1:AcquireTime
13SP1:cam1:AcquireTime 2019-08-13 16:15:10.742 0.001
**************
Any idea what could have been wrong that rebooting fixed?
Mark