I remove it out, and let's Corosync design itself what address will be used.
It's work well.
Teenigma
On Wed, Jul 16, 2014 at 7:05 PM, Jan Friesse wrote:
> Teerapatr
>
>> Dear Honza,
>>
>> Sorry to say this, but I found new error again. LOL
>>
>> This time, I already install the 1.4.1-17 as your
Teerapatr
> Dear Honza,
>
> Sorry to say this, but I found new error again. LOL
>
> This time, I already install the 1.4.1-17 as your advice.
> And the nodename, without altname, is map to IPv6 using hosts file.
> Everything is fine, but the 2 node can't communicate to each other.
> So I add the
Dear all,
The problem is solved.
Teenigma
On Tue, Jul 15, 2014 at 1:53 PM, Teerapatr Kittiratanachai
wrote:
> Dear Honza,
>
> Sorry to say this, but I found new error again. LOL
>
> This time, I already install the 1.4.1-17 as your advice.
> And the nodename, without altname, is map to IPv6 usi
Dear Honza,
Sorry to say this, but I found new error again. LOL
This time, I already install the 1.4.1-17 as your advice.
And the nodename, without altname, is map to IPv6 using hosts file.
Everything is fine, but the 2 node can't communicate to each other.
So I add the multicast address manually
Honza
Great, Thank you very much.
But the terrible thing for me is I'm using the package from OpenSUSE repo.
When i turn back to CentOS repo, which store lower version, the
Dependency problem has occurred.
Anyway, thank you for your help.
Teenigma
On Mon, Jul 14, 2014 at 8:51 PM, Jan Friesse
Honza,
How do I include the patch with my CentOS package?
Do I need to compile them manually?
Yes. Also official CentOS version was never 1.4.5. If you are using
CentOS, just use stock 1.4.1-17.1. Patch is included there.
Honza
TeEniGMa
On Mon, Jul 14, 2014 at 3:21 PM, Jan Friesse wrote
Honza,
How do I include the patch with my CentOS package?
Do I need to compile them manually?
TeEniGMa
On Mon, Jul 14, 2014 at 3:21 PM, Jan Friesse wrote:
> Teerapatr,
>
>
>> For more information,
>>
>>
>> these are LOG from /var/log/messages
>> ...
>> Jul 14 10:28:07 wh00 kernel: : DLM (built
Teerapatr,
> For more information,
these are LOG from /var/log/messages
...
Jul 14 10:28:07 wh00 kernel: : DLM (built Mar 25 2014 20:01:13) installed
Jul 14 10:28:07 wh00 corosync[2716]: [MAIN ] Corosync Cluster
Engine ('1.4.5'): started and ready to provide service.
Jul 14 10:28:07 wh00 cor
For more information,
these are LOG from /var/log/messages
...
Jul 14 10:28:07 wh00 kernel: : DLM (built Mar 25 2014 20:01:13) installed
Jul 14 10:28:07 wh00 corosync[2716]: [MAIN ] Corosync Cluster
Engine ('1.4.5'): started and ready to provide service.
Jul 14 10:28:07 wh00 corosync[2716]: [
Dear Honza,
Sorry for late reply.
After I have tested with all new configuration.
On IPv6 only, and with no altname.
I face with error below,
Starting cluster:
Checking if cluster has been disabled at boot...[ OK ]
Checking Network Manager... [ OK ]
Teerapatr,
> Hi Honza,
>
> As you said I use the nodename identify by hostname (which be accessed
> via IPv6) and the node also has the altname (which be IPv4 address).
>
This doesn't work. Both hostname and altname have to be same IP version.
> Now, I configure the mcast address for both node
Hi Honza,
As you said I use the nodename identify by hostname (which be accessed
via IPv6) and the node also has the altname (which be IPv4 address).
Now, I configure the mcast address for both nodename and altname
manually. The CMAN and Pacemaker can start ad well. But they don't
communicate to
Teerapatr,
> OK, some problems are solved.
> I use the incorrect hostname.
>
> For now, the new problem has occured.
>
> Starting cman... Node address family does not match multicast address family
> Unable to get the configuration
> Node address family does not match multicast address family
OK, some problems are solved.
I use the incorrect hostname.
For now, the new problem has occured.
Starting cman... Node address family does not match multicast address family
Unable to get the configuration
Node address family does not match multicast address family
cman_tool: corosync daemon d
I not found any LOG message
/var/log/messages
...
Jul 10 07:44:19 nwh00 kernel: : DLM (built Jun 19 2014 21:16:01) installed
Jul 10 07:44:22 nwh00 pacemaker: Aborting startup of Pacemaker Cluster Manager
...
and this is what display when I try to start pacemaker
# /etc/init.d/pacemaker start
Sta
On 9 Jul 2014, at 9:15 pm, Teerapatr Kittiratanachai
wrote:
> Dear All,
>
> I has implemented the HA on dual stack servers,
> Firstly, I doesn't deploy IPv6 record on DNS yet. The CMAN and
> PACEMAKER can work as normal.
> But, after I create record on DNS server, i found the error that
>
Dear All,
I has implemented the HA on dual stack servers,
Firstly, I doesn't deploy IPv6 record on DNS yet. The CMAN and
PACEMAKER can work as normal.
But, after I create record on DNS server, i found the error that
cann't start CMAN.
Are CMAN and PACEMAKER support the IPv6?
Regards,
T. Ki
17 matches
Mail list logo
