[pgpool-general: 2641] Re: bash script can't see env variables when run by pgpool

[Gintautas Sulskus]

Hello,

ifconfig_path = '/home/ubuntu/apps/scripts'
PgpoolAdmin description of ifconfig_path is: The path of a command to
switch the IP address. I understand it as the path for if_up_cmd
and if_down_cmd commands.

if_up_cmd = 'pg_ni_up.sh up eth0:1 10.0.1.244 255.255.255.0'
if_down_cmd = 'pg_ni_up.sh down eth0:1'


PS. Is this mailing list the right place to discuss about PgpoolAdmin?
In the latest PgpoolAdmin version "if_*up*_cmd " is described as "The
command to bring *down* the virtual IP" and "if_*down*_cmd" as "The command
to bring *up* the virtual IP". Clearly descriptions are mixed up.

Gintautas


On Mon, Mar 10, 2014 at 2:46 AM, Yugo Nagata <nagata at sraoss.co.jp> wrote:

> Hi,
>
> On Sun, 9 Mar 2014 03:00:52 +0000
> Gintautas Sulskus <gingaz at gmail.com> wrote:
>
> > Hello,
> >
> > I am trying to set up pgpool watchdog. For virtual IP control my plan is
> to
> > use bash scripts (if_up_cmd/if_down_cmd). In my script I use some
> > environment variables.
> >
> > A strange thing occurs here. No matter under what user I run pgpool,
> script
> > can't pick up my custom environment variables from /etc/environment
> > (including customised PATH). It still sees standard binaries like
> ifconfig
> > though.
>
> How do you configure pgpool.conf about if_up_cmd, if_down_cmd,
> ifconfig_path?
> pgpool see ifconfig commands on the path specified by these options.
>
> >
> > Same script, when run manually by me, works under all users. Any ideas
> what
> > can be wrong?
> >
> > The only solution I have come up is to redefine env variables in the
> script.
> >
> > Thanks.
> >
> > Best Regards,
> > Gintas
>
>
> --
> Yugo Nagata <nagata at sraoss.co.jp>
>



-- 
Best Regards,
Gintautas Sulskus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20140321/dd7e1daa/attachment.html>