Search results

  1. M

    Segmentation fault after upgrade to proxmox 3.2

    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 ~#...
  2. M

    Proxmox VE 1.8 released!

    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...
  3. M

    Proxmox VE 1.8 released!

    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
  4. M

    Proxmox VE 1.8 released!

    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...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!