Recent content by dank

Perferk. I will try it.

Hi, have a cluster of nodes with different powerfull hardware. After a while, the cluster loses nodes (going red in the UI). VMs are still running. The logfile produces a lot of corosync[364738]: [TOTEM ] Retransmit List: ca8 ca9 caa cab ... Messages. Google means...

Hi, I have the same problem here (a cluster of 11 different powerful node). After a while, nodes will be shown as not reachable. @tapsa: Could you solve the problem?

Hi, I'm not able to migrate an openvz container online to another machine inside the cluster. I got the following error: May 08 13:27:41 starting migration of CT 150 to node 'sv01' (141.24.212.28) May 08 13:27:41 container is running - using online migration May 08 13:27:41 container data is...

And shutdown before? As mentioned, I made an update shortly before. After this, the gui mades the trouble. However, now it is running. Thank you again.

Perfect!!! That's what I'm looking for :-). I tried a restart of some of the services before. But, it looks there are depencies between them. Now, my cluster have a running GUI without a reboot. You should think about an automatic restarts of this services aftern an update. Regards Daniel

No, no change. Is there a connection problem between the proxmox services? Can I reset them manually? Similar to a reboot.

Yes, networking is running. All vms are accessable from outside. The access from on clusternode the another does also work.

Hi, I have here a cluster of 5 nodes (all running the same version 2.0 of proxmox). After one week, one of the cluster nodes was not accessibly by the ui. The vm's were already running. The kernelog says: kernel: Neighbour table overflow. kernel: __ratelimit: 62 callbacks suppressed As...

You can change it on the cli: /etc/ssh/sshd_config (ssh daemon) /etc/ssh/ssh_config (client) Regards

Hi, I had built an openvz container with two bridged network cards: - eth0 is brigded to the external network and - eth1 is bridged to the internal (192.x.x.x) network. Both network cards should be configured using dhcp. eth0 gets his IP depending on the configured MAC from the external...