Now I have added an eth0 in webgui, but it is not visible inside the container by trying with ifconfig. I have also tried to add manually in network/interfaces an eth0 entry - still not visible.
and remember venet0:0 is not reachable, venet0:1 is pingable ... did not understand this. But the...
No. Have not tried. With Proxmox 1.x this was not necessary.
Additonal - why it is possible to reach always one of the IP addresses I gave the container, but not all IPs (even when they are from the same network)?
The iptables rule is already removed - that was a test, but without ip tables...
the arp requested is received by the host:
But the host did not answer.
And the host itself can ping the container:
venet0 is up
The container can't ping anything outside:
IPs inside container are correct:
IP address which is configurated as venet0:0 can be reached from outside, but...
I really become silly now.
I first had a 2.x cluster with 3 nodes.
1 node crashed and it was not possible to remove the crashed node from the cluster.
I tried to setup the node completly new and first it was possible to add the node again to the cluster.
Then the IP addresses and hostnames...
hell - now vzlist is empty.
but all containers are still here:
drwxr-xr-x 20 root root 4096 May 6 00:05 100
drwxr-xr-x 20 root root 4096 May 6 09:21 101
drwxr-xr-x 21 root root 4096 May 10 16:15 102
how to start or reacitvate the containers now?
yep. this is what i did - and as result i have two clusters, but i want a cluster and a node.
Additional - running (!) - containers disappeared from webgui on kemp010
Additional in ssh all additional ip addresses disappeared when I take a look with ipconfig, but containers with not listed IPs...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.