Re: [ClusterLabs] Fence agent for VirtualBox

Hi, we have added support for a host with Windows but it is not trivial to setup because of various contexts/privileges. Install openssh on Windows (tutorial can be found on http://linuxbsdos.com/2015/07/30/how-to-install-openssh-on-windows-10/) There is a major issue with current setup in

[ClusterLabs] Adding a node to the cluster deployed with "Unicast configuration"

Hi everyone, i have a problem when scaling a corosync/pacemaker cluster deployed using unicast. eg on corosync.conf. nodelist { node { ring0_addr: 10.10.0.10 nodeid: 1 } node { ring0_addr: 10.10.0.11 nodeid: 2 } } Tried to add the new node with the new config (meaning, adding the new node) nad

[ClusterLabs] Fence agent for VirtualBox

Hi, I have updated fence agent for Virtual Box (upstream git). The main benefit is new option --host-os (host_os on stdin) that supports linux|macos. So if your host is linux/macos all you need to set is this option (and ssh access to a machine). I would love to add a support also for windows but

Re: [ClusterLabs] Antw: Oracle Stopping

The first place where you need to look is oracle log. 2017-02-22 8:43 GMT+01:00 Ulrich Windl : Chad Cravens schrieb am 22.02.2017 um 02:44 in > Nachricht >

Re: [ClusterLabs] Antw: Corosync ring marked as FAULTY

22.02.2017 11:40, Denis Gribkov wrote: Hi, On 22/02/17 10:35, bliu wrote: Did you specify interface with "-i " when you are using tcpdump. If you did, corosync is not talking with the multicast address, you need to check if your private network support multicast. Yes, I have used command:

Re: [ClusterLabs] Antw: Corosync ring marked as FAULTY

Hi, On 22/02/17 10:35, bliu wrote: Did you specify interface with "-i " when you are using tcpdump. If you did, corosync is not talking with the multicast address, you need to check if your private network support multicast. Yes, I have used command: # tcpdump -i em2 udp port 5505 -vv -X

Re: [ClusterLabs] Antw: Corosync ring marked as FAULTY

Hi On 02/22/2017 04:24 PM, Denis Gribkov wrote: Hi, Just tried - no any packet captured even if I re-enabled ring 0 on all nodes. Re-enable ring 0 will just reset the faulty to 0, no more operation. Did you specify interface with "-i " when you are using tcpdump. If you did, corosync

Re: [ClusterLabs] Antw: Corosync ring marked as FAULTY

Hi, Just tried - no any packet captured even if I re-enabled ring 0 on all nodes. On the other hand if I create listen UDP socket on the same port using nc utility: # nc -u -l 5505 then try to send some messages from other node - I can capture and see these packets. On 22/02/17 10:02,

Re: [ClusterLabs] Antw: Corosync ring marked as FAULTY

Hi, Denis could you try tcpdump "udp port 5505" on the private network to see if there is packet? On 02/22/2017 03:47 PM, Denis Gribkov wrote: In our case it does not create problems since all nodes are located in few networks whichserved by single router. There are also no any errors