Experimental Physics and Industrial Control System
|
Hi Joe,
On 5/24/19 4:16 PM, Sullivan, Joseph via Tech-talk wrote:
The following warning messages are appearing periodically (~2hrs) on all the EPICs IOC's (VxWorks and Linux -
base-3.14.12.3) on a beamline here at the APS - (base-3.14.12.3).
../udpiiu.cpp: Undecipherable (payload too small) UDP msg from 169.254.0.2:3956 ignored
../udpiiu.cpp: Undecipherable (payload too small) UDP msg from 169.254.132.146:3956 ignored
../udpiiu.cpp: Undecipherable (payload too small) UDP msg from 169.254.0.2:3956 ignored
../udpiiu.cpp: Undecipherable (payload too small) UDP msg from 169.254.0.2:3956 ignored
../udpiiu.cpp: Undecipherable (payload too small) UDP msg from 169.254.0.2:3956 ignored
../udpiiu.cpp: Undecipherable (payload too small) UDP msg from 169.254.0.2:3956 ignored
../udpiiu.cpp: Undecipherable (payload too small) UDP msg from 169.254.0.2:3956 ignored
../udpiiu.cpp: Undecipherable (payload too small) UDP msg from 169.254.132.146:3956 ignored
../udpiiu.cpp: Undecipherable (payload too small) UDP msg from 169.254.132.146:3956 ignored
IP addresses in the 169.254 range are self-assigned by a computer that cannot get an address from a DHCP server. You should have IT track down which network port(s) are using these addresses and get those machines configured properly (or have them disconnected).
Eventually the CAS-Event processes fail (after a day or so). A reboot brings everything back and the sequence starts over.
That is unfortunate, we would like IOCs to be immune to bad packets. If you can get a packet capture of the broadcast packets going to port 5064 on this network (before the rogue client gets killed) it would let us try to prevent this particular payload from
crashing the IOCs.
This happened after the IOCs where brought up after a shutdown period.
Is this a network issue (someone on the CA ports that should not be) or should I look at the CA Clients (medm)?
I don't think these messages would be caused by a real CA client, even one that doesn't have a proper IP address. You need to get the network police down to that beamline to find the rogue machine(s). It's a pity it's now after 5pm on a holiday weekend; Mary
is still here though.
- Andrew
--
Complexity comes for free, Simplicity you have to work for.
|
- Replies:
- Re: UDP Warnings (VME and Linux) - Subnet wide Sullivan, Joseph via Tech-talk
- References:
- UDP Warnings (VME and Linux) - Subnet wide Sullivan, Joseph via Tech-talk
- Navigate by Date:
- Prev:
Re: UDP Warnings (VME and Linux) - Subnet wide Mark Rivers via Tech-talk
- Next:
Stream module git link broken? Gofron, Kazimierz 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:
Re: UDP Warnings (VME and Linux) - Subnet wide Mark Rivers via Tech-talk
- Next:
Re: UDP Warnings (VME and Linux) - Subnet wide Sullivan, Joseph 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
|
ANJ, 10 Jun 2019 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|