VM Container not showing up after creation

[Richard Reijmers]

After creating a Container VM with a precreated template (

debian-6.0-standard_6.0-4_i386.tar.gz) it doesn't show up in the list of VM's.

Another post on this forum was about the same problem, but with a KVM VM.

Installing a KVM VM is not an issue for me.

After installing a CT VM I can see the CT with vzlist -a, but not in the WebInterface.
The CT is fully functional.

Tried rebooting the VM and the Host itself, but it did not result in showing the additional CT VM.

Earlier created CT VM's are in my list, so it has been working previously.

​

[TABLE="class: normal, width: 0"]
[TR]
[TD="align: left"]Version (package/version/build)[/TD]
[TD="align: left"]pve-manager/1.9/6542[/TD]
[/TR]
[TR="bgcolor: #EDEDED"]
[TD="align: left"]Kernel Version[/TD]
[TD="align: left"]Linux 2.6.32-6-pve #1 SMP Tue Sep 13 10:44:10 CEST 2011[/TD]
[/TR]
[/TABLE]

Any help greatly appreciated!

 

[dietmar]

Any hint in /var/log/syslog?

 

[Richard Reijmers]

Hi Dietmar,

That was enough for me to fix the problem.
Here are my findings:
# tail -f /var/log/syslog
Feb 10 13:20:57 proxmox pvedaemon[2176]: ERROR: unable to parse config line: FIREWALL="#012
# grep -lir 'FIREWALL' /etc/vz/
/etc/vz/conf/211.conf
# cat 211.conf
..
..
..
..
FIREWALL="
# Allow access to PostgreSQL port only from release.prod
# and release.test machines. You may use domain names here.
[5432]
10.0.2.203
10.0.2.213
"

It wasn't liking that, so removed it, tested my PostgreSQL server, which still worked fine, even the IP restriction, which I probable put somewhere else as well and this must've been old.
Tested the ProxMox CT creating process and it worked like a charm again.

Many thanks for pointing me in the right direction!

Richard