HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

The fork function failed. There is not enough memory available

 
SOLVED
Go to solution
DnD_1
Regular Advisor

The fork function failed. There is not enough memory available

I can see that memory is full.


# swapinfo -tam
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev - - - - -1 - 0 /dev/vg00/lvol3 disabled
reserve - 0 0
memory 1577 1558 19 99%
total 1577 1558 19 99% - 0 -

How do I extend the memory though ? Please help ...

Many thanks !
15 REPLIES
Johnson Punniyalingam
Honored Contributor
Solution

Re: The fork function failed. There is not enough memory available

>>dev - - - - -1 - 0 /dev/vg00/lvol3 disabled<<

may i know why does your swap space has been disabled
Problems are common to all, but attitude makes the difference
DnD_1
Regular Advisor

Re: The fork function failed. There is not enough memory available

I have no idea why it became disabled.

The server rebooted due to some issue.

How to I proceed ?
Johnson Punniyalingam
Honored Contributor

Re: The fork function failed. There is not enough memory available

I suspect -its because of "/dev/vg00/lvol3 disable" the server rebooted.

please post the below outputs to advice / suggestions

# more /etc/shutdownlog
# bdf
# vgdisplay -v /dev/vg00 |more

if possible can you check the /var/adm/syslog/OLDSyslog.log
Problems are common to all, but attitude makes the difference
Johnson Punniyalingam
Honored Contributor

Re: The fork function failed. There is not enough memory available

we need to check with "lvol3" have any "disk problem ?
Problems are common to all, but attitude makes the difference
DnD_1
Regular Advisor

Re: The fork function failed. There is not enough memory available

Hi..

the info,

# more /etc/shutdownlog

14:54 Wed Dec 9, 2009. Reboot: (by may1!root)
17:11 Wed Dec 9, 2009. Reboot: (by may1!oraelr)
08:26 Thu Dec 10, 2009. Reboot: (by may1!root)


# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 212992 135912 76656 64% /
/dev/vg00/lvol1 298928 64224 204808 24% /stand
/dev/vg00/lvol8 4718592 1481216 3212232 32% /var
/dev/vg00/lvol7 2244608 1320864 916576 59% /usr
/dev/vg00/lvol4 3080192 6736 3053416 0% /tmp
/dev/vg00/lvol6 2736128 1561984 1165032 57% /opt
/dev/vg00/lvol5 32768 8048 24576 25% /home
/dev/vg00/lvol2 52428800 43180651 8679824 83% /may/opt
/dev/vg01/lvdb 2129920000 2043599484 80925505 96% /db
/dev/vg00/lvol9 5128192 3809634 1236167 76% /may/oracle

--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 11
Open LV 10
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 4384
VGDA 4
PE Size (Mbytes) 16
Total PE 8748
Alloc PE 5966
Free PE 2782
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 304
Current LE 19
Allocated PE 38
Used PV 2

LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 51200
Current LE 3200
Allocated PE 3200
Used PV 2

LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 208
Current LE 13
Allocated PE 26
Used PV 2

LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 3008
Current LE 188
Allocated PE 376
Used PV 2

LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 32
Current LE 2
Allocated PE 4
Used PV 2

LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 2672
Current LE 167
Allocated PE 334
Used PV 2

LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 2192
Current LE 137
Allocated PE 274
Used PV 2

LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 4608
Current LE 288
Allocated PE 576
Used PV 2

LV Name /dev/vg00/lvol9
LV Status available/syncd
LV Size (Mbytes) 5008
Current LE 313
Allocated PE 626
Used PV 2

LV Name /dev/vg00/lvol0
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 256
Allocated PE 256
Used PV 2


--- Physical volumes ---
PV Name /dev/dsk/c2t1d0
PV Status available
Total PE 4374
Free PE 0
Autoswitch On

PV Name /dev/dsk/c3t0d0
PV Status available
Total PE 4374
Free PE 2782
Autoswitch On

And the syslog show something like this,

