I'm sorry.
restart_on_promote is a parameter of pgsql RA.
# pcs resource update pgsql restart_on_promote=false
--
Regards,
Takehiro Matsushima
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/lin
tart PostgreSQL manually(It runs as master, confirm you can
connect to it using psql)
5. Stop PostgreSQL
6. Start pacemaker.
Regards,
Takehiro Matsushima
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/lin
Hi.
Let me ask some things,
Can pz01 run under pacemker, without pz02?
Something differed from running only pz02?
Could you find some hints in the logs of each postgresql(and pgstartup.log)?
Good-luck,
Takehiro Matsushima
___
Linux-HA mailing list
> 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
Thank you, it is no problem.
> I try start pgsql and cleanup pgsq. And got same error. Why RA dow
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 Attr
sorry, it is not correct.
> "tail -n 1 /etc/postgresql/9.3/main/postgresql.conf"
"tail -n 3 /etc/postgresql/9.3/main/postgresql.conf" is correct.
--
Regards,
Takehiro Matsushima
___
Linux-HA mailing list
Linux-HA@lists.linux-ha
I used resource-agents contained in default debian repositories, and
replace pgsql RA with this;
https://raw.github.com/ClusterLabs/resource-agents/a6f4ddf76cb4bbc1b3df4c9b6632a6351b63c19e/heartbeat/pgsql
but, maybe it is same yours.
> But I can't udnerstand what this code will do:
>
]
Masters: [ pg2 ]
Slaves: [ pg3 ]
Stopped: [ pgsql:0 ]
Node Attributes:
* Node pg1:
+ master-pgsql:0: -INFINITY
+ pgsql-data-status : DISCONNECT
+ pgsql-status : STOP
* Node pg2:
+ master-pgsql:1
us : STREAMING|ASYNC
>> > + pgsql-status : HS:async
>> > * Node b.mydomain.com:
>> > + pgsql-data-status : STREAMING|ASYNC
>> > + pgsql-status : HS:async
>> >
>> > Migration s
; Migration summary:
> * Node a.mydomain.com:
> * Node b.mydomain.com:
> * Node c.mydomain.com:
>
> Failed actions:
> pgsql:0_monitor_0 (node=a.mydomain.com, call=31, rc=2,
> status=complete): invalid parameter
> pgsql:0_monitor_0 (node=b.mydomain.com, call=26, rc=2,
> sta
\
> op monitor interval="10s" timeout="60s" on-fail="restart" \
> op stop interval="0s" timeout="60s" on-fail="block" \
> meta target-role="Started"
> group master pgsql-master-ip
> ms msPostgresql p
Hello,
1. How is it work stably after that? Failover works correctly, too?
2. I see, in this case, specify rep_mode="async" in crm config then
all slaves run in async.
--
Regards,
Takehiro Matsushima
___
Linux-HA mailing list
Linux-HA@l
is broken.
So, the 3rd node is set Async intentionally, Mr. MATSUO answered.
And also refer followings he said.
https://github.com/ClusterLabs/resource-agents/commit/55494b5052f540030938733ec4729cc37ac64a8c
https://github.com/t-matsuo/resource-agents/is
?
I'm sorry if you done.
Regards,
Takehiro Matsushima
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
s required. :)
regards,
Takehiro Matsushima
2013/11/13 Ahmed Munir :
> Hi All,
>
> I would like to know, is it possible to change the ping port as 5060 using
> ocf::pingd? Means to say need to send ping at port 5060.
>
> If it is possible please advise what parameters do I need to
15 matches
Mail list logo
