Recent content by qstraza

The problem was in the bridge settings. I enslaved the wrong interface.

Anyone with the solution?

I decided not to open a new thread but write in this one since the topic seems related. So, I have two nodes with two NICs. Eth0 goes on the internet and eth1 goes on switch on both nodes. Also, eth0 bridges vmbr0 and eth1 bridges vmbr1. If I put two containers on the same node and add...

I have similar problems with migrating with online option enabled. I had the same problems on 2.2, 2.3 and now on 3.1. I run containers on shared NFS. When I run online migration I get this: Sep 20 09:25:31 starting migration of CT 105 to node 'proxmox' (192.168.0.1) Sep 20 09:25:31 container...

something like this should help to move confs around easily: #/bin/bash CT=$1 FROM=$2 TO=$3 DIR=/etc/pve/nodes if [ $# -ne 3 ]; then echo "You need to run it as: $0 CT sourceNode destionationNode" exit; fi if [ ! -d $DIR/$FROM ]; then echo "Looks like source node \"$FROM\" does...

I had similar problems yesterday while upgrading from 2.3 to 3.1. First node went great, I did not run ./pve-upgrade-2.3-to-3.0 --purge at the end. On the second node also everything went smooth, then I ran ./pve-upgrade-2.3-to-3.0 --purge And it delete all of my CTs (on this node), it...

Well it meritoriously started working. So doing this on CT A: iptables -t nat -A POSTROUTING -s '10.20.30.0/24' -o eth0 -j SNAT --to $globalipaddr #you could also do Masquerade, but SNAT is preferable whenever possible iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 8081 -j DNAT...

Hi, I have been struggling for a while now and I cannot figure it out. First, the setting; Node has 2 bridged connection, one is bridged to physical NIC, which goes out to the web (vmbr0). Second bridge (vmbr1) is not bridged to anything but has a IP 10.20.30.1. So, I have two CT's. Lets...

Hi, I had the same error. In my case there was a ssh problem. I set sshd on both nodes to allow only logins with keys so when running the command on node2 pvecm add node1 was problematic because node2 could not ssh to node1 (no keys). So, just make sure first that you are able to ssh as...