Hi Geoff,
Geoff Savage wrote:
>
> Here is an error message about bad UDP messages. We have seen this
> from two different IOCs over the weekend.
>
> CAC: post_msg(): Corrupt cmd in UDP msg b
> ../iocinf.c: bad UDP msg from d0olctl50.fnal.gov:5064
>
> Could this be caused by low memory on the IOCs? Each were running
> around 80-90% of memory capacity of 16MB.
I'll leave Jeff to answer that, but would ask what you know about the
machine d0olctl50.fnal.gov? Does it normally have CA connections to the
relevent IOCs? Could it have been running something like a network
sniffer at the time of the messages? If something other than CA had sent
either directed or broadcast UDP messages to port 5064 I would expect
something like that error to be reported.
- Andrew
--
Perfection is reached, not when there is no longer anything to add,
but when there is no longer anything to take away.
- Antoine de Saint-Exupery
- References:
- bad UDP messages Geoff Savage
- Navigate by Date:
- Prev:
bad UDP messages Geoff Savage
- Next:
RE: VxWorks on Linux Mark Rivers
- 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:
bad UDP messages Geoff Savage
- Next:
Re: bad UDP messages Noboru Yamamoto
- 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
|