Thanks to all the folks who replied. I received many suggestions:
Set vm-swap-eager = 0
Run sys_check and fix errors that it reports
Set max-proc-per-user =1024 (or greater - ours is set at 2048)
Check the shared memory and semophores
Check the limits on the account running Tuxedo with ulimit -a
Increase task-max
Increase maxusers in /sys/conf/HOSTNAME to increase maxuproc
A couple of folks explained the fork() errors to me and pointed out that
Tuxedo SHOULD return an error code since fork() can fail for two different
reasons.
What I Did:
Well, I shotgunned it, since obtaining reboots is difficult. sys_check
reported vm-page-free-target was less than vm-page-free-optimal. Increased
vm-page-free-target=1024 as recommended. Set vm-swap-eager=0. Set the
values of msg-mni=128, sem-mni-32, and sem-msl=200 (these match settings on
our other servers). Then I rebooted. After rebooting I ran vmstat and just
for fun ran swapon -s. To my great consternation it returned NO swap
configured. <smack> Added the swap partition I thought was configured out
of the box, and told the DBAs to give it a try. Problem is now solved. I
never ran swapon before rebooting and apparently did not properly read the
vmstat.
Thanks to:
Tom Devine
Walter North
Mike Fulce
Oisin McGuinness
Dr. Thomas Blinn
"Alan"
Hajnik Ferenc
Cy Dewhurst
Thanks to you all, once again
Bill
> -----Original Message-----
> From: Skulley, William [SMTP:William.Skulley_at_rfets.gov]
> Sent: Tuesday, February 06, 2001 1:25 PM
> To: 'tru64-unix-managers_at_ornl.gov'
> Subject: System Resources Question
>
> This may be slightly off topic, so apologies ahead of time.
>
> OS is Tru64 5.0a, PK2. Hardware is an ES40. 2GB of RAM, almost 6GB of
> swap
>
> We are running PeopleSoft on this server and the DBAs are reporting an
> error
> in Tuxedo:
>
> 828: ERROR: Cannot create error process - fork() failed
>
> The Tuxedo Documentation says:
>
> 828
> ERROR: Cannot create error process - fork(failed)
>
> Description:
> The system, in trying to initiate the user error handler, could not fork a
> new process (the fork() system call returns -1).
>
> Action:
> This error is directly related to system resources (too many processes,
> lack
> of swap space, etc). Consult your UNIX system administrator for
> appropriate
> actions.
>
> So they have contacted me. The number of processes does not appear to be
> anywhere close max-proc-per-user (set at 512), swap space appears to be
> fine. Assuming I know nothing (fairly close to true), how would I attempt
> to troubleshoot this problem? I look at that error documentation and
> don't
> see enough information to solve the problem? Anyone seen and worked
> through
> this?
>
> Thanks
> Bill Skulley
> DynCorp I&ET
Received on Wed Feb 07 2001 - 14:28:52 NZDT