I can not see more than 5 Containers in ProxMox

[xRay]

Hi

I can only see like 5 containers in Proxmox, if I list them on the console:

CTID NPROC STATUS IP_ADDR HOSTNAME
1101 12 running 192.168.0.160 dev-zimbra-01.x.y
1102 12 running 192.168.0.161 zz.x.y
1103 12 running 192.168.0.162 dev-asterisk-01.x.y
1104 15 running 192.168.0.163 nuxeo.x.y
1105 17 running 192.168.0.165 yy.x.y
1106 10 running 192.168.0.166 auth-01.x.y

You see that I have 6 containers, but proxmox only sees the first 5. I tried to restart apache and the proxmox daemon as well, all the same.

actually I have 7 containers, one not active (i use it only to create debian bootstrapped templates):
ray@pve01:/etc/vz/conf$ sudo vzlist -a
CTID NPROC STATUS IP_ADDR HOSTNAME
777 - stopped - -
1101 12 running 192.168.0.160 dev-zimbra-01.x.y
1102 12 running 192.168.0.161 zz.x.y
1103 12 running 192.168.0.162 dev-asterisk-01.x.y
1104 15 running 192.168.0.163 nuxeo.x.y
1105 17 running 192.168.0.165 yy.x.y
1106 10 running 192.168.0.166 auth-01.x.y

So, is this a *free* limit? Or a bug? I do not think it is supposed to be so. I use Proxmox 1.3

thanks,
Ray

 

[dietmar]

How did you create those containers - using the web interface?

 

[xRay]

Yep, i created the image manually, bootstrapping debian like you do with standard openvz.

i put the template in /var/lib/vz/templates/cache and created a virtual container with this template from the proxmox web interface ...

but in theory, should'nt it make no difference creating the container with vzcreate or use the web interface?

best

 

[dietmar]

but in theory, should'nt it make no difference creating the container with vzcreate or use the web interface?

You are right - I guess we have a bug in config file parser - is there a hint in the syslog?

 

[xRay]

seems you are right, i found these in the syslog:

Jul 14 12:50:33 pve01 pvedaemon[17951]: ERROR: unable to parse config line: OSTEMPLATE=debian-5.0#012


The Problem was that in the 777 vps, which I use to create templates, the quotes for OSTEMPLATE where missing.

I think it would be great if there's a config-parsing error that this error would as well be indicated in the webfront, and i think it should not stop searching for/loading the other templates, showing the template in the list and like, instead of the bars show the errormessage or an indicator with an popup for the error ...

It was not obvious for me to assume there is a parsing error and to look in the logs.

Thanks for the quick response,

Best regards,
Raimund