[j-nsp] Resource Temporarily Unavailable - Juniper MX

Alexandre Snarskii snar at snar.spb.ru
Mon Dec 5 10:08:41 EST 2011


On Mon, Dec 05, 2011 at 07:48:22AM -0500, Paul Stewart wrote:
> Can anyone shed some light on these log messages?
> 
>  
> 
> Nov 30 04:48:21  core2.toronto1 rpd[1359]: bgp_send: sending 19 bytes to
> xx.xxx.52.50 (External AS xxxxx) blocked (no spooling requested): Resource
> temporarily unavailable
> 
> We get these every so often .. Presuming it has to due with load on the
> system for a short period of time?

More possibly it's caused by remote system load (or link congestion
or whatever other reason for remote system not able to receive updates
fast enough). Then, when socket buffer is full with unacknowledged data,
your system tries to send another update/keepalive message and it 
results in write(2) syscall returning EAGAIN error (actually, not
an error, just and indication of 'no data sent, try again later'),
which translates to "Resource temporarily unavailable" message. 

> 
> Platform is Juniper MX boxes running 10.0R3.10
> 
>  
> 
> Thanks,
> 
>  
> 
> Paul
> 
>  
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

-- 
In theory, there is no difference between theory and practice. 
But, in practice, there is. 



More information about the juniper-nsp mailing list