Corosync Error

S

Stephan Kunz

Member
Feb 9, 2015
21
0
21
Hi there;

i wants to have a 2 nodes configuration

cl1 = 192.168.123.10
cl2 = 192.168.123.11

i changed the hosts file and ping is working fine!

then i created a cluster at the cl1 and i added the cl2

like this tutorial:
http://www.jamescoyle.net/how-to/911-how-to-cluster-proxmox

but i earned quorum fail.....

so i make pvecm expected 1


CL1 pvecm status =

root@cl1:/etc# pvecm statusVersion: 6.2.0
Config Version: 2
Cluster Name: cl1proxmoxclu
Cluster Id: 5801
Cluster Member: Yes
Cluster Generation: 301100
Membership state: Cluster-Member
Nodes: 1
Expected votes: 1
Total votes: 1
Node votes: 1
Quorum: 1
Active subsystems: 5
Flags:
Ports Bound: 0
Node name: cl1
Node ID: 1
Multicast addresses: 239.192.22.191
Node addresses: 192.168.123.10
Click to expand...

CL2 PVEcm status =

root@cl2:~# pvecm status
cman_tool: Cannot open connection to cman, is it running ?
Click to expand...

so next i tried to start
Code: 
service cman start

root@cl2:~# service cman startStarting cluster:
Checking if cluster has been disabled at boot... [ OK ]
Checking Network Manager... [ OK ]
Global setup... [ OK ]
Loading kernel modules... [ OK ]
Mounting configfs... [ OK ]
Starting cman... /usr/sbin/ccs_config_validate: line 186: 3197 Segmentation fault (core dumped) ccs_config_dump > $tempfile


Unable to get the configuration
corosync [MAIN ] Corosync Cluster Engine ('1.4.7'): started and ready to provide service.
corosync [MAIN ] Corosync built-in features: nss
corosync [MAIN ] Successfully read config from /etc/cluster/cluster.conf
corosync died with signal: 11 Check cluster logs for details
[FAILED]
Click to expand...

Pleas can you help me???

is it possible to run at my cluster1 proxmox with 3.1 and at cluster2 3.3??






greetings from germany!!!

stephan
 
Last edited:
Stephan Kunz said:
Hi there;

i wants to have a 2 nodes configuration

cl1 = 192.168.123.10
cl2 = 192.168.123.11

i changed the hosts file and ping is working fine!

then i created a cluster at the cl1 and i added the cl2

like this tutorial:
http://www.jamescoyle.net/how-to/911-how-to-cluster-proxmox

but i earned quorum fail.....

so i make pvecm expected 1


CL1 pvecm status =



CL2 PVEcm status =



so next i tried to start
Code: 
service cman start



Pleas can you help me???

I suggest you to add a node. With 3 nodes, the quorum will be fine...
Click to expand...
 
Hi Wolfgang,

i know the guides.

because i don´t know how to update and i run there 6 vm server on the proxmox 3.1. and my backup cluster is 3.3 the newest version.

but now i put a 3. cl 3 on a pc system in the clustershare.

now it works. i see all 3 nodes and on the first node teh vms 100-105

now i want a HA and drbd but i dont know how.

can you do this and we will pay for it? or can you post me an how to for doing this?

We have a nas qnap and i want to use this for storege the vms, is this possible?

greetings
 
Hallo Wolfgang,

root@cl1:/etc/pve# apt-get dist-upgradePaketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Click to expand...

but the version is the 3.1.21 again :(


hi badji...

is this fencing working with my qnap nas?

so can i use this as a fencingdevice?

is there a better guide to make this fencing runing?

greetings from germany
 
What you are using as repository?
 
hmmmm.... i cant find it on my switch....

the website:
http://sbkb.cisco.com/CiscoSB/ukp.aspx?pid=2

give me this opertunities

[TABLE="width: 100%"]
[TR]
[TD="class: articlehead"]Article ID[/TD]
[TD="class: articlehead"]Title[/TD]
[/TR]
[TR]
[TD="class: article"]3424[/TD]
[TD="class: article"]Creation and Management of Secure Sensitive Data (SSD) Rules on 200/300 Series Managed Switches[/TD]
[/TR]
[TR]
[TD="class: article"]4241[/TD]
[TD="class: article"]Configuration of Power over Ethernet (PoE) Properties on Cisco 200/300 Series Managed Switches[/TD]
[/TR]
[TR]
[TD="class: article"]100[/TD]
[TD="class: article"]System Information on the 200/300 Series Managed Switches[/TD]
[/TR]
[TR]
[TD="class: article"]3207[/TD]
[TD="class: article"]Access Profiles Configuration on 200/300 Series Managed Switches[/TD]
[/TR]
[TR]
[TD="class: article"]3214[/TD]
[TD="class: article"]Access Profile Rules Configuration on 200/300 Series Managed Switches[/TD]
[/TR]
[TR]
[TD="class: article"]2009[/TD]
[TD="class: article"]View TCP/UDP Service Status on 200/300 Series Managed Switches[/TD]
[/TR]
[TR]
[TD="class: article"]1800[/TD]
[TD="class: article"]RMON Events on 200/300 Series Managed Switches[/TD]
[/TR]
[TR]
[TD="class: article"]990[/TD]
[TD="class: article"]802.1X Host and Session Authentication Configuration on 200/300 Series Managed Switches[/TD]
[/TR]
[TR]
[TD="class: article"]998[/TD]
[TD="class: article"]Link Layer Discovery Protocol Properties Configuration on 200/300 Series Managed Switches[/TD]
[/TR]
[TR]
[TD="class: article"]85[/TD]
[TD="class: article"]Port Security Configuration on the 200/300 Series Managed Switches[/TD]
[/TR]
[TR]
[TD="class: article"]81[/TD]
[TD="class: article"]Setup Spanning Tree Protocol (STP) on a Interface on the 200/300 Series Managed Switches[/TD]
[/TR]
[/TABLE]
Click to expand...

i tried to find snmp but as you can see there is nothing in the cisco help.

perhaps my sg 200-50 is not able to use snmp

greetings and thx 4 reading ;)
 
Stephan Kunz said:
nothing its emtpy ;(

is this update possible with runing vms?
Click to expand...
If you have a subscription you should have this file:
/etc/apt/sources.list.d/pve-enterprise.list
containing this:
deb https://enterprise.proxmox.com/debian wheezy pve-enterprise

If you do not have a subscription add this file:
/etc/apt/sources.list.d/pve-no-subscription.list
containing this:
deb http://download.proxmox.com/debian wheezy pve-no-subscription

After creating the file:
apt-get update && apt-get dist-upgrade
 
It is not really necessary to stop the VMs,
but you will get a new Kernel and new Qemu-Kvm and they need restart Vm and host.

The recommended way on a so old release is to update and then reboot.
 
You must log in or register to reply here.
Top Bottom