# echo "maxuprc/D" | adb -k /dev/ksyms /dev/mem
physmem 1f3415
maxuprc:
maxuprc: 29995

# isainfo -kv
64-bit sparcv9 kernel modules

# swap -s
total: 4384192k bytes allocated + 1722416k reserved = 6106608k used, 37170768k available

No, I was wrong, I am not maxing out at 300 processes.

The message occurs when I try to start another PeopleSoft App. I currently have 5 PeopleSoft Application running. I get the fork errors when I try to start the 6th one. So, to get around it, I shut off one of the PeopleSoft App to start another one. I want to start all 6. Soon, I will need to add 5 more Apps. I ran 5 oracle database with 10 Peoplesoft App one time on a 4G mem system. There was no problem. I did not get this fork error with the 4G system. Therefore, I think it has something to do with the system, not letting me using more than 8G. Maybe some sort of parameters or something is wrong. When you upgrade your system memory, all you do is manually add the physical memory into the box right? No need to configure anything special right? I believe the box will automatically detect the memory and let you use it, correct? But, even before we upgrade to 16G, the box never really used all of the previous 8G of memory. It always get to around 7 to 7 ½ G.

There is no message on the system console. I only get the message when I try to start my PeopleSoft processes. The system does not freeze or anything. Just fork error and system continues to run. Does not matter what user you are logged in as.


I ran these right after the fork error:

Code:

psoft:fshw > vmstat 1 5
 procs     memory            page            disk          faults      cpu
 r b w   swap  free  re  mf pi po fr de sr m0 m1 m2 m3   in   sy   cs us sy id
 0 0 0 37946976 11757256 112 422 311 4 1 0 0 0 0  1  0 1102 4396 1193  6  2 92
 0 0 0 37073088 10833640 14 510 0 0 0 0  0  0  0  0  0 1782 37611 1839 18 3 79
 0 1 0 37069600 10830040 42 670 0 0 0 0  0  0  0  0  0 5293 8597 2602 32  7 61
 1 1 0 37069280 10829704 114 653 0 0 0 0 0  0  0  0  0 5950 18070 6655 31 7 62
 0 0 0 37069480 10829848 0 0 0  0  0  0  0  0  0  0  0 1839 2007 1246 18  6 75

psoft:fshw > kstat -p "cpu_stat:0:cpu_stat0:procovf"
cpu_stat:0:cpu_stat0:procovf    0

psoft:fshw > echo "fork_fail_pending/D" | adb -k /dev/ksyms /dev/mem
Cannot adb -k: cannot open /dev/kmem


psoft:fshw > grep swap /etc/vfstab
/dev/md/dsk/d5  -       -       swap    -       no      -
/dev/dsk/c1t1d0s1       -       -       swap    -       no      -
/dev/dsk/c1t2d0s1       -       -       swap    -       no      -
/dev/dsk/c1t4d0s1       -       -       swap    -       no      -
#/dev/dsk/c1t5d0s1      -       -       swap    -       no      -
swap    -       /tmp    tmpfs   -       yes     -

psoft:fshw > df -k /tmp
Filesystem            kbytes    used   avail capacity  Mounted on
swap                 37067824      72 37067752     1%    /tmp

psoft:fshw > swap -l
swapfile             dev  swaplo blocks   free
/dev/md/dsk/d5      85,5      16 8395184 8395184
/dev/dsk/c1t1d0s1   118,17     16 16780208 16780208
/dev/dsk/c1t2d0s1   118,1      16 16780208 16780208
/dev/dsk/c1t4d0s1   118,41     16 16780208 16780208

I don't think the problem is swap related.


Here is the error message:

Booting admin processes ...

exec BBL -A :
Failed.

tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler

exec tmshutdown -y

Shutting down all admin and server processes in /opt/psoft/ftst/appserv/fshw/PSTUXCFG

tmshutdown: internal error: CMDTUX_CAT:764: ERROR: can't attach to BB


tmboot: CMDTUX_CAT:828: ERROR: Cannot create error process - fork() failed

One thing that I can try is to use some sort of application that uses a lot of memory and test my machine memory. Do you know of any sample/test application that does this?



Thanks