Re: Pacemaker dynamic membership

I'm sorry I had not helped.
can you show the files：

1. cat /etc/cluster/cluster.conf
2. ls /etc/corosync/service.d/ .if the directory is not empty , show
config files
3. pcs cluster cib /tmp/cib.cfg && cat /tmp/cib.cfg
4. cat /etc/corosync/corosync.conf
5. tailf -n 100 /var/log/cluster/corosync.log
6. /var/log/message

On 2015年10月12日 15:56, Nikolay Popov wrote:
> Hi, Wensheng.
>
> Thanks for the advice.
> But it's not working.
>
> 10.10.2015 11:03, 张文升 пишет:
>> hi ：
>> I also do not skilled, but can give you some advice. We can discuss.
>>
>> first：
>> pcs resource update postgresql node_list="pi01 pi02 pi03........"
>>
>> then on pi05：
>> 1、stop pacemaker
>> /etc/init.d/pacemaker stop
>>
>> 2、find “PGSQL.lock” file and remove it，eg.,
>>
>> rm -f /tmp/PGSQL.lock
>>
>> rm -f /var/lib/pgsql/tmp/PGSQL.lock
>>
>> 3、start corosync and pacemaker
>>
>>
>>
>> On 2015年10月07日 15:44, Nikolay Popov wrote:
>>> pgsql_start_0 on pi05 'unknown error' (1): call=27, status=complete,
>>> exitreason='My data may be
>>> inconsistent. You have to remove /var/lib/pgsql/tmp/PGSQL.lock file
>>> to force start.',
>>> last-rc-change='Fri Oct 2 17:04:10 2015', queued=0ms, exec=2553ms
>> Nikolay Popov n(dot)popov(at)postgrespro(dot)ru Postgres Professional:
>> http://www.postgrespro.com The Russian Postgres Company
>

--
----------------------
张文升 | PostgreSQL DBA
----------------------