migrated container missing from web interface list

lp86

Member
Mar 3, 2010
58
0
6
Ohio
www.ohiointernet.net
I moved a OpenVZ container from a CentOS based OpenVZ system to proxmox, I can see it if I run "vzlist", but it doesn't show up in the web interface. Is there something I need to do? (I restarted the vz, pvedaemon, apache2 services already)
 
did you followed this howto?
 
Yes, that is one of the first things I looked at. I just checked again, I had the setting as "pve-auto", its supposed to be "pve.auto". It is still not showing up in the web interface list. I restarted vz & pvedaemon again just to be sure (after the pve-auto/pve.auto change)

Here is the 101.conf file

Code:
ONBOOT="yes"


# UBC parameters (in form of barrier:limit)
# Primary parameters
AVNUMPROC="450:450"
NUMPROC="800:800"
NUMTCPSOCK="1600:1600"
NUMOTHERSOCK="1600:1600"
VMGUARPAGES="1836000:2147483647"
# Secondary parameters
KMEMSIZE="36877434:40565177"
TCPSNDBUF="5738878:12292478"
TCPRCVBUF="5738878:12292478"
OTHERSOCKBUF="2869439:9423039"
DGRAMRCVBUF="2869439:2869439"
OOMGUARPAGES="154623:2147483647"
# Auxiliary parameters
LOCKEDPAGES="1800:1800"
SHMPAGES="15462:15462"
PRIVVMPAGES="2000000:2500000"
NUMFILE="14400:14400"
NUMFLOCK="1000:1100"
NUMPTY="160:160"
NUMSIGINFO="1024:1024"
DCACHESIZE="8052815:8294400"


PHYSPAGES="0:2147483647"
NUMIPTENT="20000:20000"


# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="471353358:510632804"
DISKINODES="27301316:30031448"
QUOTATIME="0"
DISK_QUOTA=yes
QUOTAUGIDLIMIT="10000"


# CPU fair sheduler parameter
CPUUNITS="125000"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
OSTEMPLATE="sausalito-5-blueonyx_5106R-5.6-OhioInternet-06102011_i386"
ORIGIN_SAMPLE="pve.auto"
IP_ADDRESS="xxx.xxx.xxx.xxx"
HOSTNAME="srv.domain.tld"
NAMESERVER="8.8.8.8 8.8.4.4"
 
bingo!

This was the problem

ERROR: unable to parse config line: DISK_QUOTA=yes#012

-----
DISK_QUOTA=yes
-----
I added quotes to yes, and that fixed it
-----
DISK_QUOTA="yes"
-----

The settings were all screwey, the machine had 7mb ram allocated and 7162 mb of swap. had 449.6 GB of disk space. All easily fixed fortunately.
 

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!