[pgcluster: 805] Re: 環境構築に関する質問

myoujint myoujint @ nttdata-hokkaido.co.jp
2005年 9月 2日 (金) 12:41:00 JST


明神です。

Netstatの結果は以下のようになっています。

[postgres @ repl postgres]$ netstat -an|grep 5441
tcp        0      0 0.0.0.0:5441            0.0.0.0:*               LISTEN
unix  2      [ ACC ]     STREAM     LISTENING     989171 /tmp/.s.PGSQL.5441

5443は起動しようとすると以下のようにコンソールに出力され続け、うまく起動でき
ません。
<一部抜粋>
LOG:  could not create IPv6 socket: Address family not supported by protocol
LOG:  database system was shut down at 2005-09-02 12:15:43 JST
LOG:  checkpoint record is at 0/A302E0
LOG:  redo record is at 0/A302E0; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 544; next OID: 17230
FATAL:  DummyProc[0] is in use by PID 17240
LOG:  background writer process (PID 17246) exited with exit code 1
LOG:  terminating any other active server processes
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted at 2005-09-02 12:16:19 JST
LOG:  checkpoint record is at 0/A302E0
LOG:  redo record is at 0/A302E0; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 544; next OID: 17230
LOG:  database system was not properly shut down; automatic recovery in
progressFATAL:  DummyProc[0] is in use by PID 17240
FATAL:  DummyProc[0] is in use by PID 17240
FATAL:  DummyProc[1] is in use by PID 17246
LOG:  background writer process (PID 17250) exited with exit code 0
LOG:  terminating any other active server processes
LOG:  all server processes terminated; reinitializing
LOG:  semctl(130351114, 0, IPC_RMID, ...) failed: Identifier removed
LOG:  semctl(130383883, 0, IPC_RMID, ...) failed: Identifier removed
LOG:  semctl(130416652, 0, IPC_RMID, ...) failed: Identifier removed
LOG:  semctl(130449421, 0, IPC_RMID, ...) failed: Identifier removed
LOG:  semctl(130482190, 0, IPC_RMID, ...) failed: Identifier removed
LOG:  semctl(130514959, 0, IPC_RMID, ...) failed: Identifier removed
LOG:  semctl(130547728, 0, IPC_RMID, ...) failed: Identifier removed
LOG:  database system was interrupted at 2005-09-02 12:16:19 JST
LOG:  checkpoint record is at 0/A302E0
LOG:  redo record is at 0/A302E0; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 544; next OID: 17230
LOG:  database system was not properly shut down; automatic recovery in
progress
LOG:  database system is ready
LOG:  record with zero length at 0/A3031C
LOG:  redo is not required
LOG:  record with zero length at 0/A3031C
LOG:  redo is not required
LOG:  database system is ready
LOG:  background writer process (PID 17256) exited with exit code 1
LOG:  terminating any other active server processes
LOG:  all server processes terminated; reinitializing
LOG:  database system was shut down at 2005-09-02 12:16:20 JST
LOG:  checkpoint record is at 0/A3031C
LOG:  redo record is at 0/A3031C; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 544; next OID: 17230
LOG:  database system is ready
LOG:  database system is ready
LOG:  background writer process (PID 17259) exited with exit code 1
LOG:  terminating any other active server processes
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted at 2005-09-02 12:16:20 JST
LOG:  checkpoint record is at 0/A3031C
LOG:  redo record is at 0/A3031C; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 544; next OID: 17230
LOG:  database system was not properly shut down; automatic recovery in
progress
LOG:  record with zero length at 0/A30358
LOG:  redo is not required
LOG:  database system is ready
LOG:  background writer process (PID 17261) exited with exit code 1
LOG:  terminating any other active server processes
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted at 2005-09-02 12:16:20 JST
LOG:  checkpoint record is at 0/A30358
LOG:  redo record is at 0/A30358; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 544; next OID: 17230
LOG:  database system was not properly shut down; automatic recovery in
progress
LOG:  record with zero length at 0/A30394
LOG:  redo is not required

どちらか先に起動したほうは、正常に起動されたように見えています。
5443は、5441のDATAディレクトリをコピーしてポート番号を変えたものになります。

Postgresql.confの設定値
 listen_addresses = '*'
 port = 5441          <- コピーしたディレクトリの設定は5443

> はせがわといいます。createdbがエラーになっていますので、
> クラスタサーバが起動していないと思います。
>
> netstat -an|grep 5441
> netstat -an|grep 5443
>
> の結果はどうなりますか?
>
> 2005/09/02 11:33:06, "myoujint" <myoujint @ nttdata-hokkaido.co.jp> was
wrote
> > #-------------------------------------------------------------
> > # A setup of Cluster DB(s)
> > #-------------------------------------------------------------
> > <Cluster_Server_Info>
> >     <Host_Name>   repl  </Host_Name>
> >     <Port>                5441        </Port>
> >     <Recovery_Port>       7101        </Recovery_Port>
> >     <LifeCheck_Port>      7201        </LifeCheck_Port>
> > </Cluster_Server_Info>
> > <Cluster_Server_Info>
> >     <Host_Name>   repl  </Host_Name>
> >     <Port>                5443        </Port>
> >     <Recovery_Port>       7101        </Recovery_Port>
> >     <LifeCheck_Port>      7201        </LifeCheck_Port>
> > </Cluster_Server_Info>
> (snip)
> > リングログで、460が似ている事象と思い、createdbを実行しましたが以
> > 下のようなエラーになってしまいます。
> > [postgres @ repl pgsql]$ createdb db1
> > createdb: could not connect to database template1: could not connect to
> > server: そのようなファイルやディレクトリはありません
> >         Is the server running locally and accepting
> >         connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
> >
> > 初歩的なことで申し訳ございませんが、ご教授頂きたくよろしくお願いします。
> >
> >
> >






pgcluster メーリングリストの案内