Login Problem... URGENT please..

[Jonathan Caplette]

Hi guys,

I need a fast one from you!

At login, After the "Please wait...checking for disk quotas" message, which
usually pauses for less than a second, they get a message that says "could
not execute quota command" and it hangs for about ten minutes before
completing the login.

After login, when trying to execute an application, (such as elm)it says
"ksh: cannot fork: too many processes", then bounces back to a prompt.

thanks
Jonathan

[G. Vrijhoeven · Accepted solution]

Hi,

Looks like you have 1 a run away process on the machine or reached kernel parameter limits.

for kernel parameters look here:
http://docs.hp.com/hpux/onlinedocs/os/KCparams.OverviewAll.html
hope this will help

[A. Clay Stephenson]

Hi Jonathan:

You have too many processes running. You need to kill some processes, increase NPROC, and possibly increase swap.

[Thierry Poels_1]

Hi,

"too many processes":
either your "nproc" (and/or "maxuprc"!) kernal parameters is set too low, and should be increased. Or you have a program/script that is looping and too many creating subprocesses.

check nproc usage with "sar -v 5 5" and running processes with "ps -ef".

good luck,
Thierry.

[Roger Baptiste]

<< cannot="" ="" too="" many="" processes="">>

Your system has reached
the limit of maximum number
of processes it can run.
This limit can be increased
by changing the Kernel parameter - nproc .

Go into SAM, kernel configuration -> configurable parameters : and change maxusers , nproc.
(maxusers increase will automatically incrase nproc)

Note that this change will
need a Reboot of the box.

-raj

[Sanjay_6]

Hi Jonathan,

The error "cannot fork: too many processes" refers to a mxing out of a kernel parameter.

quote //

The most likely cause of this error is the kernal parameter, maxuprc, is set too low. The value of this parameter indicates the maximum number of processes which any one user can have running at one time. The default value is 64, which may to be too low with extensive use of Windows and/or background processes. Setting maxuprc to 128 (or larger) and rebuilding the kernal should fix this problem.

//unquote

There is a ksh patch too on this PHCO_18164 for 11.0 and PHCO_17691 for 10.20. Patch PHCO-18164 has been superceded by patch patch PHCO_22712.

hope this helps.

Regds

[Jonathan Caplette]

Ok.. thanks guys...

That's what I was thinking of... :)