[Pgpool-general] pool_read_message_length2: message length (25) in slot 2 does not match with slot 0(30)

Tatsuo Ishii ishii at sraoss.co.jp
Sat Jan 15 04:17:14 UTC 2011


> First I have had pgpool-II with 2 backends. It worked nicely.
> 
> Then I configured pgpool-II with 4 backends. Now, it works, but all of a
> sudden I'm getting this in log:
> 
> 2011-01-14 11:37:00 LOG:   pid 6431: pool_read_message_length2: message
> length (25) in slot 2 does not match with slot 0(30)
> 2011-01-14 11:37:00 LOG:   pid 6431: pool_read_message_length2: message
> length (25) in slot 3 does not match with slot 0(30)
> 2011-01-14 11:37:00 LOG:   pid 6431: pool_read_message_length2: message
> length (25) in slot 2 does not match with slot 0(30)
> 2011-01-14 11:37:00 LOG:   pid 6431: pool_read_message_length2: message
> length (25) in slot 3 does not match with slot 0(30)
> 
> It's only slot 2 or 3, does that match backend ids? Would it mean that
> for some reason for my new backends (2 and 3) the message length is not
> consistent?
> 
> This is weird, as I have identical PG versions on all nodes, and I have
> simply copied entire /etc/postgresql config to all nodes, so the config
> is identical.

There must be something different in node 2, 3 than node 0, 1. We may
be able to find the difference by enabling debug mode (-d).
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp


More information about the Pgpool-general mailing list