OpenVZ Forum: Support » fork: Cannot allocate memory

Home » General » Support » fork: Cannot allocate memory

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

fork: Cannot allocate memory [message #49038]

Fri, 01 March 2013 22:10

gorgi_selkov
Messages: 5
Registered: March 2013

Junior Member

Hi,

Is there any way to fix this stuff? I'm getting this error on my VPS - /etc/motd_dyn: fork: Cannot allocate memory

Please help me.

Regards,
George

Report message to a moderator

Re: fork: Cannot allocate memory [message #49039 is a reply to message #49038]

Sun, 03 March 2013 09:43

amissus
Messages: 21
Registered: November 2011
Location: Czech Republic - Ostrava

Junior Member

Probably resource shortage.

What about output of
cat /proc/user_beancounters or
cat /proc/bc/[ctid]/resources
or vzubc [ctid] command? Focus on column fail counts.

Simmilar issue here
http://forum.openvz.org/index.php?t=msg&goto=9094&

[Updated on: Sun, 03 March 2013 09:44]

Report message to a moderator

Re: fork: Cannot allocate memory [message #49040 is a reply to message #49039]

Sun, 03 March 2013 10:16

gorgi_selkov
Messages: 5
Registered: March 2013

Junior Member

cat /proc/user_beancounters:

root@popularno:~# cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
1416: kmemsize 53614111 62537728 88080384 100663296 0
lockedpages 0 8 4096 4096 0
privvmpages 233037 327680 262144 327680 1890103
shmpages 1072 2368 262144 262144 0
dummy 0 0 0 0 0
numproc 192 240 1024 1024 0
physpages 158317 262108 0 262144 0
vmguarpages 0 0 262144 262144 0
oomguarpages 133555 227146 262144 262144 0
numtcpsock 26 286 4096 4096 0
numflock 7 8 4096 4096 0
numpty 1 5 16 16 0
numsiginfo 0 27 4096 4096 0
tcpsndbuf 567328 2820456 14680064 16777216 0
tcprcvbuf 425984 1993072 14680064 16777216 0
othersockbuf 1253352 1914680 14680064 16777216 0
dgramrcvbuf 0 9248 14680064 16777216 0
numothersock 584 638 4096 4096 0
dcachesize 33552215 33554432 29360128 33554432 0
numfile 4493 4945 16384 16384 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 24 24 4096 4096 0
root@popularno:~#

--------------------------------------------------

the others shows

root@popularno:~# cat /proc/bc/[ctid]/resources
cat: /proc/bc/[ctid]/resources: No such file or directory

root@popularno:~# vzubc [ctid]
-bash: vzubc: command not found

Report message to a moderator

Re: fork: Cannot allocate memory [message #49041 is a reply to message #49038]

Sun, 03 March 2013 10:19

gorgi_selkov
Messages: 5
Registered: March 2013

Junior Member

this is newest:

Version: 2.5
uid resource held maxheld barrier limit failcnt
1416: kmemsize 57459734 62537728 8 8080384 100663296 0
lockedpages 0 8 4096 4096 0
privvmpages 326529 327680 262144 327680 1891685
shmpages 1072 2368 262144 262144 0
dummy 0 0 0 0 0
numproc 203 240 1024 1024 0
physpages 196693 262108 0 262144 0
vmguarpages 0 0 262144 262144 0
oomguarpages 170924 227146 262144 262144 0
numtcpsock 35 286 4096 4096 0
numflock 7 8 4096 4096 0
numpty 1 5 16 16 0
numsiginfo 0 27 4096 4096 0
tcpsndbuf 1364216 2820456 1 4680064 16777216 0
tcprcvbuf 573440 1993072 1 4680064 16777216 0
othersockbuf 1250792 1914680 1 4680064 16777216 0
dgramrcvbuf 0 9248 1 4680064 16777216 0
numothersock 580 638 4096 4096 0
dcachesize 33551386 33554432 2 9360128 33554432 0
numfile 4515 4945 16384 16384 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 24 24 4096 4096 0
root@popularno:~# cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
1416: kmemsize 57284486 62537728 8 8080384 100663296 0
lockedpages 0 8 4096 4096 0
privvmpages 327230 327680 262144 327680 1891745
shmpages 1072 2368 262144 262144 0
dummy 0 0 0 0 0
numproc 203 240 1024 1024 0
physpages 202365 262108 0 262144 0
vmguarpages 0 0 262144 262144 0
oomguarpages 176637 227146 262144 262144 0
numtcpsock 25 286 4096 4096 0
numflock 7 8 4096 4096 0
numpty 1 5 16 16 0
numsiginfo 0 27 4096 4096 0
tcpsndbuf 711736 2820456 1 4680064 16777216 0
tcprcvbuf 409600 1993072 1 4680064 16777216 0
othersockbuf 1250792 1914680 1 4680064 16777216 0
dgramrcvbuf 0 9248 1 4680064 16777216 0
numothersock 580 638 4096 4096 0
dcachesize 33551469 33554432 2 9360128 33554432 0
numfile 4506 4945 16384 16384 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 24 24 4096 4096 0

Report message to a moderator

Re: fork: Cannot allocate memory [message #49042 is a reply to message #49038]

Sun, 03 March 2013 11:17

amissus
Messages: 21
Registered: November 2011
Location: Czech Republic - Ostrava

Junior Member

privvmpages 233037 327680 262144 327680 1890103
// last column shows failures count of row parameter (privvmpages), as you can see, there is large number indicating insufficient memory. Everytime, when this resource is not enough, it increments failure counter. Your container is really insufficient with privvmpages.
Post your CT config file, what OpenVZ kernel are you using?

[Updated on: Sun, 03 March 2013 11:19]

Report message to a moderator

Re: fork: Cannot allocate memory [message #49047 is a reply to message #49042]

Mon, 04 March 2013 14:33

gorgi_selkov
Messages: 5
Registered: March 2013

Junior Member

I'm hosting in Hosting24, they do not allow using of CT file, and this is what I received as an answer about the kernel version: OpenVZ operating system-level virtualization technology.

Is there any way to fix this stuff?

Report message to a moderator

Re: fork: Cannot allocate memory [message #49048 is a reply to message #49047]

Mon, 04 March 2013 14:46

gorgi_selkov
Messages: 5
Registered: March 2013

Junior Member

LATEST REPORT

root@popularno:~# cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
1416: kmemsize 52942742 62537728 88080384 100663296 0
lockedpages 0 8 4096 4096 0
privvmpages 221954 327680 262144 327680 3055192
shmpages 1072 2368 262144 262144 0
dummy 0 0 0 0 0
numproc 188 246 1024 1024 0
physpages 152776 262181 0 262144 0
vmguarpages 0 0 262144 262144 0
oomguarpages 132589 227146 262144 262144 0
numtcpsock 19 286 4096 4096 0
numflock 7 8 4096 4096 0
numpty 1 5 16 16 0
numsiginfo 0 30 4096 4096 0
tcpsndbuf 347016 2820456 14680064 16777216 0
tcprcvbuf 311296 1993072 14680064 16777216 0
othersockbuf 1250792 1914680 14680064 16777216 0
dgramrcvbuf 0 9248 14680064 16777216 0
numothersock 580 641 4096 4096 0
dcachesize 33553073 33554432 29360128 33554432 0
numfile 4486 4945 16384 16384 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 24 24 4096 4096 0
root@popularno:~#

Report message to a moderator

Re: fork: Cannot allocate memory [message #49049 is a reply to message #49038]

Mon, 04 March 2013 17:47

amissus
Messages: 21
Registered: November 2011
Location: Czech Republic - Ostrava

Junior Member

Your container encounters memory insufficiency.
Consult it with your VPS provider, when you have not access to hardware node.

Report message to a moderator

Previous Topic:	Vzdump all container in backup hard disk
Next Topic:	CentOS OpenVZ & IP routing

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Nov 08 18:12:25 GMT 2024

Total time taken to generate the page: 0.03345 seconds