Re: Buffer problems

[Andrew Johnson <anj@aps.anl.gov>]

Mark Rivers wrote:
> At least 2 IOCs at Brookhaven, on the same subnet, just got lots of the
> following errors:
>
> iocx17b2> ../online_notify.c: CA beacon (send to "130.199.193.255:5065")
> error was "S_errno_ENOBUFS"

> So this looks OK?  Is there something else I should check?  Clearly
> something is going on on the network there that is causing these
> problems.

There are two different kinds of network buffers in vxWorks that can run 
out.  In Tornado 2.x mbufShow() is a synonym for netStackDataPoolShow() 
which shows the buffers used by the IP stack for data packets.  There is 
another command netStackSysPoolShow() which is shows the state of the 
system buffer pool - these buffers are used for the ARP cache, routing 
tables and other system storage associated with the network.

However in the above case you might find there's nothing wrong with these 
buffers either.  I'm not quite sure what causes ENOBUFS errors when 
sending CA beacons; I have seen similar errors on IOCs here that have 
never run out of DataPool or SysPool buffers, and I don't yet know what 
they're complaining about (any ideas Jeff?).  They do appear to be benign 
though, if my memory is correct - the loss of a beacon can cause some 
unnecessary CA searches to occur, but nothing should break.

- Andrew
--
Dear God, I didn't think orange went with purple until I saw
the sunset you made last night.  That was really cool. - Caro