Pete,
On Friday, August 28, 1998 7:02 AM, Pete Jemian [SMTP:[email protected]] wrote:
>
> What is causing this error message?
>
> 1998-08-27,22:57:08: 0xc2e7d4 (CA UDP): CAS: UDP send to "164.54.216.13" failed
> because "S_errno_ENOBUFS"
> 1998-08-27,22:57:08: 0xc2e7d4 (CA UDP): CAS: UDP send to "164.54.216.13" failed
> because "S_errno_ENOBUFS"
> 1998-08-27,22:57:08: 0xc2e7d4 (CA UDP): CAS: UDP send to "164.54.216.13" failed
> because "S_errno_ENOBUFS"
>
> A couple of IOCs are generating these messages (time/date stamp added by me).
> Tried rebooting the server (164.54.216.13), that did not help.
>
I see this message from the IOC's CA server when I am testing it under a
heavy UDP load. The server is attempting to send a UDP response frame and
the ENOBUFS error code is returned from the sendto() function. It appears that
this results from a transient congestion in the IP kernel. Since the UDP
portions of CA have built in retransmission timers (as is normal for UDP protocols)
then this situation is benign as long as it is transient. I did not suppress the message
because I felt that it was worthwhile to monitor the frequency of this congestion.
I suspect that this message is scrolling other more important information off of the
screen. I will store an internal counter for these occurrences which will be displayed
by casr, and otherwise suppress the message.
Jeff
- Navigate by Date:
- Prev:
Systems that use EPICS: Design papers? Brian Glendenning
- Next:
DELETE [email protected] William Spengler
- 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:
S_errno_ENOBUFS Pete Jemian
- Next:
Bus errors? SIBLEY
- 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·