![]() |
![]() ![]()
Experimental Physics and
| ||||||||||||||
|
Over the weekend we received these error messages from an mv5500 running vxworks 5.5 and epics 3.14.6. As far as I can tell this is an ENOBUFS error. Is this the correct interpretation? CAS: UDP send to "131.225.231.247:35139" failed because "errno = 0x37" CAS: UDP send to "131.225.231.247:35139" failed because "errno = 0x37" ../online_notify.c: CA beacon (send to "131.225.231.255:5065") error was "errno = 0x37" CAS: UDP send to "131.225.231.247:35139" failed because "errno = 0x37" CAS: UDP send to "131.225.231.65:33655" failed because "errno = 0x37" CAS: UDP send to "131.225.231.65:33655" failed because "errno = 0x37" CAS: UDP send to "131.225.231.65:33655" failed because "errno = 0x37" CAS: UDP send to "131.225.231.247:35139" failed because "errno = 0x37" CAS: UDP send to "131.225.231.247:35139" failed because "errno = 0x37" CAS: UDP send to "131.225.231.247:35139" failed because "errno = 0x37" CAS: UDP send to "131.225.231.65:33655" failed because "errno = 0x37" CAS: UDP send to "131.225.231.65:33655" failed because "errno = 0x37" CAS: UDP send to "131.225.231.65:33655" failed because "errno = 0x37" CAS: UDP send to "131.225.231.247:35139" failed because "errno = 0x37" What buffer needs to overflow to get this error? I thought the only UDP messages from an IOC were beacons to port 5065. What are the other UDP messages to ports other than 5065? Could this indicate a problem somewhere else on our network? Thanks, Geoff
| ||||||||||||||
ANJ, 02 Sep 2010 |
![]() · Download · Search · IRMIS · Talk · Documents · Links · Licensing · |