[ On Saturday, June 23, 2001 at 20:22:01 (+0200), wojtek@wojtek.3miasto.net wrote: ]
> Subject: no buffer space available
>
> what could cause this?
> only restarting pppd fixed it.
> 
> Jun 23 07:13:02 xxx named[75]: ns_forw: sendto([217.96.12.60].53): No
> buffer space available
> Jun 23 07:43:02 xxx named[75]: ns_forw: sendto([217.96.12.60].53): No 
> buffer space available
> Jun 23 08:13:02 xxx named[75]: ns_forw: sendto([217.96.12.60].53): No
> buffer space available
> Jun 23 08:43:02 xxx named[75]: ns_forw: sendto([217.96.12.60].53): No
> buffer space available
> Jun 23 09:13:02 xxx named[75]: ns_forw: sendto([217.96.12.60].53): No
> buffer space available
> Jun 23 09:43:02 xxx named[75]: ns_forw: sendto([217.96.12.60].53): No
> buffer space available

I don't know, but when it happens to me it's usually my router/FW, and
it not named that complains but simply packets stop being routed (though
an attempt to ping on the router will result in the same "no buffer
space" error message).

Usually "ifconfig rtk0 down; sleep 600; ifconfig rtk0 up" or similar
(substitute which ever interface seems to be stuck) will fix it.....

In your example restarting pppd equivalently ifconfig's the interface
down and up again, IIRC.

-- 
							Greg A. Woods

+1 416 218-0098      VE3TCP      <gwoods@acm.org>     <woods@robohack.ca>
Planix, Inc. <woods@planix.com>;   Secrets of the Weird <woods@weird.com>