pacemaker+corosync+drbdでのクラスタ環境の構築について

Question

リソースとしてVIP、ディレクトリマウント、postgre起動をマイグレーションさせます。VIP、ディレクトリマウントはうまくいったのですがposgreだけがうまくいきません。ご教示お願い致します。
1．crm_mon -rfA -1の結果 ※crm resource cleanup prmDBはおこなっております。
Online: [ db-sr01 db-sr02 ]

Full list of resources:

Resource Group: grpTrac
prmVIP (ocf:💓IPaddr2): Started db-sr01
prmFS (ocf:💓Filesystem): Started db-sr01
prmDB (ocf:💓pgsql): Stopped
Master/Slave Set: msDrbd [drbd]
Masters: [ db-sr01 ]
Slaves: [ db-sr02 ]
Clone Set: clnDiskd1 [prmDiskd1]
Started: [ db-sr01 db-sr02 ]
Clone Set: clnPing [prmPing]
Started: [ db-sr01 db-sr02 ]

Node Attributes:

• Node db-sr01.slan4test.local:
  • default_ping_set : 100
  • diskcheck_status : normal
  • master-drbd : 10000
• Node db-sr02.slan4test.local:
  • default_ping_set : 100
  • diskcheck_status : normal
  • master-drbd : 1000

Migration Summary:

• Node db-sr01:
  prmDB: migration-threshold=1 fail-count=1000000 last-failure='Wed Aug 31 15:21:02 2016'
• Node db-sr02:
  prmDB: migration-threshold=1 fail-count=1000000 last-failure='Wed Aug 31 15:23:03 2016'

Failed Actions:

• prmDB_start_0 on db-sr01 'unknown error' (1): call=43, status=Timed Out, exitreason='none',
  last-rc-change='Wed Aug 31 15:19:02 2016', queued=0ms, exec=120005ms
• prmDB_start_0 on db-sr02 'unknown error' (1): call=49, status=Timed Out, exitreason='none',
  last-rc-change='Wed Aug 31 15:21:03 2016', queued=0ms, exec=120005ms

2．crm設定ファイルのpostgresqlの部位 ※ディレクトリはデフォルトです。
primitive prmDB ocf💓pgsql
params
pgctl="/usr/pgsql-9.3/bin/pg_ctl"
psql="/usr/pgsql-9.3/bin/psql"
pgdata="/var/lib/pgsql/9.3/data"
start_opt="-p 5432"
pgdba="postgres"
pgport="5432"
pgdb="template1"
op start interval="0s" timeout="120s" on-fail="restart"
op monitor interval="10s" timeout="10s" on-fail="restart"
op stop interval="0s" timeout="20s" on-fail="ignore"

3.db-sr01の/var/log/cluster/corosync.log
db-sr01. pengine: notice: process_pe_message: Calculated Transition 9: /var/lib/pacemaker/pengine/pe-input-320.bz2
Aug 31 16:27:28 [38273] db-sr01. crmd: info: do_state_transition: State transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS cause=C_IPC_MESSAGE origin=handle_response ]
Aug 31 16:27:28 [38273] db-sr01. crmd: info: do_te_invoke: Processing graph 9 (ref=pe_calc-dc-1472628448-88) derived from /var/lib/pacemaker/pengine/pe-input-320.bz2
Aug 31 16:27:28 [38273] db-sr01. crmd: notice: te_rsc_command: Initiating action 7: stop prmDB_stop_0 on db-sr02.slan4test.local
Aug 31 16:27:28 [38268] db-sr01. cib: info: cib_perform_op: Diff: --- 0.14.62 2
Aug 31 16:27:28 [38268] db-sr01. cib: info: cib_perform_op: Diff: +++ 0.14.63 (null)
Aug 31 16:27:28 [38268] db-sr01. cib: info: cib_perform_op: + /cib: @num_updates=63
Aug 31 16:27:28 [38268] db-sr01. cib: info: cib_perform_op: + /cib/status/node_state[@id='3232291618']/lrm[@id='3232291618']/lrm_resources/lrm_resource[@id='prmDB']/lrm_rsc_op[@id='prmDB_last_0']: @operation_key=prmDB_stop_0, @operation=stop, @transition-key=7:9:0:771aad93-6768-44c9-a256-5576872e7c91, @transition-magic=0:0;7:9:0:771aad93-6768-44c9-a256-5576872e7c91, @call-id=50, @rc-code=0, @op-status=0, @last-run=1472628448, @last-rc-change=1472628448, @exec-time=98
Aug 31 16:27:28 [38268] db-sr01. cib: info: cib_process_request: Completed cib_modify operation for section status: OK (rc=0, origin=db-sr02.slan4test.local/crmd/29, version=0.14.63)
Aug 31 16:27:28 [38273] db-sr01. crmd: info: match_graph_event: Action prmDB_stop_0 (7) confirmed on db-sr02.slan4test.local (rc=0)
Aug 31 16:27:28 [38273] db-sr01. crmd: notice: run_graph: Transition 9 (Complete=4, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-320.bz2): Complete
Aug 31 16:27:28 [38273] db-sr01. crmd: info: do_log: FSA: Input I_TE_SUCCESS from notify_crmd() received in state S_TRANSITION_ENGINE
Aug 31 16:27:28 [38273] db-sr01. crmd: notice: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL origin=notify_crmd ]
Aug 31 16:27:33 [38268] db-sr01. cib: info: cib_process_ping: Reporting our current digest to db-sr01.slan4test.local: 3899259ea248a97c3987289289195c9a for 0.14.63 (0x1a69540 0)

Answer 1

pgsql リソースの start でタイムアウトになっていますね。
ログ(/var/lib/pgsql/9.3/data/pg_log/ 以下)に何か原因が出力されていないか、手動で postgres プロセスを起動できるか、確認ください。

/var/log/cluster/corosync.log を調べるのであれば、エラーが発生した 15:21:02 ころからタイムアウト時間(120秒)前の 15:19:02 の間を、「prmDB_start_0」、「rc=(0以外の数字)」、「Timeout」をキーワードに。
タイムアウトしたことは出力されますが、その原因まではわからないかもしれません。