Re: PVA Gateway (p4p) is Missing some Status PVs

[Heinz Junkes via Core-talk <core-talk at aps.anl.gov>]

I can confirm that with p4p version: 4.1.10

(base) hactar:~ junkes$ pvget FHIFEL:PVA_GW:STS:cache

FHIFEL:PVA_GW:STS:cache <undefined>              []

Still an empty list there.

(base) hactar:~ junkes$ pvget FHIFEL:PVA_GW:STS:ds:byhost:tx

FHIFEL:PVA_GW:STS:ds:byhost:tx 2023-08-24 21:54:49.296

Account              Client  "TX (B/s)"

wieland 141.14.64.252:61925 1.20526e+06

But ds:byhost:tx is ok.

Heinz

On 24. Aug 2023, at 11:43, Michael Davidsaver via Core-talk <core-talk at aps.anl.gov> wrote:

On 8/23/23 09:56, Murray, Doug wrote:

We’ve been setting up the latest version of the p4p PVA Gateway (R4.1.9) and have noticed that a couple status PVs are no longer providing expected results.
 * The *<statusprefix>cache* PV always returns an empty list, but previously provided “a list of channels to which the GW Client is connected”.

This was an oversight when porting to PVXS.  I had a couple of TODO items
which did not get marked as such.

https://github.com/mdavidsaver/p4p/commit/2930d9fcc0370ef3f292f5d24a46d1b4ef98f314#diff-8061cbf72533fa48d08f5f9891a94f5ebeaaffbba7f9e5cdae7aa10d594d09deR945

 * The *<statusprefix>ds:byhost:tx* PV always provides the same client host address as 255.255.255.255, regardless of the client’s true IP address.

Can you provide some more detail?

My usual testing is all on one host with different ports.  So I can see
how I might not notice an issue like this.  However, I can check the port
numbers with the output of `netstat -tpn`.  From what I see, I think the
IP:port reported by in the ds: and us: tables are socket peer addresses.

These were working well in previous versions.  Has anybody else encountered this?
cheers
-doug
SLAC