I try proced it manual and have not got any error. Strange. Ok, I manually
remove include line, restart pgsql on all nodes and cleanup resource. Now I
got this:
root@a:~# crm_mon -VAf -1
============
Last updated: Sat Dec 14 15:48:17 2013
Last change: Sat Dec 14 15:48:04 2013 via crmd on a.mydomain.com
Stack: openais
Current DC: a.mydomain.com - partition with quorum
Version: 1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff
3 Nodes configured, 3 expected votes
6 Resources configured.
============
Online: [ a.mydomain.com c.mydomain.com b.mydomain.com ]
Master/Slave Set: msPostgresql [pgsql]
Slaves: [ b.mydomain.com c.mydomain.com ]
Stopped: [ pgsql:0 ]
apache-master-ip (ocf::heartbeat:IPaddr2): Started a.mydomain.com
apache (ocf::heartbeat:apache): Started a.mydomain.com
Node Attributes:
* Node a.mydomain.com:
+ master-pgsql:0 : -INFINITY
+ pgsql-data-status : LATEST
+ pgsql-status : STOP
* Node c.mydomain.com:
+ pgsql-data-status : STREAMING|ASYNC
+ pgsql-status : HS:alone
+ pgsql-xlog-loc : 000000001B000090
* Node b.mydomain.com:
+ pgsql-data-status : STREAMING|ASYNC
+ pgsql-status : HS:alone
+ pgsql-xlog-loc : 000000001B000090
Migration summary:
* Node a.mydomain.com:
pgsql:0: migration-threshold=1 fail-count=1
* Node b.mydomain.com:
* Node c.mydomain.com:
Failed actions:
pgsql:0_monitor_4000 (node=a.mydomain.com, call=36, rc=7,
status=complete): not running
root@a:~# /etc/init.d/postgresql status
9.3/main (port 5432): down
root@a:~#
I try start pgsql and cleanup pgsq. And got same error. Why RA down pgsql
on a node?
I try cleanup few times and got this:
============
Last updated: Sat Dec 14 15:52:33 2013
Last change: Sat Dec 14 15:52:30 2013 via crmd on a.mydomain.com
Stack: openais
Current DC: a.mydomain.com - partition with quorum
Version: 1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff
3 Nodes configured, 3 expected votes
6 Resources configured.
============
Online: [ a.mydomain.com c.mydomain.com b.mydomain.com ]
Resource Group: master
pgsql-master-ip (ocf::heartbeat:IPaddr2): Started c.mydomain.com
Master/Slave Set: msPostgresql [pgsql]
Masters: [ c.mydomain.com ]
Slaves: [ a.mydomain.com ]
Stopped: [ pgsql:1 ]
apache-master-ip (ocf::heartbeat:IPaddr2): Started a.mydomain.com
apache (ocf::heartbeat:apache): Started a.mydomain.com
Node Attributes:
* Node a.mydomain.com:
+ master-pgsql:0 : -INFINITY
+ pgsql-data-status : STREAMING|ASYNC
+ pgsql-status : HS:async
* Node c.mydomain.com:
+ master-pgsql:2 : 1000
+ pgsql-data-status : LATEST
+ pgsql-master-baseline : 000000001C000090
+ pgsql-status : PRI
* Node b.mydomain.com:
+ master-pgsql:1 : -INFINITY
+ pgsql-data-status : DISCONNECT
+ pgsql-status : STOP
Migration summary:
* Node a.mydomain.com:
* Node b.mydomain.com:
pgsql:1: migration-threshold=1 fail-count=1000000
* Node c.mydomain.com:
Failed actions:
pgsql:1_start_0 (node=b.mydomain.com, call=64, rc=1, status=complete):
unknown error
I manualy start pgsql on b and cleanup again
And now I have:
Online: [ a.mydomain.com c.mydomain.com b.mydomain.com ]
Resource Group: master
pgsql-master-ip (ocf::heartbeat:IPaddr2): Started c.mydomain.com
Master/Slave Set: msPostgresql [pgsql]
Masters: [ c.mydomain.com ]
Slaves: [ a.mydomain.com b.mydomain.com ]
apache-master-ip (ocf::heartbeat:IPaddr2): Started a.mydomain.com
apache (ocf::heartbeat:apache): Started a.mydomain.com
Node Attributes:
* Node a.mydomain.com:
+ master-pgsql:0 : -INFINITY
+ pgsql-data-status : STREAMING|ASYNC
+ pgsql-status : HS:async
* Node c.mydomain.com:
+ master-pgsql:2 : 1000
+ pgsql-data-status : LATEST
+ pgsql-master-baseline : 000000001C000090
+ pgsql-status : PRI
* Node b.mydomain.com:
+ master-pgsql:1 : -INFINITY
+ pgsql-data-status : DISCONNECT
+ pgsql-status : HS:alone
Migration summary:
* Node a.mydomain.com:
* Node b.mydomain.com:
* Node c.mydomain.com:
So, how I can switch master to a node and fix HS:standalone status?
About your questions:
I have two questions.
1. As you can see - now I have not hawe two master status in one node
2. My node_list contains is a.mydomain.com b.mydomain.com c.mydomain.com
2013/12/14 Takehiro Matsushima <[email protected]>
> Thank you.
>
> > May be sed rule is incorrect?
> Okay, let's try it manually.
>
> REP_MODE_CONF=/var/lib/pgsql/tmp/rep_mode.conf
> rep_mode_string="include '$REP_MODE_CONF' # added by pgsql RA"
> sed "/${rep_mode_string//\//\\/}/d"
> /etc/postgresql/9.3/main/postgresql.conf
>
>
> BTW, in your past post,
>
> > Node Attributes:
> > * Node a.mydomain.com:
> > + master-pgsql:0 : 1000
> > + master-pgsql:1 : 1000
> > + pgsql-data-status : LATEST
> > + pgsql-master-baseline : 0000000008000090
> > + pgsql-status : PRI
> > * Node c.mydomain.com:
> > + master-pgsql:2 : -INFINITY
> > + pgsql-data-status : STREAMING|ASYNC
> > + pgsql-status : HS:async
> > * Node b.mydomain.com:
> > + master-pgsql:0 : -INFINITY
> > + master-pgsql:1 : 100
> > + pgsql-data-status : STREAMING|SYNC
> > + pgsql-status : HS:sync
> > + pgsql-xlog-loc : 000000000E0000C8
>
> and
> > node_list="a b c"
> in pgsql primitive params.
>
> I have two questions.
>
> 1. Can you find two "master-pgsql" lines in a.mydomain.com and
> b.mydomain.com yet?
> 2. Does parameter of pgsql primitive "node_list" contains "a b c", not
> "a.mydomain.com b.mydomain.com c.mydomain.com"?
>
> I'm sorry to not be resolved easily.
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
