Anybody know what "sendmail[848]: NOQUEUE: SYSERR(root): getrequests: accept: No buffer spac

[Ben_31]

sendmail[848]: NOQUEUE: SYSERR(root): getrequests: accept: No buffer space available

Shows up in syslog.
Huh? The box has plenty of RAM and Disk Space...

What up?

[Michael Tully]

Check the available space in /var

[Sridhar Bhaskarla]

I would be looking for swap space.

Do a "swapinfo -tm" and look at the total column. If it is around 100%, then your system is out of virtual memory.

-Sri

[Jeff Schussele · Accepted solution]

Hi Ben,

Check these previous posts:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x4ebf50dde50cd71190050090279cd0f9,00.html

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xaa36c4c76f92d611abdb0090277a778c,00.html

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc97742308663d611abdb0090277a778c,00.html

I found all these searching the forum with
"getrequests: accept: No buffer space available"

HTH,
Jeff

[Sridhar Bhaskarla]

Hi Ben,

Since you found the solution in one of those links that have many messages, can you post what exactly you found here so that it will help others in future?.

No buffer space a.k.a ENOBUFS error is very misleading and most of the times we found that it has nothing to do with networking configuration as such.

In your case, it could be that you were running out of uproc/nproc parameter or insufficient swap reservation pool etc., that might have caused sendmail not to respond within the tolerating limits of the client.

So, we would appreciate if you can post what you found it. I am particularly tracking these incidents.

Thanks,
Sri

[Jeff Schussele]

Hi (again) Ben,

My esteemed colleaugue brings up a very good point - we're all curious - which was it?
ENOBUFS is a very slippery character - please clue us in.

No points please,
Jeff