bob@acornrc.UUCP (Bob Weissman) (04/07/88)
Lately, on a Vax 11/750 running 4.2bsd, we've been getting ENOBUFS
errors ("No buffer space available") when users attempt to connect
to another Ethernet site via rlogin, rsh, etc.
I've been unable to track down the source of this error, and have
found that rebooting the Vax makes thinks OK again for a couple of
days. None of our other hosts have this problem.
I'd like to find a more gentle way to fix this problem. Can
anyone help?
Thanks,
--
Bob Weissman
Internet: bob@acornrc.uucp
UUCP: ...!{ ames | decwrl | oliveb | apple }!acornrc!bob
Arpanet: bob%acornrc.uucp@ames.arc.nasa.govchris@mimsy.UUCP (Chris Torek) (04/07/88)
In article <699@acornrc.UUCP>, bob@acornrc.UUCP (Bob Weissman) writes: >Lately, on a Vax 11/750 running 4.2bsd, we've been getting ENOBUFS >errors ("No buffer space available") .... If these occur on connections that go over an `IMP' (anything that you configure with `ifconfig imp0 ...' [or imp1, etc.]), the problem is most likely the IMP message queue size bug. This and a whole raft of other bugs (numbering in the *hundreds*) are fixed in 4.3BSD. If that is not it, run `netstat -m' to see whether it really is running out of mbufs (`%d requests for memory denied' should always be `0'). -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163) Domain: chris@mimsy.umd.edu Path: uunet!mimsy!chris