<div dir="ltr">Or probably this one? :)<br><br>* Fix to output error message when if_up_cmd fails. (Yugo Nagata) [3.3]<br>
<br>
This is suggested by Sergey Arlashin in [pgpool-general: 2457].<br>
<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 7, 2014 at 2:05 PM, Alexandru Cardaniuc <span dir="ltr"><<a href="mailto:cardaniuc@gmail.com" target="_blank">cardaniuc@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Is it related to the following?<div class=""><br>* Fix to output error message when wd_escalation_command fails with exit<br>
code other than 0 (Yugo Nagata) [3.3]<br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 26, 2014 at 12:08 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"><div>On Tue, 25 Mar 2014 00:18:07 -0700<br>
Alexandru Cardaniuc <<a href="mailto:cardaniuc@gmail.com" target="_blank">cardaniuc@gmail.com</a>> wrote:<br>
<br>
> Also, with version 3.3.2 when I would bring pgpool down on the primary node<br>
> and watchdog would bring delegate_IP up on the secondary node I would see<br>
> in the pgpool.log:<br>
><br>
> 2014-03-25 06:27:31 LOG: pid 6974: wd_escalation: escalated to master<br>
> pgpool successfully<br>
><br>
> And the delegate_IP will be up correctly.<br>
><br>
> Now with version 3.3.3 when that same thing happens, I get in pgpool.log:<br>
><br>
> 2014-03-25 05:11:58 LOG: pid 13889: wd_escalation: escalating to master<br>
> pgpool<br>
> 2014-03-25 05:11:58 DEBUG: pid 13889: exec_ifconfig: wait() failed at<br>
> errno: 10<br>
> 2014-03-25 05:11:58 ERROR: pid 13889: wd_IP_up: ifconfig up failed<br>
> 2014-03-25 05:11:58 DEBUG: pid 13889: wd_declare: send the packet to<br>
> declare the new master<br>
> 2014-03-25 05:11:58 LOG: pid 13889: wd_escalation: escalated to master<br>
> pgpool with some errors<br>
><br>
> But when I check with ifconfig, the delegate_IP was properly brought up<br>
> with ifconfig. Is that a new bug with pgpool 3.3.3?<br>
<br>
</div>Errors if_cmd_up command are checked in 3.3.3. However, wait()'s error of<br>
errno:10 (ECHILD) migth have to be ignored. I'll see detail and fix it.<br>
<div><div><br>
><br>
><br>
> I am not subscribed to pgpool-hackers, so if you respond, please include<br>
> pgpool-general as well.<br>
><br>
> Sincerely,<br>
> Alexandru<br>
><br>
> On Mon, Mar 24, 2014 at 8:49 PM, Alexandru Cardaniuc <<a href="mailto:cardaniuc@gmail.com" target="_blank">cardaniuc@gmail.com</a>>wrote:<br>
><br>
> > Looks like there is a typo in pgpool.spec file.<br>
> ><br>
> > When building:<br>
> > + ./configure --build=x86_64-redhat-linux-gnu<br>
> > --host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu<br>
> > --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin<br>
> > --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share<br>
> > --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec<br>
> > --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man<br>
> > --infodir=/usr/share/info --with-pgsql-includedir=/usr/pgsql-8.4/include/<br>
> > --with-pgsql-lib=/usr/pgsql-8.4/lib --disable-static --with-pam<br>
> > --disable-rpath --sysconfdir=/etc/pgpool-II/<br>
> > configure: WARNING: unrecognized options: --with-pgsql-lib<br>
> ><br>
> > Instead of:<br>
> > %build<br>
> > %configure --with-pgsql-includedir=%{pghome}/include/ \<br>
> > --with-pgsql-lib=%{pghome}/lib \<br>
> > --disable-static --with-pam --disable-rpath \<br>
> > --sysconfdir=%{_sysconfdir}/pgpool-II/<br>
> ><br>
> > Should be:<br>
> > %build<br>
> > %configure --with-pgsql-includedir=%{pghome}/include/ \<br>
> > --with-pgsql-libdir=%{pghome}/lib \<br>
> > --disable-static --with-pam --disable-rpath \<br>
> > --sysconfdir=%{_sysconfdir}/%{name}/<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On Mon, Mar 24, 2014 at 4:15 PM, Yugo Nagata <<a href="mailto:nagata@sraoss.co.jp" target="_blank">nagata@sraoss.co.jp</a>> wrote:<br>
> ><br>
> >> Pgpool Global Development Group is pleased to announce the availability<br>
> >> of pgpool-II 3.3.3, 3.2.8, 3.1.11, 3.0,15, and pgpoolAdmin 3.3.1. These<br>
> >> are the latest stable minor versions of each major versions of pgpool-II.<br>
> >><br>
> >> You can download the source code, installer, RPMs from:<br>
> >> <a href="http://pgpool.net/mediawiki/index.php/Downloads" target="_blank">http://pgpool.net/mediawiki/index.php/Downloads</a><br>
> >><br>
> >><br>
> >> ===============================================================================<br>
> >> pgpool-II 3.3.3, 3.2.8, 3.1.11, 3.0,15<br>
> >><br>
> >> ===============================================================================<br>
> >><br>
> >> * installer: Fix bug that install of pgpool-II RPM fails (Yugo Nagata)<br>
> >> [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> * installer: Fix to set up passwordless SSH from apache@localhost to<br>
> >> postgres@localhost (Yugo Nagata) [3.3]<br>
> >><br>
> >> * Fix bug that restarted pgpool's watchdog status is regarded as down<br>
> >> (Yugo Nagata) [3.3]<br>
> >><br>
> >> * doc: Add mention about "listen queue" and how to increase the "backlog"<br>
> >> in the num_init_children section. (Tatsuo Ishii) [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> * Fix bug that watchdog status goes down even when only one of trusted<br>
> >> servers get unpingable (Yugo Nagata) [3.3][3.2]<br>
> >><br>
> >> * Fix bad performance of unlogged tables detection code. (Tatsuo Ishii)<br>
> >> [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> Pointed out at [pgpool-hackers: 435][[pgpool-general:2325].<br>
> >><br>
> >> * Fix primary node detection logic. (Tatsuo Ishii) [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> There's a possibility that primary node is not detected. This happens<br>
> >> in following situation. node 0: primary, node 1: standby. Node 0 goes<br>
> >> down. Health checking detects the fact but local status is not updated<br>
> >> yet. Primary node finding (find_primary_node) runs. Node 0's status is<br>
> >> yet healthy. Because find_primary_node fails to connect to node 0, it<br>
> >> immediately returns -1 and fails to find that fact that node 1 is now<br>
> >> primary.<br>
> >><br>
> >> Fix is just continuing to look for primary node when fails to connect<br>
> >> to a node.<br>
> >><br>
> >> Per [pgpool-general: 2409].<br>
> >><br>
> >> * Add raw mode support to pgpool_setup. (Tatsuo Ishii) [3.3]<br>
> >><br>
> >> * test: Integrate jdbc test to regression test. (Tatsuo Ishii) [3.3]<br>
> >><br>
> >> * Fix jdbc DML fails when operated in raw mode and auto commit is off.<br>
> >> (Tatsuo Ishii) [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> This is reported in bug #92.<br>
> >><br>
> >> * Fix to output error message when wd_escalation_command fails with exit<br>
> >> code other than 0 (Yugo Nagata) [3.3]<br>
> >><br>
> >> This is suggested by Sergey Arlashin in [pgpool-general: 2457].<br>
> >><br>
> >> * test: Add new regression test for query cache. (Tatsuo Ishii) [3.3][3.2]<br>
> >><br>
> >> * Fix query cache bug with extended protocol. (Tatsuo Ishii) [3.3][3.2]<br>
> >><br>
> >> SELECT retrieves outdated cache even DML was executed in an expilicit<br>
> >> transaction. The bug had been there since in memory query cache was<br>
> >> born. Per [pgpool-general-jp: 1252].<br>
> >><br>
> >> * Add missing entries "relcache_size" and "check_temp_table" to show<br>
> >> pool_status (Tatsuo Ishii) [3.3][3.2]<br>
> >><br>
> >> * Fix to output error message when if_up_cmd fails. (Yugo Nagata) [3.3]<br>
> >><br>
> >> This is suggested by Sergey Arlashin in [pgpool-general: 2457].<br>
> >><br>
> >> * Avoid to send queries to unrelated nodes in streaming replication mode.<br>
> >> (Tatsuo Ishii) [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> Pgpool-II sends certain queries, such as BEGIN, END and SET commands to<br>
> >> all of DB nodes. However in streaming replication mode, only primary<br>
> >> node and at most one standby node are only concerned (if primacy node<br>
> >> is selected as the load balance node, only 1 node is concerned).<br>
> >><br>
> >> See [pgpool-hackers: 464] for more details.<br>
> >><br>
> >> * Fix possible buffer overrun problem and memory leak. (Tatsuo Ishii)<br>
> >> [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> Per Coverity 1111465 and 1111482.<br>
> >><br>
> >> * Fix possible buffer overrun. (Tatsuo Ishii) [3.3][3.2][3.1]<br>
> >><br>
> >> Replace strcpy() with strlcpy(). Per Coverity report 1111478, 1111480,<br>
> >> 1111481.<br>
> >><br>
> >> * Add dubug messages for analyzing errors in if_up_cmd (Yugo Nagata)<br>
> >> [3.3]<br>
> >><br>
> >> * Fix freeing NULL. (Tatsuo Ishii) [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> Per Coverity 1111384.<br>
> >><br>
> >> * Do not enable query cache on materialized views. (Tatsuo Ishii)<br>
> >> [3.3][3.2]<br>
> >><br>
> >> Per bug #95.<br>
> >><br>
> >> * Fix memory leak. (Tatsuo Ishii) [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> Per Coverity 1111446.<br>
> >><br>
> >> * Fix a segmentation fault in parallel mode with system_db_hostname is<br>
> >> empty (Yugo Nagata) [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> * Fix to output debug messages in processing pgpool.conf with -d option<br>
> >> (Yugo Nagata) [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> Previously, some debug messages in pool_get_config() ware not output<br>
> >> even when -d option was used.<br>
> >><br>
> >> * Fix JDBC exception of prepared statement including now() in<br>
> >> replication mode (Yugo Nagata) [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> With JDBC, when a prepared statement is executed more than<br>
> >> PrepareThreshold times, the statement is named and Describe message<br>
> >> is sent after Parse. With named statement, pgpool rewrite now() to<br>
> >> parameter in replication mode. Hence, rewritten query has additonal<br>
> >> parameter than original. In this case, ParameterDescription message<br>
> >> sent to frontend (response of Describe) should include OIDs of the<br>
> >> same number os original query's parameters. Otherwize, JDBC throws<br>
> >> ArrayIndexoutOfBoundsException.<br>
> >><br>
> >> This is reported in [pgpool-general-jp: 1192].<br>
> >><br>
> >> * Fix backend error of prepared statement about table which has<br>
> >> column whoes default value is now() in replication mode (Yugo Nagata)<br>
> >> [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> When pgpool parses a named prepared statement with default now(),<br>
> >> timestamps are replaced to additional parameters. So, Bind message also<br>
> >> should inclued additional parameter format codes. However, when the<br>
> >> number of original parameter was one, pgpool didn't handle this. This<br>
> >> caused a error like "incorrect binary data format in bind parameter 2".<br>
> >><br>
> >> * test: Fix a bug of regression test of JDBC that shows OK even when<br>
> >> this fails (Yugo Nagata) [3.3]<br>
> >><br>
> >> * test: Add a new regression test for JDBC's PrepareThreshold<br>
> >> (Yugo Nagata) [3.3]<br>
> >><br>
> >> * doc: Add description about parallel mode doesn't support PREPARE<br>
> >> (Yugo Nagata) [3.3][3.2][3.1][3.0]<br>
> >><br>
> >> Per bug #93<br>
> >><br>
> >><br>
> >> ===============================================================================<br>
> >> pgpoolAdmin 3.3.1<br>
> >><br>
> >> ===============================================================================<br>
> >><br>
> >> * Fix a bug that watchdug status is shown as "Unknown" when it's "Down"<br>
> >> (Yugo Nagata)<br>
> >><br>
> >> * Fix a bug that restart of PostgreSQL doesn't work (Yugo Nagata)<br>
> >><br>
> >> * Fix to get properly if the login user is a super user or not on backend<br>
> >> nodes. (Nozomi Anzai)<br>
> >><br>
> >> This problem could be occured especially when he isn't a super user.<br>
> >> Per [pgpool-general: 2340].<br>
> >><br>
> >> * Fix that pgpool_pgctl can be executed only when the login user is super<br>
> >> user in backend nodes.(Nozomi Anzai)<br>
> >><br>
> >> Previously, any login user was able to try to execute pgpool_pgctl()<br>
> >> which could stop/restart/reload a backend node even if he was not a<br>
> >> super<br>
> >> user. Also pgpool_pgctl() was executed by sr_check_user or<br>
> >> health_check_user,<br>
> >> but it wasn't reasonable. This update is that buttons of<br>
> >> stop/restart/reload<br>
> >> are disabled when the login user isn't a super user and that<br>
> >> pgpool_pg_ctl()<br>
> >> is executed by login user instead of sr_check_user or health_check_user<br>
> >> who don't have to be non-superuser. Per [pgpool-general: 2338].<br>
> >><br>
> >> --<br>
> >> Yugo Nagata <<a href="mailto:nagata@sraoss.co.jp" target="_blank">nagata@sraoss.co.jp</a>><br>
> >> _______________________________________________<br>
> >> pgpool-general mailing list<br>
> >> <a href="mailto:pgpool-general@pgpool.net" target="_blank">pgpool-general@pgpool.net</a><br>
> >> <a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br>
> >><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Sincerely yours,<br>
> > Alexandru Cardaniuc<br>
> ><br>
><br>
><br>
><br>
> --<br>
> Sincerely yours,<br>
> Alexandru Cardaniuc<br>
<br>
<br>
</div></div><span><font color="#888888">--<br>
Yugo Nagata <<a href="mailto:nagata@sraoss.co.jp" target="_blank">nagata@sraoss.co.jp</a>><br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br>Sincerely yours,<br>Alexandru Cardaniuc
</div>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Sincerely yours,<br>Alexandru Cardaniuc
</div>