Dec 10 07:37:42 may above message repeats 7 times
Dec 10 07:37:58 may prngd[2015]: Could not fork: Not enough space
Dec 10 07:40:00 may ftcd[5425]: Unable to reserve process start-up resource
Dec 10 07:57:31 may prngd[2015]: Could not fork: Not enough space
Dec 10 07:57:42 may above message repeats 23 times
Dec 10 07:55:00 may ftcd[5425]: Unable to reserve process start-up resource
Dec 10 07:57:42 may above message repeats 7 times
Dec 10 07:58:22 may prngd[2015]: Could not fork: Not enough space
Dec 10 07:59:00 may ftcd[5425]: Unable to reserve process start-up resource
Dec 10 08:17:04 may prngd[2015]: Could not fork: Not enough space
Dec 10 08:17:42 may above message repeats 22 times
Dec 10 08:15:01 may ftcd[5425]: Unable to reserve process start-up resource
Dec 10 08:17:42 may above message repeats 8 times
Dec 10 08:17:55 may prngd[2015]: Could not fork: Not enough space
Dec 10 08:20:00 may ftcd[5425]: Unable to reserve process start-up resource
Dec 10 08:26:25 may prngd[2015]: Could not fork: Not enough space
Dec 10 08:26:33 may above message repeats 10 times
Dec 10 08:25:00 may ftcd[5425]: Unable to reserve process start-up resource
Dec 10 08:26:33 may above message repeats 3 times
Dec 10 08:26:33 may syslogd: going down on signal 15
Johnson Punniyalingam
Honored Contributor

Re: The fork function failed. There is not enough memory available

# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 212992 135912 76656 64% /

suspect some have tried to configure

/dev/vg00/lvol3 -> has swap device resulted in System reboot, because lvol3 is ment for / file system

can you please check , any one write to do ?
Problems are common to all, but attitude makes the difference
DnD_1
Regular Advisor

Re: The fork function failed. There is not enough memory available

hi..

no one done anything, the server reboot by me to removed some unused LUN.

since the issue now is the memory, wondering how do i extend those memory ? or enable the disabled lvol3 ? or any better solution ?

many thanks !!

Johnson Punniyalingam
Honored Contributor

Re: The fork function failed. There is not enough memory available

insufficient swap / or swap file system is missing thats why you do have error in syslog

Could not fork: Not enough space
Problems are common to all, but attitude makes the difference
Johnson Punniyalingam
Honored Contributor

Re: The fork function failed. There is not enough memory available

can you post the output

lvdisplay /dev/vg00/lvol2

more /etc/fstab

we need add back the swap space
Problems are common to all, but attitude makes the difference
DnD_1
Regular Advisor

Re: The fork function failed. There is not enough memory available

Info requested.

# lvdisplay /dev/vg00/lvol2
--- Logical volumes ---
LV Name /dev/vg00/lvol2
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 51200
Current LE 3200
Allocated PE 3200
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

# lvdisplay /dev/vg00/lvol3
--- Logical volumes ---
LV Name /dev/vg00/lvol3
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 208
Current LE 13
Allocated PE 26
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default

# more /etc/fstab
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /tmp vxfs delaylog 0 2
/dev/vg00/lvol5 /home vxfs delaylog 0 2
/dev/vg00/lvol6 /opt vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2
/dev/vg00/lvol9 /may/oracle vxfs largefiles 0 2
/dev/vg00/lvol2 /may/opt vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vgnetapp/lvdb /db vxfs largefiles 0 2

Johnson Punniyalingam
Honored Contributor

Re: The fork function failed. There is not enough memory available

may i know how much is your psyical size mememory ?

# dmesg |grep pshyical

usually we will create swap swap double the size

Problems are common to all, but attitude makes the difference
Johnson Punniyalingam
Honored Contributor

Re: The fork function failed. There is not enough memory available

# lvcreate -L 1024 -n lvol11 /dev/vg00


Use SAM to declare your new secondary swap or use the command line:

# swapon /dev/vg14/lvol15


Verify it has been added in "/etc/fstab" when using SAM, or add it manually when using the command line.

Example:
/dev/vg00/lvol11 . swap defaults 0 0



Configuration of Swap using SAM

SAM - Swap --> Actions --> Add Device Swap -> Add File System Swap...

point your /dev/vg00/lvol11 while reading the removed swap space.

finally check with swapinfo -mat
Problems are common to all, but attitude makes the difference
DnD_1
Regular Advisor

Re: The fork function failed. There is not enough memory available

physical page size = 4096 bytes, logical page size = 4096 bytes
Johnson Punniyalingam
Honored Contributor

Re: The fork function failed. There is not enough memory available

Ok,

create file system has mentioned above,
and Use SAM to declare has secondary swap space,

I hope some how the "primary swap" has been removed or damaged, we try to add the secondary space space ,

but to regain the "primary" swap . I hope you need to "Ignite Server" hence its Contigious

Problems are common to all, but attitude makes the difference
DnD_1
Regular Advisor

Re: The fork function failed. There is not enough memory available

Thanks...

I not quite sure how to do it, since I'm a dummies...so I let it be and ask others more HP experienced guys to do it... :D

let see what he going do...