Page 1 of 1
Virtuozzo Help
Posted: Fri Feb 25, 2011 10:04 am
by jmackenz
Not exactly control panel, but kinda related.
I'm trying to install virtuozzo for the first time, it all seemed to go well until I tried to login to my "parallels power panel" and was told my username and password seem to be incorrect.
I can ssh in and su to root.
Am I missing something? it seems to tell me to log in with my root credentials , but no go.
Re: Virtuozzo Help
Posted: Fri Feb 25, 2011 6:45 pm
by jmackenz
Ok, so I made some headway :
I found the vzlist command it returned :
vzlist
CTID NPROC STATUS IP_ADDR HOSTNAME
1 1 running 192.168.195.134 -
50 12 running x.public.ip.address managed.domain
101 12 running x.public.ip.address server101.domain
I also found how to set root passwords on these containers and can now get in through the agent and also ssh
Now I set resolv.conf in container 50 to my main nameservers, and I can ping them, but cannot resolve names.
Any ideas? Also where did it pull the 192.blah address from?
Re: Virtuozzo Help
Posted: Sat Feb 26, 2011 6:04 am
by paulie
jmackenz wrote:Ok, so I made some headway :
CTID NPROC STATUS IP_ADDR HOSTNAME
1 1 running 192.168.195.134 -
50 12 running x.public.ip.address managed.domain
101 12 running x.public.ip.address server101.domain
I also found how to set root passwords on these containers and can now get in through the agent and also ssh
Now I set resolv.conf in container 50 to my main nameservers, and I can ping them, but cannot resolve names.
Any ideas? Also where did it pull the 192.blah address from?
Container 1 is your service container where Virtuozzo does most of its stuff, it creates its own internal IP and AFAIK thats how the node communicates with the service container.
This looks like Virtuozzo 4.6 in which case container 50 is your PIM (or PVA) as its now called, you should be able to login to this at
https://managed.domain:4648 with god only knows what username and password (I use what I think is the root user and password but we only have one 4.6 install).
Your power panels are located on port 4643 and we've only ever logged into them with plesk credentials, but it seems logical that your root username and password could work.
In terms of nameservers, rather than setting them in resolv.conf set them on the command line using the --nameserver command (from memory) or through PVA (which you may not be able to get into!).
I found the whole install process for Virtuozzo 4.6 and especially the idea of having PIM (now PVA) in its own container very confusing, I have yet to have the fun involved in either upgrading 4.0 to 4.6 or in adding another 4.6 server to PIM. Its a strange world when you consider Virtuozzo 4.0 to be a polished install process.
Hope this helps, but it probably doesn't. Unfortunately there's no avoiding the documentation with Virtuozzo...
Paul.
Re: Virtuozzo Help
Posted: Sat Feb 26, 2011 9:05 am
by jmackenz
Hi Paulie,
You confirmed my thoughts on container 50 , however I set nameserver to the IP from command line and from editing container conf file.
Both seem to lead to their info being generated in the containers resolv.conf , but still no name resolution.
Other Thoughts?
Re: Virtuozzo Help
Posted: Sun Feb 27, 2011 11:32 pm
by jmackenz
So... I came across the following regarding some specific blocks my host puts in place.
http://forums.serverbeach.com/showthrea ... -the-Beach
from those instructions I set container 50 to be 172.16.98.101
and I also on the server level added eth0:0 as 172.16.98.101 , with this i left the gateway set to the same address as the gateway in eth0
I then ran the following commands :
Code: Select all
iptables -t nat -A PREROUTING -d public.secondary.ip -i eth0 -p tcp --dport 22 -j DNAT --to-destination 172.16.98.101:22
iptables -t nat -A PREROUTING -d public.secondary.ip -i eth0 -p tcp --dport 4643 -j DNAT --to-destination 172.16.98.101:4643
iptables -t nat -A PREROUTING -d public.secondary.ip-i eth0 -p tcp --dport 80 -j DNAT --to-destination 172.16.98.101:80
iptables -t nat -A POSTROUTING -s 172.16.98.101 -o eth0 -j SNAT --to-source public.secondary.ip
iptables -t nat -A OUTPUT -d public.secondary.ip -j DNAT --to-destination 172.16.98.101
iptables -P FORWARD ACCEPT
Again I can ping out, I can ssh in , but I can't resolve names. any ideas with this further insight?