> --- On Tue, 11/1/11, Toshihiro Kitagawa <[email protected]> wrote: >> Glyn Astill <[email protected]> >> wrote: >> >> > --- On Tue, 11/1/11, Tatsuo Ishii <[email protected]> >> wrote: >> > >> > > > The previous error with the >> > > pool_passwd appears to have gone on startup, but >> it still >> > > appears when the server is stopped. >> > > >> > > Can you please explain more detail? >> > > >> > >> > When I stop pgpool-II I get the following message: >> > >> > 2011-01-11 09:44:18 ERROR: pid 13462: >> pool_init_pool_passwd: couldn't open >> /usr/local/etc/pool_passwd. reason: Permission denied >> > stop request sent to pgpool. waiting for >> termination....done. >> > >> > This doesn't seem to cause a problem, so is it >> expected behaviour? >> > >> > > > Also I'm seeing a problem where a namaed >> prepared >> > > statement gets deallocated but pgpool thinks it >> still exists >> > > when my app tries to recreate it. >> > > > >> > > > The output of the log is here: >> > > > >> > > > http://www.privatepaste.com/c3068423a3 >> > > > >> > > > Was thinking it could be something to do >> with this >> > > change? : >> > > > >> > > > http://pgfoundry.org/pipermail/pgpool-committers/2010-October/001507.html >> > > >> > > That change was made by Toshihiro. Toshihiro? >> > >> >> I think that change is not the cause of this issue. >> >> I found a bug that happen when "DEALLOCATE" by simple query >> protocol >> was sent after extended query protocol was sent. >> >> I created a temporary patch for V3_0_STABLE until next >> version up. >> Can you please try including patches? >> > > I've applied both patches, but I'm not seeing any changes to either issue. > > I've attached an strace log where I've:
Ok, I checked the log and bottom line is, the error: /usr/local/etc/pool_passwd. reason: Permission denied is harmless. This just said pgpool tried to create pool_passwrd under /usr/local/etc but failed because the directory does not allow pgpool to create files. So you could either: 1) Ignore the error message 2) Change the directory permission of /usr/local/etc 3) Touch file /usr/local/etc/pool_passwd then change the file permission to allow pgpool to open with the file with writing -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > 1) started pgpool > 2) connected from a client > 3) had that client issue the prepare, deallocate and prepare to get the error > 4) killed pgpool > > Let me know if this is any use. > > Thanks > Glyn > > > _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
