newly installed VZ container won't start

  • Thread starter Thread starter infinity-tec
  • Start date Start date
I

infinity-tec

Guest
I'm running proxmox 1.3 since 2 years, never had a problem.
I have a windows server 2008 KVM and VZ template for wifi billing running.

Since I have to make major changes in my billing system I installed an other VZ template of the wifi billing system. But it wont start. The template starts for a few second and goes to mount.

I suspected a bad template and downloaded it again, but still the same, and it is the same template I have just running fine now.

maybe there is an issue with the system resources, how do I check?
Sorry I'm not the super guru on linux, please someone help.
 
see the log (see Adminstrator/Logs)

what template do you use?
 
I'm running this template "ubuntu-8.04-promesh.mx.5.1.0.final_8.04-1_i386.tar.gz" and I have it running once no problem on that proxmox server.

Where exactly do I have to go to get the right log? web interface or WinSCP

Thanks Thomas
 
I have tried to install other VZ templates with the same result, just wont start always to mount only.
 
again, see the logs and post it.
 
I created the container (1014) again and started here is the task log:

/usr/sbin/vzctl start 1014
Starting container ...
Container is mounted
Adding IP address(es): 10.10.0.14
Setting CPU units: 1000
Setting CPUs: 1
Configure meminfo: 262144
Set hostname: mx.mydomain.net
File resolv.conf was modified
Setting quota ugidlimit: 0
Container start in progress...
VM 1014 started

and here the syslog:
Jun 28 22:27:17 proxmox pvedaemon[9892]: creating new VM 1014 on node 0 (localhost)
Jun 28 22:27:42 proxmox proxwww[9918]: Starting new child 9918
Jun 28 22:27:44 proxmox proxwww[9919]: Starting new child 9919
Jun 28 22:27:44 proxmox proxwww[9920]: Starting new child 9920
Jun 28 22:28:47 proxmox proxwww[9949]: Starting new child 9949
Jun 28 22:28:52 proxmox proxwww[9951]: Starting new child 9951
Jun 28 22:29:25 proxmox pvedaemon[9892]: VM 1014 created
Jun 28 22:30:01 proxmox /USR/SBIN/CRON[10007]: (root) CMD (/usr/share/vzctl/scripts/vpsnetclean)
Jun 28 22:30:01 proxmox /USR/SBIN/CRON[10011]: (root) CMD (/usr/share/vzctl/scripts/vpsreboot)
Jun 28 22:30:01 proxmox /USR/SBIN/CRON[10010]: (root) CMD (test -x /usr/lib/atsar/atsa1 && /usr/lib/atsar/atsa1)
Jun 28 22:30:52 proxmox pvedaemon[10073]: starting VM 1014 on node 0 (localhost)
Jun 28 22:30:52 proxmox kernel: CT: 1014: started
Jun 28 22:30:53 proxmox pvedaemon[10073]: VM 1014 started
Jun 28 22:30:53 proxmox kernel: CT: 1014: stopped

Thanks Thomas
 
I'm not really keen to upgrade just now, everything is working fine.
And as I mentioned I have this template running already once on my proxmox without any trouble.
I just don't know where to look to find the problem.

I will download your mailgateway and try to install it.
 
if you send a link to the problematic template and can try it here.
 
I will dig out the link but I'm pretty sure it is not the template, since every template I have installed since a week or so will not start at all.
There must be something broken in the server, just don't know where.
 
just send to t.huber (at) proxmox.com
 
Just installed, works here.

take a look on the "Boot/Init" logs.
(click start and then go to "Virtual Machines Logs: Boot/Init")
 
The boot/Init log only shows:

"starting init logger"

thats all, the VZ only starts for one second and goes to mount, thats it.
 
I tried again and I got this:

starting init logger
init: Unable to open control socket:Address already in use

What address is meant?
 
I did reboot, I did create another container with the same template and still I cannot start it, any ideas??

Is there a way to repair the host installation? or to check if everything is fine?
 
As suggested you should update to the latest version. As I do not know whats wrong on your side I can give no other hint in the moment.
 
You must log in or register to reply here.
Top Bottom