Search results

So you mean, that Proxmox needs DNS resolving after a node is rebooting? When I join a node with pvecm, I use IP address, not domain names. I don't understand why it needs DNS resolving after reboot? Yes, my DNS server is a guest on a node. But what if my DNS would be the DNS of my ISP, if...

Hi! I've run into a very strange upgrade process. I'm using proxmox for a very long time ( from 1.4 ). Our DNS server was always a guest machine on one of the proxmox nodes. Now I upgraded all nodes from 5.1 to 5.2, but the node with the DNS guest failed to join the cluster after reboot. In...

Restarting corosync on hn46 solved this problem So something went wrong when I added hn47 to the cluster, but I don't know what.

Thank for fast your response. I already checked etc/hosts, I think they are OK: hn46: 127.0.0.1 localhost.localdomain localhost xx.xx.xx.76 hn46.in****ax.hu hn46 pvelocalhost hn47: 127.0.0.1 localhost.localdomain localhost xx.xx.xx.77 hn47.in****ax.hu hn47 pvelocalhost

Hi, I have the same problem with proxmox 4.1 root@hn46:~# pvecm nodes Membership information ---------------------- Nodeid Votes Name 2 1 hn42 3 1 hn43 1 1 hn45 4 1 hn46 (local) 5 1...

If I run vzdump manually in the console with "-stdexcludes 0" parameter, then the log directories are saved succesfully. I found in the vzdump manual that the default value of the stdexcludes parameter is 1. I think it is wrong, it should be 0. For some reason the "stdexcludes: 0" in...

I can confirm this bug. All my lxc backups exculdes /var/log. It happens on a node with zfsvols storage and a node with the default local lvm storage too I tried to put "stdexcludes: 0" in vzdump.conf, but not helped.

I can confirm this bug(?) in proxmox 4.1. Deleting the rule above solves this issue. But how can I make this change permament? And is there any side effect removing this rule? Thx

I've got similar problem. Yesterday I upgraded from 3.0 to 3.1. After that the nightly backup of a KVM guest to a CIFS share failed. After 3% it hanged and in the KVM guest load average went up to several hundreds, and stopped responding. There is an openvz CT too on the server, it's backup...

Last night I rebooted both nodes. There was only one problem: 2 of the 4 network card's name has changed (eth0 -> eth4, eth1 -> eth5) I could solve this issue quickly.

Hi, I've got a 2 node cluster with proxmox 2.1 running 10+ CT-s. Let's call this 2 nodes: HN1 and HN2 I did a very very bad thing: On HN1 I wanted to delete "etc" directory in the /root forder. So in that directory I wanted to execute: "rm etc -r". But accidentally I executed "rm /etc...