Web Hosting Talk : Web Hosting Main Forums : VPS Hosting : CT boot issues

[bomozah]

hello All ,,
i' trying to restart one of my vps user but it's wan't start

[root@vps2 log]# vzctl restart 180
Restarting container
Starting container ...
Container is unmounted
Container is mounted
Warning: NUMIPTENT 2:2 is less than minimally allowable value, set to 16:16
Adding IP address(es): 74.63.193.133 74.63.193.134
arpsend: 74.63.193.133 is detected on another computer : 00:09:b7:42:74:00
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 74.63.193.133 eth1 FAILED
arpsend: 74.63.193.134 is detected on another computer : 00:09:b7:42:74:00
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 74.63.193.134 eth1 FAILED
bash: fork: Cannot allocate memory
Setting CPU limit: 400
Setting CPU units: 1000
Setting CPUs: 4
Configure meminfo: 1572864
Set hostname: server.clinet.org
bash: fork: Cannot allocate memory
Container start in progress...
[root@vps2 log]#

[root@vps2 log]# vzctl enter 180
enter into CT 180 failed
Unable to get tty name: Bad file descriptor
Unable to fork: Cannot allocate memory
[root@vps2 log]#

The Ram on the node

[root@vps2 log]# free -m
             total       used       free     shared    buffers     cached
Mem:          7959       5596       2363          0        148       3961
-/+ buffers/cache:       1486       6473
Swap:         9983          0       9983
[root@vps2 log]#

any solution ?

Thank you

[waveweb]

it dosent seem to be a ram issue on the node, but on the VPS itself, try to increase the RAM on the VPS

if dosent work, can you paste the results of

cat /proc/user_beancounters

[Jacob Wall]

Basically, your resource limits are too low for your applications' demands when the vps is started up. Just do as waveweb already stated, up all aspects and see if it fixes itself.