Re: [ClusterLabs] Anyone successfully install Pacemaker/Corosync on Freebsd?

[Christine Caulfield]

On 21/12/15 16:12, Ken Gaillot wrote:
> On 12/19/2015 04:56 PM, mike wrote:
>> Hi All,
>>
>> just curious if anyone has had any luck at one point installing
>> Pacemaker and Corosync on FreeBSD. I have to install from source of
>> course and I've run into an issue when running ./configure while trying
>> to install Corosync. The process craps out at nss with this error:
> 
> FYI, Ruben Kerkhof has done some recent work to get the FreeBSD build
> working. It will go into the next 1.1.14 release candidate. In the
> meantime, make sure you have the very latest code from upstream's 1.1
> branch.
> 

I also strongly recommend using the latest (from git) version of libqb
has it has some FreeBSD bugs fixed in it. We plan to do a proper release
of this in the new year.

Chrissie

>> checking for nss... configure: error: in `/root/heartbeat/corosync-2.3.3':
>> configure: error: The pkg-config script could not be found or is too
>> old. Make sure it
>> is in your PATH or set the PKG_CONFIG environment variable to the full
>> path to pkg-config.​
>> Alternatively, you may set the environment variables nss_CFLAGS
>> and nss_LIBS to avoid the need to call pkg-config.
>> See the pkg-config man page for more details.
>>
>> I've looked unsuccessfully for a package called pkg-config and nss
>> appears to be installed as you can see from this output:
>>
>> root@wellesley:~/heartbeat/corosync-2.3.3 # pkg install nss
>> Updating FreeBSD repository catalogue...
>> FreeBSD repository is up-to-date.
>> All repositories are up-to-date.
>> Checking integrity... done (0 conflicting)
>> The most recent version of packages are already installed
>>
>> Anyway - just looking for any suggestions. Hoping that perhaps someone
>> has successfully done this.
>>
>> thanks in advance
>> -mgb
> 
> 
> ___
> Users mailing list: Users@clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> 


___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Help required for N+1 redundancy setup

[Nikhil Utane]

Thanks to you Ken for giving all the pointers.
Yes, I can use service start/stop which should be a lot simpler. Thanks
again. :)

On Tue, Dec 22, 2015 at 9:29 PM, Ken Gaillot  wrote:

> On 12/22/2015 12:17 AM, Nikhil Utane wrote:
> > I have prepared a write-up explaining my requirements and current
> solution
> > that I am proposing based on my understanding so far.
> > Kindly let me know if what I am proposing is good or there is a better
> way
> > to achieve the same.
> >
> >
> https://drive.google.com/file/d/0B0zPvL-Tp-JSTEJpcUFTanhsNzQ/view?usp=sharing
> >
> > Let me know if you face any issue in accessing the above link. Thanks.
>
> This looks great. Very well thought-out.
>
> One comment:
>
> "8. In the event of any failover, the standby node will get notified
> through an event and it will execute a script that will read the
> configuration specific to the node that went down (again using
> crm_attribute) and become active."
>
> It may not be necessary to use the notifications for this. Pacemaker
> will call your resource agent with the "start" action on the standby
> node, after ensuring it is stopped on the previous node. Hopefully the
> resource agent's start action has (or can have, with configuration
> options) all the information you need.
>
> If you do end up needing notifications, be aware that the feature will
> be disabled by default in the 1.1.14 release, because changes in syntax
> are expected in further development. You can define a compile-time
> constant to enable them.
>
>
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] cluster node config - DNS or IP addresses?

[Digimer]

On 22/12/15 05:31 PM, Ilia Sokolinski wrote:
> Hi,
> 
> What are the best practices with respect to using DNS names vs IP addresses 
> in pacemaker/corosync configuration?
> 
> Thanks
> 
> Ilia Sokolinski

I use `uname -n` and have the hostname resolve via /etc/hosts.

-- 
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?

___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] Regarding IP tables and IP Address clone

[Somanath Jeeva]

Hi ,

Thanks for the quick reply.

I will check with our IT team regarding the multicast MAC at switch level.

But the Virtual IP is reachable for 15 minutes or so after I start the 
pacemaker/Corosync service. After which it becomes unreachable. However when I 
restart the iptables service it becomes reachable again for another 15 min.
Would this be because of firewall configurations.


With Regards
Somanath Thilak J

___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org