Can I force it to listen on 5076 instead of falling back to another port? It seems to be falling back to the dynamically assigned port number excessively. I checked to see if anything was bound to 5076 with lsof |grep 5076 and ss -tulpn |grep 5076, but it still reported a dynamically assigned port.
I don't think this is the whole story, because on my latest invocation of the IOC I did NOT get a dynamic port, but phoebus still told me that the PVs were disconnected, and it tried to look at a stale port number to communicate with the IOC. Eventually I seem to be able to get Phoebus to switch back to the default ports, but so far it's just a process of trial and error to find something that works.
Greg
> -----Original Message-----
> From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Leblanc, Gregory
> via Tech-talk
> Sent: Monday, August 21, 2023 10:26 AM
> To: tech-talk at aps.anl.gov
> Subject: [External] Trouble with pva:// on Phoebus with often-restarted IOCs
>
> Use caution with links and attachments.
>
> Hi folks,
>
> I'm working on developing an HMI here at the same time that I'm developing the
> .db files. I'm using the Phoebus nightly builds on a windows machine, and epics-
> base checked out from github, compiled on CentOS 9 Stream. I'm also trying to
> use pva:// for all the PVs in Phoebus . My typical workflow is to add a new record
> to the .db file, stop the IOC, make distclean, make, and restart with st.cmd.
> Next, I'll add a new widget to the Phoebus interface. The first time I launch the
> Phoebus display for the day, everything seems to work OK. On all subsequent
> times, the PVs show up in a disconnected state. If I switch to ca://, I don't see this
> issue. I think this is somehow related to the dynamically assigned TCP port
> numbers, but I'm unclear on what changes between the first launch and all
> subsequent launches. In my IOC output, I see:
>
> First launch:
> 2023-08-21T09:13:00.122 Using dynamically assigned TCP port 38547.
>
> Next launch:
> 2023-08-21T09:13:46.475 Using dynamically assigned TCP port 34715.
>
> And in the Error Log on Phoebus:
> 2023-08-21 10:21:46 WARNING [org.epics.pva] Cannot connect to TCP
> /10.0.0.241:34715
>
> I have confirmed that indeed I cannot telnet to the second port number listed
> when things aren't working, although I haven't tried the telnet test when things
> ARE working, but I'll try to do that today. I've opened ports 5076/udp, 5075/tcp,
> 5064 and 5065 both tcp and udp. Any thoughts on where to go next?
> Greg
>
> --
> Gregory Leblanc
> Accelerator Engineer
> Edwards Accelerator Lab - Ohio University
> 123 University Terrace
> Athens, OH 45701 USA
> leblanc at ohio.edu
> M: (401) 52-OUAL1 or (401) 526-8251
- Replies:
- Re: [External] Trouble with pva:// on Phoebus with often-restarted IOCs Torsten Bögershausen via Tech-talk
- Re: [External] Trouble with pva:// on Phoebus with often-restarted IOCs Michael Davidsaver via Tech-talk
- References:
- Trouble with pva:// on Phoebus with often-restarted IOCs Leblanc, Gregory via Tech-talk
- Navigate by Date:
- Prev:
Trouble with pva:// on Phoebus with often-restarted IOCs Leblanc, Gregory via Tech-talk
- Next:
Re: [External] Trouble with pva:// on Phoebus with often-restarted IOCs Torsten Bögershausen 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
- Navigate by Thread:
- Prev:
Trouble with pva:// on Phoebus with often-restarted IOCs Leblanc, Gregory via Tech-talk
- Next:
Re: [External] Trouble with pva:// on Phoebus with often-restarted IOCs Torsten Bögershausen 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
|