[Pacemaker] Hostname issues

[Dan Frincu]

Hi,

On Tue, Jun 21, 2011 at 5:12 PM, Proskurin Kirill
<k.proskurin at corp.mail.ru>wrote:

> Hello all
>
> I have 4 nodes - all of them with two nic in two network. All of them have
> 2 DNS name - one for internal network and one for external.
>
> This host *must* have a hostname of external network(for other software to
> work). Corosync must works on internal nic.
>
> But it is ask for uname -n for node name and get external name.
>
> How to avoide this? I can`t change hostname to int one and can`t run
> corosync on ext network.
>

Corosync runs on the IP addresses that you configure in
/etc/corosync/corosync.conf.

Pacemaker requires unique hostnames (as they are retrieved via uname -n) to
function properly.

If they are "internal" or "external" it really doesn't matter for the
cluster stack, that's a human point of view, the machine has no real opinion
in this (e.g.: if you configure IP communication channels properly, then
corosync will use the internal network, but the hostnames will be set to the
"external" hostname as these two are unrelated).

Regards


>
> --
> Best regards,
> Proskurin Kirill
>
> ______________________________**_________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/**mailman/listinfo/pacemaker<http://oss.clusterlabs.org/mailman/listinfo/pacemaker>
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/**doc/Cluster_from_Scratch.pdf<http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf>
> Bugs: http://developerbugs.linux-**foundation.org/enter_bug.cgi?**
> product=Pacemaker<http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker>
>



-- 
Dan Frincu
CCNA, RHCE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110621/814d39ec/attachment.htm>