Search results

Hi, I was wondering if anyone had any experience on setting up direct connections to my san that houses the iscsi luns. Currently I have everything in the following setup Switch | | | | node node node san I would like to do...

I can tear down and redo my second cluster.

Hi Ksosez, I was wondering if you had a change to test this?

Shut off the second cluster. No change I restarted cman and pve-cluster and I got the totem trying to retransmit (both were talking had quroum) Mar 25 00:22:00 novaprospekt corosync[210647]: [TOTEM ] Retransmit List: 1c8 1c9 1ca 1b3 1b4 1b7 1b8 1b9 1cd 1ba 1bb 1bc 1bd 1be 1bf 1c0 1c1 1c2...

It turns into Mar 22 23:47:42 proton pvedaemon[1863]: WARNING: ipcc_send_rec failed: Connection refused Would it matter that there are two different clusters on the same subnet? For example it is setup like this currently. Fiber in -> Managed Switch (1) -> {node1 cluster a, node2 cluster a}...

None that I have seen.

Same thing happens. Did not see any telltale things in any of the logs I looked it. I have run apt-get update/dist-upgrade and haven't had anything for a couple of weeks. here is current pveversion -v pve-manager: 2.0-38 (pve-manager/2.0/af81df02) running kernel: 2.6.32-7-pve...

I will disable the starting of the VM's on boot and restart the nodes and see if that makes a difference.

Nothing has changed. Same thing is happening on two different setups. 1 has a managed switch (multicast enabled) the other is a dumb switch. Hardware has not changed in either. Only stuff I have done to them is keep them up to date with patches.

Yes I was able to online/offiline migrate vms between the clusters

Output of cman root@proton:~# /etc/init.d/cman restart Stopping cluster: Stopping dlm_controld... [ OK ] Stopping fenced... [ OK ] Stopping cman... [ OK ] Waiting for corosync to shutdown:[ OK ] Unloading kernel modules... [ OK ] Unmounting configfs... [ OK ]...

Nothing that I can find. Was thing in messages was for corosync and that was yesterday Mar 12 22:12:42 novaprospekt corosync[189622]: [TOTEM ] Retransmit List: 41a 424 425 427 3ec 3ef 40b 41d 41e 41f 420 421 422 40c 40d 40e 40f 410 411 412 413 414 415 416 417 418 419 41b 41c 426 Mar 12...

Turns to stopped on Service Viewer. And quorum is lost. And then on both systems I have seen errors in the syslog similar to this. Mar 9 15:06:06 proton pmxcfs[92900]: [status] crit: cpg_send_message failed: 9 Mar 9 15:06:06 proton pmxcfs[92900]: [status] crit: cpg_send_message failed: 9...

root@blackmesa:~# pveversion -v pve-manager: 2.0-38 (pve-manager/2.0/af81df02) running kernel: 2.6.32-7-pve proxmox-ve-2.6.32: 2.0-60 pve-kernel-2.6.32-7-pve: 2.6.32-60 lvm2: 2.02.88-2pve1 clvm: 2.02.88-2pve1 corosync-pve: 1.4.1-1 openais-pve: 1.1.4-2 libqb: 0.10.1-2 redhat-cluster-pve: 3.1.8-3...

Got it working. When that failed it got me to realize that the firewall was actually blocking it. Thanks!

I currently do not have any ACL's for these luns.

[ANSWERED] Shared Iscsi LVM not showing up on new nodes Hi, I am using the following: pve-manager: 2.0-38 (pve-manager/2.0/af81df02) running kernel: 2.6.32-7-pve proxmox-ve-2.6.32: 2.0-60 pve-kernel-2.6.32-7-pve: 2.6.32-60 lvm2: 2.02.88-2pve1 clvm: 2.02.88-2pve1 corosync-pve: 1.4.1-1...

This seems to have fixed it :) in Scientific Linux 6.1

I am not running any x server on these vms.

I also am using a shared iSCSI LVM storage, and here is my uname -a is Linux local.local 2.6.32-220.4.1.el6.x86_64 #1 SMP Mon Jan 23 17:20:44 CST 2012 x86_64 x86_64 x86_64 GNU/Linux 100.conf root@proton:/etc/pve/nodes/proton/qemu-server# cat 100.conf bootdisk: virtio0 cores: 2 ide2...