[Pgpool-general] Re:read_message_length problems

[Tatsuo Ishii]

> Hi
> Thanks for your quick reply. and sorry for asking such a fundamental issue.
> I turned pgpool on with -d option. then I have got a message below.
> 
> pgpool -d -n &
> [1] 25056
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: listen_addresses
> [root at dc1 pgsql]# 2005-10-12 18:15:52 DEBUG: pid 25056: value: '*' kind: 4
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: port
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 9999 kind: 2
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: socket_dir
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: '/tmp' kind: 4
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: backend_host_name
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: '' kind: 4
> 2005-10-12 18:15:52 DEBUG: pid 25056: ::
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: backend_port
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 5432 kind: 2
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: backend_socket_dir
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: '/tmp' kind: 4
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: secondary_backend_host_name
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: '192.168.1.206' kind: 4
> 2005-10-12 18:15:52 DEBUG: pid 25056: :192.168.1.206:
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: secondary_backend_port
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 5433 kind: 2
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: num_init_children
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 1 kind: 2
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: max_pool
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 4 kind: 2
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: child_life_time
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 300 kind: 2
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: connection_life_time
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 0 kind: 2
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: logdir
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: '/tmp' kind: 4
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: replication_mode
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: true kind: 1
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: replication_strict
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: true kind: 1
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: replication_timeout
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 5000 kind: 2
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: load_balance_mode
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: true kind: 1
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: weight_master
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 0.5 kind: 3
> 2005-10-12 18:15:52 DEBUG: pid 25056: weight_master: 0.500000
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: weight_secondary
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 0.5 kind: 3
> 2005-10-12 18:15:52 DEBUG: pid 25056: weight_secondary: 0.500000
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: replication_stop_on_mismatch
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: false kind: 1
> 2005-10-12 18:15:52 DEBUG: pid 25056: replication_stop_on_mismatch: 0
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: reset_query_list
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 'ABORT; RESET ALL; SET SESSION 
> AUTHORIZATION DEFAULT' kind: 4
> 2005-10-12 18:15:52 DEBUG: pid 25056: extract_string_tokens: token: ABORT
> 2005-10-12 18:15:52 DEBUG: pid 25056: extract_string_tokens: token:  RESET 
> ALL
> 2005-10-12 18:15:52 DEBUG: pid 25056: extract_string_tokens: token:  SET 
> SESSION AUTHORIZATION DEFAULT
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: print_timestamp
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: true kind: 1
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: master_slave_mode
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: false kind: 1
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: connection_cache
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: true kind: 1
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: health_check_timeout
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 20 kind: 2
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: health_check_period
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 0 kind: 2
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: health_check_user
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: 'nobody' kind: 4
> 2005-10-12 18:15:52 DEBUG: pid 25056: key: insert_lock
> 2005-10-12 18:15:52 DEBUG: pid 25056: value: false kind: 1
> 2005-10-12 18:15:52 DEBUG: pid 25056: weight: 1073741823
> 2005-10-12 18:15:52 DEBUG: pid 25057: I am 25057
> 2005-10-12 18:15:52 LOG:   pid 25056: pgpool successfully started
> 
> and when i try to connect from pgadmin3 i get :
> 
> >2005-10-12 15:44:23 DEBUG: pid 21207: I am 21207 accept fd 6
> >2005-10-12 15:44:23 DEBUG: pid 21207: Protocol Major: 1234 Minor: 5679
> >database:  user:
> >2005-10-12 15:44:23 DEBUG: pid 21207: SSLRequest: sent N; retry startup
> >2005-10-12 15:44:23 DEBUG: pid 21207: Protocol Major: 3 Minor: 0 database:
> >nittel user: nittel
> >2005-10-12 15:44:23 DEBUG: pid 21207: connecting postmaster Unix domain
> >socket: /tmp/.s.PGSQL.5432
> >2005-10-12 15:44:23 DEBUG: pid 21207: connected to postmaster Unix domain
> >socket: /tmp/.s.PGSQL.5432 fd: 7
> >2005-10-12 15:44:23 DEBUG: pid 21207: read_message_length: lenghth: 12
> >2005-10-12 15:44:23 ERROR: pid 21207: read_message_length: length does not
> >match between backends master(12) secondary(8)
> 
> I have checked values of server_version, server_encoding, client_encoding, 
> is_superuser, session_authorization, DateStyle, TimeZone, and 
> integer_datetimes  but it seems both servers have the same values.
> is there anywhere i should look at?
> Thank you for help.

Ok. I lose. Can you turn off the replication mode and show me the
debug messages for two servers?
--
SRA OSS, Inc. Japan
Tatsuo Ishii