[Pgpool-general] problem with backendkey data
Takumi Okubo
t-okubo at tsysd.net
Tue Oct 18 09:51:35 GMT 2005
Hi
i am having an error that i have two servers(say serv1 and serv2), both have
postgreSQL 8.0.3
and pgpool(2.6.3) is running on the primary server(serv1).
i have been trying to access the DBs via pgpool and i have had errors below:
2005-10-18 19:40:41 DEBUG: pid 9991: I am 9991 accept fd 6
2005-10-18 19:40:41 DEBUG: pid 9991: Protocol Major: 3 Minor: 0 database:
nittel user: postgres
2005-10-18 19:40:41 DEBUG: pid 9991: read_message_length: lenghth: 8
2005-10-18 19:40:41 DEBUG: pid 9991: trying clear text password
authentication
2005-10-18 19:40:41 ERROR: pid 9991: do_clear_text_password: failed to read
password packet "p"
2005-10-18 19:40:41 ERROR: pid 9991: pool_do_auth: backend does not return
authenticaton ok
2005-10-18 19:40:50 DEBUG: pid 9991: I am 9991 accept fd 6
2005-10-18 19:40:50 DEBUG: pid 9991: Protocol Major: 3 Minor: 0 database:
nittel user: postgres
2005-10-18 19:40:50 DEBUG: pid 9991: read_message_length: lenghth: 8
2005-10-18 19:40:50 DEBUG: pid 9991: trying clear text password
authentication
2005-10-18 19:40:50 DEBUG: pid 9991: read_message_length: lenghth: 65
2005-10-18 19:40:50 ERROR: pid 9991: pool_do_auth: invalid messages
length(65) for BackendKeyData
both DBs have the same data and a postgres.cof file. it seems that the two
postmasters do not send the same backendkeydata to pgpool but postmasters
have no errors.....
does anyone have any ideas?
Takumi Okubo
Total Systems Development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://pgfoundry.org/pipermail/pgpool-general/attachments/20051018/b7f1e3ed/attachment.html
More information about the Pgpool-general
mailing list