Postgres PAF setup

Поиск
Список
Период
Сортировка
От Andrew Edenburn
Тема Postgres PAF setup
Дата
Msg-id e3c27cb8039544c9af6849df2c494e95@gm.com
обсуждение исходный текст
Ответы Re: Postgres PAF setup  (Adrien Nayrat <adrien.nayrat@anayrat.info>)
Re: Postgres PAF setup  ("Jehan-Guillaume (ioguix) de Rorthais" <ioguix@free.fr>)
Список pgsql-general

I am having issues with my PAF setup.  I am new to Postgres and have setup the cluster as seen below. 

I am getting this error when trying to start my cluster resources.

 

Master/Slave Set: pgsql-ha [pgsqld]

     pgsqld     (ocf::heartbeat:pgsqlms):       FAILED dcmilphlum224 (unmanaged)

     pgsqld     (ocf::heartbeat:pgsqlms):       FAILED dcmilphlum223 (unmanaged)

pgsql-master-ip        (ocf::heartbeat:IPaddr2):       Started dcmilphlum223

 

Failed Actions:

* pgsqld_stop_0 on dcmilphlum224 'unknown error' (1): call=239, status=complete, exitreason='Unexpected state for instance "pgsqld" (returned 1)',

    last-rc-change='Mon Apr 23 13:11:17 2018', queued=0ms, exec=95ms

* pgsqld_stop_0 on dcmilphlum223 'unknown error' (1): call=248, status=complete, exitreason='Unexpected state for instance "pgsqld" (returned 1)',

    last-rc-change='Mon Apr 23 13:11:17 2018', queued=0ms, exec=89ms

 

cleanup and clear is not fixing any issues and I am not seeing anything in the logs.  Any help would be greatly appreciated.

 

 

My cluster config

root@dcmilphlum223:/usr/lib/ocf/resource.d/heartbeat# crm config

crm(live)configure# show

node 1: dcmilphlum223

node 2: dcmilphlum224 \

        attributes pgsqld-data-status=LATEST

primitive pgsql-master-ip IPaddr2 \

        params ip=10.125.75.188 cidr_netmask=23 nic=bond0.283 \

        op monitor interval=10s \

        meta target-role=Started

primitive pgsqld pgsqlms \

        params pgdata="/pgsql/data/pg7000" bindir="/usr/local/pgsql/bin" pgport=7000 start_opts="-c config_file=/pgsql/data/pg7000/postgresql.conf" recovery_template="/pgsql/data/pg7000/recovery.conf.pcmk" \

        op start interval=0 timeout=60s \

        op stop interval=0 timeout=60s \

        op promote interval=0 timeout=30s \

        op demote interval=0 timeout=120s \

        op monitor enabled=true interval=15s role=Master timeout=10s \

        op monitor enabled=true interval=16s role=Slave timeout=10s \

        op notify interval=0 timeout=60s \

        meta

ms pgsql-ha pgsqld \

        meta notify=true target-role=Stopped

property cib-bootstrap-options: \

        have-watchdog=false \

        dc-version=1.1.14-70404b0 \

        cluster-infrastructure=corosync \

        cluster-name=pgsql_cluster \

        stonith-enabled=false \

        no-quorum-policy=ignore \

        migration-threshold=1 \

        last-lrm-refresh=1524503476

rsc_defaults rsc_defaults-options: \

        migration-threshold=5 \

        resource-stickiness=10

crm(live)configure#

 

 

My pcs Config

Corosync Nodes:

dcmilphlum223 dcmilphlum224

Pacemaker Nodes:

dcmilphlum223 dcmilphlum224

 

Resources:

Master: pgsql-ha

  Meta Attrs: notify=true target-role=Stopped

  Resource: pgsqld (class=ocf provider=heartbeat type=pgsqlms)

   Attributes: pgdata=/pgsql/data/pg7000 bindir=/usr/local/pgsql/bin pgport=7000 start_opts="-c config_file=/pgsql/data/pg7000/postgresql.conf" recovery_template=/pgsql/data/pg7000/recovery.conf.pcmk

   Operations: start interval=0 timeout=60s (pgsqld-start-0)

               stop interval=0 timeout=60s (pgsqld-stop-0)

               promote interval=0 timeout=30s (pgsqld-promote-0)

               demote interval=0 timeout=120s (pgsqld-demote-0)

               monitor role=Master timeout=10s interval=15s enabled=true (pgsqld-monitor-interval-15s)

               monitor role=Slave timeout=10s interval=16s enabled=true (pgsqld-monitor-interval-16s)

               notify interval=0 timeout=60s (pgsqld-notify-0)

Resource: pgsql-master-ip (class=ocf provider=heartbeat type=IPaddr2)

  Attributes: ip=10.125.75.188 cidr_netmask=23 nic=bond0.283

  Meta Attrs: target-role=Started

  Operations: monitor interval=10s (pgsql-master-ip-monitor-10s)

 

Stonith Devices:

Fencing Levels:

 

Location Constraints:

Ordering Constraints:

Colocation Constraints:

 

Resources Defaults:

migration-threshold: 5

resource-stickiness: 10

Operations Defaults:

No defaults set

 

Cluster Properties:

cluster-infrastructure: corosync

cluster-name: pgsql_cluster

dc-version: 1.1.14-70404b0

have-watchdog: false

last-lrm-refresh: 1524503476

migration-threshold: 1

no-quorum-policy: ignore

stonith-enabled: false

Node Attributes:

dcmilphlum224: pgsqld-data-status=LATEST

 

 

cid:0__=0ABBF137DFA7B0688f9e8a93df93869091@local
Andrew A Edenburn
General Motors

Hyperscale Computing & Core Engineering
Mobile Phone: +01-810-410-6008

30009 Van Dyke Ave

Warren, MI. 48090-9026

Cube: 2w05-21
mailto:andrew.edenburn@gm.com

Web Connect SoftPhone 586-986-4864

 



Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.

Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.
Вложения

В списке pgsql-general по дате отправления:

Предыдущее
От: "Sven R. Kunze"
Дата:
Сообщение: Re: Rationale for aversion to the central database?
Следующее
От: Thomas Poty
Дата:
Сообщение: Re: Using the public schema