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: Re: Fwd: pvxs Access/list problem
From: Michael Davidsaver via Tech-talk <[email protected]>
To: "Heinz Junkes (FHI)" <[email protected]>
Cc: EPICS Tech-Talk <[email protected]>
Date: Wed, 12 Nov 2025 17:08:39 -0800
On 11/11/25 8:47 AM, Heinz Junkes (FHI) via Tech-talk wrote:
It must have something to do with clock synchronization/NTP (that's my guess).
Immediately after booting, when NTP is not yet synchronized, pvlist and pvget PV work, for example.

Can you check to see if the RTEMS network configuration changes?

Also, could you set the $PVXS_LOG environment variable in RTEMS prior to IOC startup?  Before the registerRecordDeviceDriver call?

epicsEnvSet( "PVXS_LOG", "pvxs.iface*=DEBUG" )

In an effort to handle changing network configuration changes, PVXS will occasionally re-query the list of local interfaces.  This has long been the case, however I did recently make a change to _when_ this happens.

With logging enabled, you should see lines like "Ignoring interface" and "Found interface":

2025-11-12T17:05:54.458712015 DEBUG pvxs.iface Ignoring interface 'lo' address family=17
2025-11-12T17:05:54.458719705 DEBUG pvxs.iface Ignoring interface 'wlp0s20f3' address family=17
2025-11-12T17:05:54.458721909 DEBUG pvxs.iface Ignoring interface 'br0' address family=17
2025-11-12T17:05:54.458723705 DEBUG pvxs.iface Ignoring interface 'tap0' address family=17
2025-11-12T17:05:54.458746937 DEBUG pvxs.iface Found interface 1 "lo" w/ 2 127.0.0.1
2025-11-12T17:05:54.458794954 DEBUG pvxs.iface Found interface 3 "wlp0s20f3" w/ 2 192.168.169.88
2025-11-12T17:05:54.458805716 DEBUG pvxs.iface Found interface 4 "br0" w/ 2 10.127.127.1
2025-11-12T17:05:54.458821577 DEBUG pvxs.iface Found interface 1 "lo" w/ 10 [::1]
2025-11-12T17:05:54.458835767 DEBUG pvxs.iface Found interface 3 "wlp0s20f3" w/ 10 [fe80::c136:44be:4935:b3e8]
%3
2025-11-12T17:05:54.458875297 DEBUG pvxs.iface Found interface 4 "br0" w/ 10 [fe80::9453:55ff:fe80:63a1]%4



References:
Re: pvxs Access/list problem Heinz Junkes (FHI) via Tech-talk
Fwd: pvxs Access/list problem Heinz Junkes (FHI) via Tech-talk

Navigate by Date:
Prev: Re: caget: Identical process variable names on multiple servers Michael Davidsaver via Tech-talk
Next: aiopvxs Python library available Mike Smith 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: Re: pvxs Access/list problem Heinz Junkes via Tech-talk
Next: Re: pvxs Access/list problem Heinz Junkes 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 ·