<br><br><div class="gmail_quote">2013/3/4 Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@postgresql.org" target="_blank">ishii@postgresql.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">> Hi Tatsuo, as promised I've tested pgpool 3.2.3 on AIX 5.2<br>
><br>
> it behaves in a really strange way, at the beginning when I was starting<br>
> pgpool it was seeming to be working pretty fine,<br>
> after some stop and start it became to behave really strangely.<br>
><br>
> it seems to mess with some cached status does exists some cache_status<br>
> file? i removed backend files .s.PGSQL.9898 % .s.PGSQL.9999 butit doesn't<br>
> change anything.<br>
<br>
</div>I don't think so. The cached status file is located at<br>
/tmp/pgpool_status in your case. From the log, it says:<br>
<br>
2013-03-04 17:44:18 ERROR: pid 72000: Could not read backend status file as /tmp/pgpool_status. reason: No such file or directory<br>
<br>
So pgpool did not read cached status and this is normal. (BTW, if you<br>
want to be sure to ignore the status file, you could start pgpool with<br>
-D option).<br>
<br><br></blockquote><div> </div><div>Yes the things you say are right, the strange thing is that the /tmp/pgpool_status file exists but pgpool is not able to read it, it's strange cause user has right to read and write on it. any way after that I started using the -D option that file has been discarded automatically by pgpool process but this didn't help.<br>
</div><div>My suspect of a strange behaviour cause of some kind of cached status comes from the fact that in the very beginning, when I was having the same configuration that I'm having now all was working really fine.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>