> There is already a socket bound to UDP 5076 which is not a PVA server/client (which should share w/ SO_REUSEADDR).
Yes, but why?
This happens on all vxWorks IOCs, and only on vxWorks IOCs. I don't know of anything I am doing that would be creating a socket bound to that port.
On 2 systems the message says <IPA> rather than 164.54.160.xxx.
13BMA.log:Wed Jan 23 15:20:23 20192019-01-23T15:20:23.891 Error binding socket 164.54.160.74:5076: S_errno_EADDRINUSE.
13BMC.log:Thu Mar 14 10:54:07 20192019-03-14T10:54:07.443 Error binding socket <IPA>: S_errno_EADDRINUSE.
13BMD.log:Thu Jan 2 11:55:09 20202020-01-02T17:55:09.970 Error binding socket 164.54.160.95:5076: S_errno_EADDRINUSE.
13IDA.log:Thu Jan 10 11:33:39 20192019-01-10T11:33:39.369 Error binding socket 164.54.160.75:5076: S_errno_EADDRINUSE.
13IDC.log:Thu Jan 2 11:13:46 20202020-01-02T17:13:46.898 Error binding socket 164.54.160.94:5076: S_errno_EADDRINUSE.
13IDD.log:Tue Mar 26 13:47:59 20192019-03-26T13:47:59.664 Error binding socket <IPA>: S_errno_EADDRINUSE.
13IDE.log:Sat Jan 26 14:42:21 20192019-01-26T14:42:21.834 Error binding socket 164.54.160.99:5076: S_errno_EADDRINUSE.
This is the output of inetstatShow on 164.54.160.75.
ioc13ida> inetstatShow
INET sockets
Prot Recv-Q Send-Q Local Address Foreign Address State
TCP 0 0 0.0.0.0.23 0.0.0.0.* LISTEN
TCP 0 0 0.0.0.0.111 0.0.0.0.* LISTEN
TCP 0 0 0.0.0.0.5064 0.0.0.0.* LISTEN
TCP 0 0 0.0.0.0.5075 0.0.0.0.* LISTEN
TCP 0 0 164.54.160.75.58992 164.54.160.12.5064 ESTABLISHED
TCP 0 0 164.54.160.75.54236 164.54.160.94.5064 ESTABLISHED
TCP 0 0 164.54.160.75.5064 164.54.160.129.63701 ESTABLISHED
TCP 0 0 164.54.160.75.58308 164.54.160.99.5064 ESTABLISHED
TCP 0 0 164.54.160.75.5064 164.54.160.116.62090 ESTABLISHED
TCP 0 0 164.54.160.75.5064 164.54.160.111.47064 ESTABLISHED
TCP 0 0 164.54.160.75.5064 164.54.160.82.42658 ESTABLISHED
TCP 0 0 164.54.160.75.5064 164.54.160.99.61986 ESTABLISHED
TCP 0 0 164.54.160.75.5064 164.54.160.43.54230 ESTABLISHED
TCP 0 32 164.54.160.75.5064 164.54.160.93.51418 ESTABLISHED
TCP 0 0 164.54.160.75.5064 164.54.160.82.42662 ESTABLISHED
TCP 0 0 164.54.160.75.5064 164.54.160.82.42664 ESTABLISHED
TCP 0 0 164.54.160.75.5064 164.54.160.24.57596 ESTABLISHED
TCP 0 0 164.54.160.75.50353 164.54.160.99.5064 ESTABLISHED
TCP 0 0 164.54.160.75.5064 164.54.160.82.42696 ESTABLISHED
TCP 0 0 164.54.160.75.5064 164.54.160.148.59787 ESTABLISHED
TCP 0 0 164.54.160.75.5064 164.54.160.74.51446 ESTABLISHED
UDP 0 0 127.0.0.1.20005 127.0.0.1.20004
UDP 0 0 0.0.0.0.123 0.0.0.0.*
UDP 0 0 127.0.0.1.20045 127.0.0.1.20044
UDP 0 0 0.0.0.0.111 0.0.0.0.*
UDP 0 0 0.0.0.0.58989 0.0.0.0.*
UDP 0 0 0.0.0.0.62001 0.0.0.0.*
UDP 0 0 0.0.0.0.60786 0.0.0.0.*
UDP 0 0 164.54.160.75.5076 0.0.0.0.*
UDP 0 0 164.54.160.255.5076 0.0.0.0.*
UDP 0 0 224.0.0.128.5076 0.0.0.0.*
UDP 0 0 0.0.0.0.54464 0.0.0.0.*
UDP 0 0 0.0.0.0.49428 0.0.0.0.*
UDP 0 0 0.0.0.0.5064 0.0.0.0.*
UDP 0 0 0.0.0.0.55281 0.0.0.0.*
UDP 0 0 224.0.0.128.5076 0.0.0.0.*
UDP 0 0 0.0.0.0.50389 0.0.0.0.*
UDP 0 0 0.0.0.0.56937 0.0.0.0.*
UDP 0 0 0.0.0.0.5065 0.0.0.0.*
UDP 0 0 0.0.0.0.51877 0.0.0.0.*
UDP 0 0 0.0.0.0.50820 0.0.0.0.*
UDP 0 0 0.0.0.0.61969 0.0.0.0.*
UDP 0 0 0.0.0.0.987 0.0.0.0.*
UDP 0 0 0.0.0.0.62807 0.0.0.0.*
UDP 0 0 0.0.0.0.985 0.0.0.0.*
UDP 0 0 127.0.0.1.58319 127.0.0.1.50389
UDP 0 0 127.0.0.1.52021 127.0.0.1.56937
UDP 0 0 164.54.160.75.54341 0.0.0.0.*
UDP 0 0 127.0.0.1.62285 127.0.0.1.62807
UDP 0 0 0.0.0.0.56299 0.0.0.0.*
UDP 0 0 0.0.0.0.54349 0.0.0.0.*
INET6 sockets
Prot Recv-Q Send-Q Local Address Foreign Address State
These are the UDP sockets on port 5076 from the above list:
UDP 0 0 164.54.160.75.5076 0.0.0.0.*
UDP 0 0 164.54.160.255.5076 0.0.0.0.*
UDP 0 0 224.0.0.128.5076 0.0.0.0.*
UDP 0 0 224.0.0.128.5076 0.0.0.0.*
The 224.0.0.128 addresses are multicast? Is this used by PVA?
Thanks,
Mark
________________________________
From: Michael Davidsaver <[email protected]>
Sent: Saturday, January 11, 2020 8:44 PM
To: Mark Rivers
Cc: [email protected]
Subject: Re: Error message binding socket 5076 on vxWorks
There is already a socket bound to UDP 5076 which is not a PVA server/client
(which should share w/ SO_REUSEADDR).
On 1/11/20 6:14 PM, Mark Rivers via Core-talk wrote:
> I am getting an error each time I boot my vxWorks IOCs:
>
>
> **************
>
> iocRun: All initialization complete
> 2020-01-12T00:15:50.825 Error binding socket 164.54.160.75:5076: S_errno_EADDRINUSE.
> **************
>
>
> 164.54.60.75 is the address of this IOC.
>
>
> The error message is always the next message after "All initialization complete".
>
>
> Is this something I am doing wrong?
>
>
> Mark
>
>
- Replies:
- Re: Error message binding socket 5076 on vxWorks Michael Davidsaver via Core-talk
- References:
- Error message binding socket 5076 on vxWorks Mark Rivers via Core-talk
- Re: Error message binding socket 5076 on vxWorks Michael Davidsaver via Core-talk
- Navigate by Date:
- Prev:
Re: Error message binding socket 5076 on vxWorks Michael Davidsaver via Core-talk
- Next:
Re: Error message binding socket 5076 on vxWorks Michael Davidsaver via Core-talk
- Index:
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:
Re: Error message binding socket 5076 on vxWorks Michael Davidsaver via Core-talk
- Next:
Re: Error message binding socket 5076 on vxWorks Michael Davidsaver via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·