Segmentation fault after upgrade to proxmox 3.2

micky10

New Member
Apr 15, 2011
4
0
1
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

~# vzctl enter 501
Container is not running

how to solve this problem ? thanks, bye
 

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!