[pgpool-general: 481] Re: abnormal behavior pgpool on drop

[Tatsuo Ishii]

I don't know about your configurations where each server is
residing. So I cannot say anything from what you showed below...
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> I see it in log for example:
> 
> On master db:
> in i see this /var/log/postgresql/postgresql-9.1-main.log
> 2012-05-21 15:02:21 MSK @  LOG:  received fast shutdown request
> 2012-05-21 15:02:21 MSK @  LOG:  aborting any active transactions
> 
> in /var/log/auth.log i see this:
> May 21 15:02:21 pre-db2 sshd[6805]: debug1: PAM: initializing for "postgres"
> May 21 15:02:21 pre-db2 sshd[6805]: debug1: PAM: setting PAM_RHOST to
> "dbbalancer1"
> May 21 15:02:21 pre-db2 sshd[6805]: debug1: PAM: setting PAM_TTY to "ssh"
> May 21 15:02:21 pre-db2 sshd[6805]: Failed none for postgres from
> 10.2.141.51 port 33031 ssh2
> May 21 15:02:21 pre-db2 sshd[6805]: debug1: Checking blacklist file
> /usr/share/ssh/blacklist.RSA-2048
> May 21 15:02:21 pre-db2 sshd[6805]: debug1: Checking blacklist file
> /etc/ssh/blacklist.RSA-2048
> May 21 15:02:21 pre-db2 sshd[6805]: debug1: temporarily_use_uid: 105/109
> (e=0/0)
> May 21 15:02:21 pre-db2 sshd[6805]: debug1: trying public key file
> /var/lib/postgresql/.ssh/authorized_keys
> May 21 15:02:21 pre-db2 sshd[6805]: debug1: fd 4 clearing O_NONBLOCK
> May 21 15:02:21 pre-db2 sshd[6805]: debug1: matching key found: file
> /var/lib/postgresql/.ssh/authorized_keys, line 2
> 
> I run pgpool on host dbbalancer1 under user postgres.  And configure pgpool
> script work under postgres and used ssh keys.
> 
> And this situation repeated twice.
> 
> 
> 
> 
> 
> 
> 2012/5/21 Tatsuo Ishii <ishii at postgresql.org>
> 
>> > I have pgpool-II version 3.1.3 installed and three db postgresql 9.1.3 in
>> > streaming replication. When i try to drop database i see this in pgpool
>> log:
>> >
>> > 2012-05-21 15:01:48 LOG:   pid 15484: pool_send_and_wait: Error or notice
>> > message from backend: : DB node id: 1 backend pid: 6769 statement: DROP
>> > DATABASE xxx; message: database "xxx" is being accessed by other users
>> > 2012-05-21 15:02:20 LOG:   pid 26326: postmaster on DB node 1 was
>> shutdown
>> > by administrative command
>> > 2012-05-21 15:02:20 LOG:   pid 26326: degenerate_backend_set: 1 fail over
>> > request from pid 26326
>> > 2012-05-21 15:02:20 LOG:   pid 4975: starting degeneration. shutdown host
>> > 10.141.2.54(5432)
>> > 2012-05-21 15:02:20 LOG:   pid 4975: Restart all children
>> > 2012-05-21 15:02:20 LOG:   pid 4975: execute command:
>> > /etc/pgpool.d/failover.sh 1 10.141.2.54 5432
>> /var/lib/postgresql/9.1/main 0
>> > 10.141.2.53 0 1
>> > 2012-05-21_15:02:20 failover: Master failed at 10.141.2.54 (0). New
>> master
>> > is 10.141.2.53 (0)
>> > 2012-05-21_15:02:20 failover: New master start triggered.
>> >
>> > Why pgpool initiated failover procedure on statement drop database? I add
>> > drop statement in black_function_list may be this helps me.
>>
>> Why do you think drop database initiated failover? The failover
>> happend 32 seconds after drop database error.
>> --
>> Tatsuo Ishii
>> SRA OSS, Inc. Japan
>> English: http://www.sraoss.co.jp/index_en.php
>> Japanese: http://www.sraoss.co.jp
>>
> 
> 
> 
> -- 
> С уважением Селявка Евгений