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
On Fri, Jan 6, 2012 at 6:05 PM, Fil wrote:
> Thanks for the fix, its working on this cluster, I'll test it in the
> morning on few more boxes.
>
> systemd, what was wrong with system V startup scripts
I believe they were too easy to work with
>
> fil
>
> On 01/06/2012 01:13 AM, Andrew Beekho
Thanks for the fix, its working on this cluster, I'll test it in the
morning on few more boxes.
systemd, what was wrong with system V startup scripts
fil
On 01/06/2012 01:13 AM, Andrew Beekhof wrote:
> On Fri, Jan 6, 2012 at 4:20 PM, Fil wrote:
>> :( weird huh
>
> It looks like they
On Fri, Jan 6, 2012 at 4:20 PM, Fil wrote:
> :( weird huh
It looks like they broke the handling of Type=forking
What I especially loved about spending the afternoon debugging systemd
is that there is zero information to go on.
Pure guesswork.
Switch over to Type=simple (and add -f to ExecS
:( weird huh
On 01/05/2012 11:54 PM, Andrew Beekhof wrote:
> Urgh, I updated my system and now I get the same behaviour as you :-(
>
> On Fri, Jan 6, 2012 at 3:50 PM, Andrew Beekhof wrote:
>> Did you disable cman's quorum timeout as per:
>>
>> http://www.clusterlabs.org/doc/en-US/Pacema
yes
On 01/05/2012 11:50 PM, Andrew Beekhof wrote:
> Did you disable cman's quorum timeout as per:
>
> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch08s02s02.html
> ?
>
> On Thu, Jan 5, 2012 at 5:15 PM, Fil wrote:
>> I am doing exactly the same thing:
>>
>> s
Urgh, I updated my system and now I get the same behaviour as you :-(
On Fri, Jan 6, 2012 at 3:50 PM, Andrew Beekhof wrote:
> Did you disable cman's quorum timeout as per:
>
> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch08s02s02.html
> ?
>
> On Thu, Jan 5, 2
Did you disable cman's quorum timeout as per:
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch08s02s02.html
?
On Thu, Jan 5, 2012 at 5:15 PM, Fil wrote:
> I am doing exactly the same thing:
>
> systemctl start cman.service
> systemctl start pacemaker.service
>
I am doing exactly the same thing:
systemctl start cman.service
systemctl start pacemaker.service
# pacemakerd --features
Pacemaker 1.1.6-4.fc16 (Build: 89678d4947c5bd466e2f31acd58ea4e1edb854d5)
Supporting: generated-manpages agent-manpages ascii-docs ncurses
trace-logging cman corosync-quorum
It seems to work here.
Can you post the output of: pacemakerd --features
What are the exact commands you're running?
I'm running:
systemctl start cman.service
systemctl start pacemaker.service
On Thu, Jan 5, 2012 at 8:29 AM, Andrew Beekhof wrote:
> Ok, I'll try to test cman+pacemaker on f
Ok, I'll try to test cman+pacemaker on f16 in the next few days.
Last time I checked corosync+pacemaker.
On Tue, Jan 3, 2012 at 12:49 PM, Fil wrote:
> yes systemd, and no selinux.
>
> On 01/02/2012 08:04 PM, Andrew Beekhof wrote:
>> On Tue, Jan 3, 2012 at 11:22 AM, Fil wrote:
>>> nothing from th
yes systemd, and no selinux.
On 01/02/2012 08:04 PM, Andrew Beekhof wrote:
> On Tue, Jan 3, 2012 at 11:22 AM, Fil wrote:
>> nothing from the pacemaker, but if I do:
>>
>> cd /etc/init.d/; ./pacemaker start
>>
>> it works every time, while:
>>
>> /etc/init.d/pacemaker start
>> or
>> systemctl star
On Tue, Jan 3, 2012 at 11:22 AM, Fil wrote:
> nothing from the pacemaker, but if I do:
>
> cd /etc/init.d/; ./pacemaker start
>
> it works every time, while:
>
> /etc/init.d/pacemaker start
> or
> systemctl start pacemaker.service
>
> fails. Which leads me to believe upstart is to blame for this.
nothing from the pacemaker, but if I do:
cd /etc/init.d/; ./pacemaker start
it works every time, while:
/etc/init.d/pacemaker start
or
systemctl start pacemaker.service
fails. Which leads me to believe upstart is to blame for this. Weird
thing is, this works in corosync/pacemaker scenario but n
On Sat, Dec 31, 2011 at 12:24 PM, Fil wrote:
> Hi Andreas,
>
> That is exactly how I am staring the cluster first cman and then
> pacemaker. For some reason pacemaker doesn't start until I run
> pacemakerd by hand and then kill it. After that I can run
>
> systemctl start pacemaker.service ( or /e
Hi Andreas,
That is exactly how I am staring the cluster first cman and then
pacemaker. For some reason pacemaker doesn't start until I run
pacemakerd by hand and then kill it. After that I can run
systemctl start pacemaker.service ( or /etc/init.d/pacemaker start )
This is the only thing which
Hello,
On 12/24/2011 09:13 AM, Fil wrote:
> Hi everyone,
>
> Happy holidays!
>
> I need some help with adding CMAN to my current cluster config.
> Currently I have a two node Corosync/Pacemaker (Active/Passive) cluster.
> It works as expected. Now I need to add a distributed filesystem to my
> s
Hi everyone,
Happy holidays!
I need some help with adding CMAN to my current cluster config.
Currently I have a two node Corosync/Pacemaker (Active/Passive) cluster.
It works as expected. Now I need to add a distributed filesystem to my
setup. I would like to test GFS2. As much as I understand I
34 matches
Mail list logo
