[pgpool-hackers: 639] Re: [pgpool-II 0000119]: Signal might be sent to pid=1 (init process) in send_failback_request()

Tatsuo Ishii ishii at postgresql.org
Thu Nov 6 08:08:30 JST 2014


Usama,

Can you please take care of this?

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

From: pgpool Bug Tracker <bugtracker at pgpool.net>
Subject: [pgpool-II 0000119]: Signal might be sent to pid=1 (init process) in send_failback_request()
Date: Wed, 5 Nov 2014 11:00:47 +0900
Message-ID: <3f27fc6842fadad83a5df50881f75935 at www.pgpool.net>

> 
> The following issue has been SUBMITTED. 
> ====================================================================== 
> http://www.pgpool.net/mantisbt/view.php?id=119 
> ====================================================================== 
> Reported By:                bow.fujita
> Assigned To:                
> ====================================================================== 
> Project:                    pgpool-II
> Issue ID:                   119
> Category:                   Bug
> Reproducibility:            sometimes
> Severity:                   minor
> Priority:                   normal
> Status:                     new
> ====================================================================== 
> Date Submitted:             2014-11-05 11:00 JST
> Last Modified:              2014-11-05 11:00 JST
> ====================================================================== 
> Summary:                    Signal might be sent to pid=1 (init process) in
> send_failback_request()
> Description: 
> I built pgpool-II 3.2.6 from source code and run as streaming-replication mode.
> There are two backend PostgreSQL 9.2.4. One is localhost and another is remote.
> While I was testing failover and failback features of pgpool-II by restarting
> each PostgresSQL server repeatedly, Linux suddenly start shutting down.
> 
> My environment is not actual Debian distribution but custom (embedded) Linux
> based on Debian and pgpool is running as root.
> 
> I investigated why Linux would be shut down and found that init process (pid=1)
> received SIGUSR1 upon segfalt occurred in child process of pgpool. Updating
> pgpool to 3.2.9 wasn't fixed unfortunately.
> So I patched some debug codes to pgpool in order to figure out which code sent
> SIGUSR1 to init process, and I found that it was in send_failback_request() in
> main.c.
> 
> My assumption is, send_failback_request() was called in pool process, however,
> that pool process had been zombie so ppid would be 1.
> 
> Here I attach the patch to prevent kill() from sending a signal to init process.
> This patch replaces all kill() with pool_kill() in source tree because I'm not
> sure which kill() is suspicious.
> 
> Regards
> 
> 
> ====================================================================== 
> 
> Issue History 
> Date Modified    Username       Field                    Change               
> ====================================================================== 
> 2014-11-05 11:00 bow.fujita     New Issue                                    
> 2014-11-05 11:00 bow.fujita     File Added: pool_kill.patch                    
> ======================================================================
> 


More information about the pgpool-hackers mailing list