After upgrade to 3.2 one of my container not start
from console:
# vzctl start 501
Starting container ...
Container is mounted
Adding IP address(es): 192.168.251.105
Setting CPU units: 1000
Setting CPUs: 2
/bin/bash: line 508: 31 Segmentation fault which resolvconf > /dev/null 2>&1
~#...
i quote from http://www.lowendbox.com/blog/reduce...i-thread-apps/
Just a small tips for those trying to run multiple threaded applications on OpenVZ.
Personally I code quite a few multi-threaded applications in Python (as some things are just too hard to do asynchronisely). Very often a 6MB...
I found this
http://www.lowendbox.com/blog/reduce-stack-limit-for-multi-thread-apps/
and the command
ulimit -s 256
after start apache resolve the problem.
But if is a problem with multiple threaded applications on OpenVZ, can occur with other program.
by
michele
I have upgrade to Proxmox VE 1.8. The old virtual machine (OpenVZ container) works fine.
But if i create a new OpenVZ container with the same model (ubuntu 8.04 standard), the apache2 server use about 400 M ram by default.
My configuration is:
proxmox1:~# pveversion -v
pve-manager: 1.8-15...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.