Recent content by peetaur

This happened again over the weekend. This time, I had ssh clients connected and idle, and 2 of them were disconnected too (using ssh settings TCPKeepAlive=yes and ServerAliveInterval=30). This doesn't happen with any other servers, so I'm still not convinced that there is a chance that it is...

I pulled the network on one machine, waited until it lost quorum, checked cman, and then plugged it back in. The one node lost quorum as expected. I didn't try unplugging a second node, because I don't want to have to reboot them to fix it. It didn't lose the qdisk since it is on a separate...

Nope. And I've seen that thread. root@bcvm3:~# iptables --list -v --line-numbers Chain INPUT (policy ACCEPT 1227K packets, 678M bytes) num pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) num pkts...

I started this discussion here: http://forum.proxmox.com/threads/10629-New-Kernel-and-bug-fixes?p=60597#post60597 And moved it here since it's no longer on topic. Problem symptoms: 2 nodes dropped out of the cluster for apparently no reason. bcvm1 was then the only node in...

Okay, but it just took REALLY long, and then sent me back to the http://forum.proxmox.com/forums/16-Proxmox-VE-2-x-Installation-and-configuration page without any message. But I'll remember to wait much longer next time. Other vBulletin forums send you to the thread you posted in, so I didn't...

The forum lost my last 2 posts... so forgive me if it appears and then this is duplicate. Here's what it looked like yesterday: root@bcvm2:~# clustat Could not connect to CMAN: Connection refused root@bcvm2:~# /etc/init.d/cman status Found stale pid file The first node that dropped out had...

The forum lost my last post... so forgive me if it appears and then this is duplicate. Here's what it looked like yesterday: root@bcvm2:~# clustat Could not connect to CMAN: Connection refused root@bcvm2:~# /etc/init.d/cman status Found stale pid file The first node that dropped out had...

A bit the other way around... Randomly I find cman stopped... and *if* quorum is lost *as a result* (due to more than one lost), I have to reboot some nodes to get quorum again before /etc/init.d/cman restart will make the node rejoin. And I'm curious on how to fix it. I don't know for sure...

I have 2 questions about the cman stopping bug. https://bugzilla.proxmox.com/show_bug.cgi?id=238 1) Does the fix also prevent cman from stopping during normal operation if quorum/connection is lost, or just when it boots? 2) And will a node now reconnect if it loses connection? Before, cman...

In that case, I suggest adding a message to the GUI when making changes. Or ideally, put a note on each line that needs a reboot, such as a "*", or a new column showing the effective setting. For example: And you said "by default". Does that mean there is a way to activate it? And what are...

When I remove a virtio .raw disk from a VM, it still appears in /dev/vdb in the VM. In my case, this disk is on an NFS server. Is this expected? What should I do to actually remove it? "qm monitor 100" followed by "info blocK" lists the disk, but "qm config 100" does not list the disk anymore...