openssh bugs - Nov 2005 - [Bug 1127] fork: Resource temporarily unavailable

http://bugzilla.mindrot.org/show_bug.cgi?id=1127

           Summary: fork: Resource temporarily unavailable
           Product: Portable OpenSSH
           Version: 4.2p1
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P1
         Component: sshd
        AssignedTo: bitbucket at mindrot.org
        ReportedBy: avinashr at gmail.com


We have a production running openssh using 3.8.1p1 openssh version. I had
noticed by "googling" that this issue was also present in 4.2p1. We
have
noticed that many times the ssh server complains in the Event Viewer log as
follows:
Fork: Resource temporarily unavailable.

This issue goes away (atleast for sometime) when the service is restarted. We
have many systems in production already using this service and this could be a
potential issue for us.

I have not noticed any issue with memory consumption whatsoever on the machine.

I have attached the log from the event viewer:

Event Type:     Error
Event Source:   sshd
Event Category: None
Event ID:       0
Date:           8/17/2005
Time:           2:35:40 PM
User:           NT AUTHORITY\SYSTEM
Computer:       400T-0940881
Description:
The description for Event ID ( 0 ) in Source ( sshd ) cannot be found. The
local computer may not have the necessary registry information or message DLL
files to display messages from a remote computer. The following information is
part of the event: sshd : PID 836 : error: fork: Resource temporarily
unavailable.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1127


avinashr at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |major






------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1127





------- Comment #1 from dtucker at zip.com.au  2005-12-14 00:41 -------
It might not be memory, it might be some other limit (eg processes).  How many
processes do you have running (not just sshd's) when you see the failure?

I don't know how Cygwin's ulimits interact with whatever Windows does
natively,
but "ulimit -a" gives me a "max user processes" limit of 63.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.