<div dir="ltr"><div>Hi <span style="color:rgb(80,0,80);font-family:arial,sans-serif;font-size:13px">Yugo,</span></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span style="font-family:arial,sans-serif;font-size:13px">I can't confirm this. Where did you get the pgpoolAdmin, tar ball or rpm?<br></span><font face="arial, sans-serif">And could you please tell me the actual steps to reproduce this?</font></blockquote>
<div><br></div><div>I will try to reinstall it cleanly.</div><div>On my machine I can reproduce this by simply modifying any value under pgpoolAdmin->"pgpool.conf Setting" and clicking "update" button.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> <span style="font-family:arial,sans-serif;font-size:13px">"Disconnect" button executes pcp_detach_node command, and "return" button<br>
</span><span style="font-family:arial,sans-serif;font-size:13px">executes pcp_attach_node command.</span></blockquote><div><br></div><div>Consider such scenario: I have 2 nodes with synchronous replication setting = enabled.</div>
<div>I can then disconnect one node from the pgpool cluster and write data to the remaining node via pgpool. </div><div>Data inconsistency occurs.</div><div>After that I can reconnect the disconnected node and the cluster behaves as if nothing happened even though there is data mismatch.</div>
<div><br></div><div>Is there any protection planned to be implemented from such cases?</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span style="font-family:arial,sans-serif;font-size:13px">Did you add pgpool.pg_ctl parameter into postgresql.conf?<br></span><a href="http://www.pgpool.net/docs/latest/pgpool-en.html#install_functions" target="_blank" style="font-family:arial,sans-serif;font-size:13px">http://www.pgpool.net/docs/latest/pgpool-en.html#install_functions<br>
</a><span style="font-family:arial,sans-serif;font-size:13px">In addition, backends must have a superuser whose name is the same<br></span><span style="font-family:arial,sans-serif;font-size:13px">as pgpoolAdmin's login user.</span></blockquote>
<div><br></div><div>I have added it, but it didn't help. Buttons are disabled and status shows "superuser: unknown".</div><div>The connection string is formed "psql -p X -U X -password X -database template1". For some reason my 9.3 psql can't connect to the pgpool unless I explicitly specify "-h localhost". However, after correcting this issue buttons still remain disabled. </div>
<div><br></div><div>I removed button attribute "disabled" manually and tried to use the buttons. They work, postgres DB can be manipulated. </div><div>For some reason button conditional $reason is_superuser='no', even though i set "isSuperUser()" to return 'yes'.</div>
<div><br></div><div>------------</div><div>Additional problems that I am still experiencing:</div><div>
<p class="">1. If I execute the pcp_recovery_node and interrupt it (ctrl+C), all pcp_* operations become unresponsive. Connections to pgpool:9999 still work though. The only way to make pcp_* work again is to reboot pgpool. </p>
<p class="">2. pgpoolAdmin freezes while pgpool is executing pcp_* operation (e.g. very long pcp_recovery)</p>3. minor: sr_check_password, health_check_password are not starred.</div><div><br></div><div>Cheers,</div><div>
Gintas</div><div><div class="" style="font-family:arial,sans-serif;font-size:13px"></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 21, 2014 at 6:39 AM, Yugo Nagata <span dir="ltr"><<a href="mailto:nagata@sraoss.co.jp" target="_blank">nagata@sraoss.co.jp</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<div class=""><br>
On Fri, 11 Apr 2014 11:40:52 +0100<br>
Gintautas Sulskus <<a href="mailto:gingaz@gmail.com">gingaz@gmail.com</a>> wrote:<br>
<br>
> Hello Yugo,<br>
><br>
> no worries, your replies are much appreciated :)<br>
><br>
> The problem was in the recovery process on a remotely failed node. If I can<br>
> remember clearly, scp operation asked for<br>
> host authorisation ("yes/no") and hung the script. A more verbose message<br>
> providing clues to pinpoint the problem quickly<br>
> would be really great.<br>
><br>
> I updated to pgpoolAdmin 3.3.1 and pgpool 3.3.3. and have noticed an issue:<br>
> 1. If I update pgpool.conf via pgpoolAdmin, it erases wd_lifecheck_method,<br>
> wd_interval, wd_heartbeat_port, wd_heartbeat_keepalive entries.<br>
> 2014-04-11 10:38:59 ERROR: pid 32410: pool_config: wd_lifecheck_method must<br>
> be either "heartbeat" or "query"<br>
> 2014-04-11 10:38:59 ERROR: pid 32410: Unable to get configuration.<br>
> Exiting...<br>
> I have to go to edit them in file. Does it occur to anyone else?<br>
<br>
</div>I can't confirm this. Where did you get the pgpoolAdmin, tar ball or rpm?<br>
And could you please tell me the accual steps to reproduce this?<br>
<div class=""><br>
> pgpoolAdmin questions:<br>
> 1. Could you please explain me, what disconnect/return button should do? I<br>
> assumed, that it would invoke failover/failback functionality.<br>
> E.g. I could "disconnect" server and then on "return" it would<br>
> resynchronise with the cluster automatically (cia pcp_recovery_node).<br>
<br>
</div>"Disconnect" button executes pcp_detach_node command, and "return" button<br>
executes pcp_attach_node command.<br>
<div class=""><br>
><br>
> If my assumptions are wrong, is it possible to call pcp_recovery_node via<br>
> interface?<br>
<br>
</div>Yes. "Recovery" button which appears when the backend goes down executes<br>
pcp_recovery_node command.<br>
<div class=""><br>
><br>
> 2. I could not find any documentation how to enable stop/start/restart<br>
> buttons in pgpoolAdmin. Currently they are disabled.<br>
> I am not certain what settings should enable this.<br>
<br>
</div>Did you add pgpool.pg_ctl parameter into postgresql.conf?<br>
<a href="http://www.pgpool.net/docs/latest/pgpool-en.html#install_functions" target="_blank">http://www.pgpool.net/docs/latest/pgpool-en.html#install_functions</a><br>
In addition, backends must have a superuser whose name is the same<br>
as pgpoolAdmin's login user.<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> Thanks for your patience! :)<br>
><br>
> Cheers,<br>
> Gintautas<br>
><br>
><br>
><br>
> On Thu, Apr 10, 2014 at 8:38 AM, Yugo Nagata <<a href="mailto:nagata@sraoss.co.jp">nagata@sraoss.co.jp</a>> wrote:<br>
><br>
> > Hi Gintautas,<br>
> ><br>
> > I'm sorry for replying late.<br>
> ><br>
> > Recovery scripts are executed by PostgreSQL, so clues would be in log<br>
> > outputs<br>
> > of backend server. Does the scripts have the permission to be executed by<br>
> > postgres user?<br>
> ><br>
> > On Sat, 29 Mar 2014 19:35:32 +0000<br>
> > Gintautas Sulskus <<a href="mailto:gingaz@gmail.com">gingaz@gmail.com</a>> wrote:<br>
> ><br>
> > > Hi Yugo,<br>
> > ><br>
> > > thanks for clarifying! Set up is working.<br>
> > ><br>
> > > I guess that a environment variable defiend in /etc/enviromment is<br>
> > reffered<br>
> > > > in pg_ni_up.sh but this doesn't work well, right?<br>
> > ><br>
> > ><br>
> > > > How about to try 'echo $PATH > /tmp/test ' in pg_ni_up.sh?<br>
> > > > Is the $PATH (or other value) defined in /etc/environment output to<br>
> > > > /tmp/test or not?<br>
> > ><br>
> > ><br>
> > > Even $PATH was not displayed correctly. I presume it was issue with<br>
> > > permissions, although it is not entirely clear to me what has caused this<br>
> > > issue.<br>
> > ><br>
> > ><br>
> > > I am still struggling with pgpool configuration though. Hopefully it is<br>
> > the<br>
> > > last question. Could please anyone give any clues on this problem:<br>
> > ><br>
> > > I have tested my online recovery steps (1st and 2nd recovery) by manually<br>
> > > running scripts. They work just fine. Everything gets logged properly.<br>
> > ><br>
> > > However, when I try to run pcp_recovery_node -d I get:<br>
> > > DEBUG: send: tos="R", len=46<br>
> > > DEBUG: recv: tos="r", len=21, data=AuthenticationOK<br>
> > > DEBUG: send: tos="D", len=6<br>
> > > DEBUG: recv: tos="e", len=20, data=recovery failed<br>
> > > DEBUG: command failed. reason=recovery failed<br>
> > > BackendError<br>
> > > DEBUG: send: tos="X", len=4<br>
> > ><br>
> > > *pgpool log output:*<br>
> > > (pgpool started in debug mode with debug_level=10)<br>
> > > CHECKPOINT in the 1st stage done<br>
> > > starting recovery command: "SELECT pgpool_recovery('pg_1st_recovery',<br>
> > > 'failed_node_ip_address', '/data/postgres/main/')"<br>
> > > exec_recovery: pg_1st_recovery command failed at 1st stage<br>
> > ><br>
> > > *pg_1st_recovery logs:*<br>
> > > none<br>
> > ><br>
> > > *my pgpool configuration:*<br>
> > > recovery_1st_stage_command=pg_1st_recovery<br>
> > > (I expect $1 $2 $3 parameters from pgpool as in examples)<br>
> > ><br>
> > > Could you please give me any hints what could be wrong?<br>
> > > Even a rough direction instead of "BackendError" would be extremely<br>
> > > valuable.<br>
> > ><br>
> > > Thanks,<br>
> > > Gintas<br>
> > ><br>
> > ><br>
> > > On Wed, Mar 26, 2014 at 7:02 AM, Yugo Nagata <<a href="mailto:nagata@sraoss.co.jp">nagata@sraoss.co.jp</a>><br>
> > wrote:<br>
> > ><br>
> > > > Hi,<br>
> > > ><br>
> > > > On Fri, 21 Mar 2014 00:55:51 +0000<br>
> > > > Gintautas Sulskus <<a href="mailto:gingaz@gmail.com">gingaz@gmail.com</a>> wrote:<br>
> > > ><br>
> > > > > Hello,<br>
> > > > ><br>
> > > > > more problems regarding watchdog:<br>
> > > > > On one of the servers I see a log entry: "wd_create_hb_send_socket:<br>
> > > > > setsockopt(SO_BINDTODEVICE) requies root privilege".<br>
> > > > > Any clues what this may be related to? I assume it's permission<br>
> > problem.<br>
> > > ><br>
> > > > You can ignore this message because SO_BINDTODEVICE is not necessary.<br>
> > > ><br>
> > > > ><br>
> > > > > Much appreciated!<br>
> > > > ><br>
> > > > > Gintautas<br>
> > > > ><br>
> > > > ><br>
> > > > > On Fri, Mar 21, 2014 at 12:48 AM, Gintautas Sulskus <<br>
> > <a href="mailto:gingaz@gmail.com">gingaz@gmail.com</a><br>
> > > > >wrote:<br>
> > > > ><br>
> > > > > > Hello,<br>
> > > > > ><br>
> > > > > > ifconfig_path = '/home/ubuntu/apps/scripts'<br>
> > > > > > PgpoolAdmin description of ifconfig_path is: The path of a command<br>
> > to<br>
> > > > > > switch the IP address. I understand it as the path for if_up_cmd<br>
> > > > > > and if_down_cmd commands.<br>
> > > > > ><br>
> > > > > > if_up_cmd = 'pg_ni_up.sh up eth0:1 10.0.1.244 255.255.255.0'<br>
> > > > > > if_down_cmd = 'pg_ni_up.sh down eth0:1'<br>
> > > ><br>
> > > > I guess that a environment variable defiend in /etc/enviromment is<br>
> > reffered<br>
> > > > in pg_ni_up.sh but this doesn't work well, right?<br>
> > > ><br>
> > > > How about to try 'echo $PATH > /tmp/test ' in pg_ni_up.sh?<br>
> > > > Is the $PATH (or other value) defined in /etc/enviroment output to<br>
> > > > /tmp/test or not?<br>
> > > ><br>
> > > > > ><br>
> > > > > ><br>
> > > > > > PS. Is this mailing list the right place to discuss about<br>
> > PgpoolAdmin?<br>
> > > > > > In the latest PgpoolAdmin version "if_*up*_cmd " is described as<br>
> > "The<br>
> > > > > > command to bring *down* the virtual IP" and "if_*down*_cmd" as "The<br>
> > > > > > command to bring *up* the virtual IP". Clearly descriptions are<br>
> > mixed<br>
> > > > up.<br>
> > > > > ><br>
> > > > > > Gintautas<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > On Mon, Mar 10, 2014 at 2:46 AM, Yugo Nagata <<a href="mailto:nagata@sraoss.co.jp">nagata@sraoss.co.jp</a>><br>
> > > > wrote:<br>
> > > > > ><br>
> > > > > >> Hi,<br>
> > > > > >><br>
> > > > > >> On Sun, 9 Mar 2014 03:00:52 +0000<br>
> > > > > >> Gintautas Sulskus <<a href="mailto:gingaz@gmail.com">gingaz@gmail.com</a>> wrote:<br>
> > > > > >><br>
> > > > > >> > Hello,<br>
> > > > > >> ><br>
> > > > > >> > I am trying to set up pgpool watchdog. For virtual IP control my<br>
> > > > plan<br>
> > > > > >> is to<br>
> > > > > >> > use bash scripts (if_up_cmd/if_down_cmd). In my script I use<br>
> > some<br>
> > > > > >> > environment variables.<br>
> > > > > >> ><br>
> > > > > >> > A strange thing occurs here. No matter under what user I run<br>
> > pgpool,<br>
> > > > > >> script<br>
> > > > > >> > can't pick up my custom environment variables from<br>
> > /etc/environment<br>
> > > > > >> > (including customised PATH). It still sees standard binaries<br>
> > like<br>
> > > > > >> ifconfig<br>
> > > > > >> > though.<br>
> > > > > >><br>
> > > > > >> How do you configure pgpool.conf about if_up_cmd, if_down_cmd,<br>
> > > > > >> ifconfig_path?<br>
> > > > > >> pgpool see ifconfig commands on the path specified by these<br>
> > options.<br>
> > > > > >><br>
> > > > > >> ><br>
> > > > > >> > Same script, when run manually by me, works under all users. Any<br>
> > > > ideas<br>
> > > > > >> what<br>
> > > > > >> > can be wrong?<br>
> > > > > >> ><br>
> > > > > >> > The only solution I have come up is to redefine env variables<br>
> > in the<br>
> > > > > >> script.<br>
> > > > > >> ><br>
> > > > > >> > Thanks.<br>
> > > > > >> ><br>
> > > > > >> > Best Regards,<br>
> > > > > >> > Gintas<br>
> > > > > >><br>
> > > > > >><br>
> > > > > >> --<br>
> > > > > >> Yugo Nagata <<a href="mailto:nagata@sraoss.co.jp">nagata@sraoss.co.jp</a>><br>
> > > > > >><br>
> > > > > ><br>
> > > > > ><br>
> > > > > ><br>
> > > > > > --<br>
> > > > > > Best Regards,<br>
> > > > > > Gintautas Sulskus<br>
> > > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > > --<br>
> > > > > Best Regards,<br>
> > > > > Gintautas Sulskus<br>
> > > ><br>
> > > ><br>
> > > > --<br>
> > > > Yugo Nagata <<a href="mailto:nagata@sraoss.co.jp">nagata@sraoss.co.jp</a>><br>
> > > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > --<br>
> > > Best Regards,<br>
> > > Gintautas Sulskus<br>
> ><br>
> ><br>
> > --<br>
> > Yugo Nagata <<a href="mailto:nagata@sraoss.co.jp">nagata@sraoss.co.jp</a>><br>
> ><br>
><br>
><br>
><br>
> --<br>
> Best Regards,<br>
> Gintautas Sulskus<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Yugo Nagata <<a href="mailto:nagata@sraoss.co.jp">nagata@sraoss.co.jp</a>><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Best Regards,<br>Gintautas Sulskus
</div>