Experimental Physics and Industrial Control System
|
Hi,
Geoff Savage wrote:
Hi,
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.
Thanks
Geoff
We occasionally encounter this message on our IOCs.
1) This message, as pointed by Andrew, one of our terminal server
responds to the CA search UDP
message at port 5064 and sends a NON-epics reply to the IOC which send
out the CA search UDP message.
Although we have several terminal servers of same type, only one of them
causes this symptom.
2) Usually, it indicates there is unresolved channel connection on this
IOC. So we have check channel
connection status on this IOC.
3) I believe the program output this message has memory leak. So if you
leave this message long enough, this would cause low memory situation,
according to my experience.
Regards,
Noboru Yamamoto
KEKB control group
KEK, JAPAN
- Replies:
- RE: bad UDP messages Jeff Hill
- References:
- bad UDP messages Geoff Savage
- Navigate by Date:
- Prev:
Re: et_wish Andrew Johnson
- Next:
mbboDirectCamac device support routine 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
- Navigate by Thread:
- Prev:
Re: bad UDP messages Andrew Johnson
- Next:
RE: bad UDP messages Jeff Hill
- 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 Aug 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|