EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  <20252026  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  <20252026 
<== Date ==> <== Thread ==>

Subject: Name resolution issue in pvagw 4.2.1
From: "Knap, Giles \(DLSLtd,RAL,CEO\) via Tech-talk" <[email protected]>
To: Tech Talk <[email protected]>
Date: Wed, 1 Oct 2025 10:31:08 +0000
I'm seeing the following isssue when using p4p v4.2.1.

When I set EPICS_PVA_ADDR_LIST it works fine for pvxget but fails for pvagw as follows:

$ pvagw /tmp/pvagw.config 
INFO:p4p.gw:*** Gateway STARTS now using "/tmp/pvagw.config".
INFO:p4p.gw:Client effective configuration for theclient:
INFO:p4p.gw:    EPICS_PVA_ADDR_LIST : bl01t-mo-sim-01 bl01t-di-cam-01 bl01t-ea-fastcs-01
INFO:p4p.gw:    EPICS_PVA_AUTO_ADDR_LIST : NO
INFO:p4p.gw:    EPICS_PVA_BROADCAST_PORT : 5076
INFO:p4p.gw:    EPICS_PVA_SERVER_PORT : 5075
2025-10-01T10:17:10.598392304 ERR pvxs.config EPICS_PVA_ADDR_LIST ignoring invalid 'bl01t-mo-sim-01' : Error resolving "bl01t-mo-sim-01" : nodename nor servname provided, or not known
2025-10-01T10:17:10.598754501 ERR pvxs.config EPICS_PVA_ADDR_LIST ignoring invalid 'bl01t-di-cam-01' : Error resolving "bl01t-di-cam-01" : nodename nor servname provided, or not known
2025-10-01T10:17:10.598816543 ERR pvxs.config EPICS_PVA_ADDR_LIST ignoring invalid 'bl01t-ea-fastcs-01' : Error resolving "bl01t-ea-fastcs-01" : nodename nor servname provided, or not known

pvxinfo/get is OK:

$ pip list | grep p4p
p4p                4.2.1
$ export EPICS_PVA_ADDR_LIST="bl01t-mo-sim-01 bl01t-di-cam-01 bl01t-ea-fastcs-01"
$ pvxinfo BL01T-DI-CAM-01:PVA:OUTPUT
BL01T-DI-CAM-01:PVA:OUTPUT from 10.111.7.5:5075
struct "epics:nt/NTNDArray:1.0" {
...

Downgrading to p4p 4.2.0 fixes the issue.

Regards,
giles

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom.

Replies:
Re: Name resolution issue in pvagw 4.2.1 Michael Davidsaver via Tech-talk

Navigate by Date:
Prev: Re: Fast stream-device IOC suddenly disconnects Zimoch, Dirk via Tech-talk
Next: Re: Name resolution issue in pvagw 4.2.1 Michael Davidsaver via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  <20252026 
Navigate by Thread:
Prev: AreaDetector Collaboration Meeting - October 2nd Henrique F. Simoes via Tech-talk
Next: Re: Name resolution issue in pvagw 4.2.1 Michael Davidsaver via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  <20252026 
ANJ, 19 Mar 2026 · Home · News · About · Talk · Base · Modules · Extensions ·
· Distributions · Download · Documents · Links · Licensing ·