> >> ... Sometimes (not always) pgPool hangs after these > >> tests. That means accessing the database through pgPool is not possible > >> any more. Attemps to access the database do not result in an error > >> message but pgPool does not answer (at least not in reasonable time). > >> However accessing the database directly still works perfect. If I > >> restart pgPool everything works fine again. > > Following on from my previous post - I've had this occur with PgPool > 2.2.2 as previously mentioned. > > I didn't have debug mode turned on at the time, but here's an strace > for what it's worth. I'll turn on debugging and wait for this to > occur again and hopefully provide more useful info.
[snip] No particular unusual things found in your trace log. It would be nice if you could send me a little bit more trace. I'm interested in what happend for pid 2587 and 2588 afterwards. -- Tatsuo Ishii SRA OSS, Inc. Japan _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
