Re: [Postgres-xc-general] Problem with postgre-xc configuration using pgxc_ctl

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Please take a look at the note I’ve just submitted and let me know what’s going on.

It is essential to specify ―prefix option to ./configure to get all the installation material to go to proper place.   Also you need to setup your .profile or similar settings to configure your PATH and LD_LIBRARY_PATH to get pgxc binaries and libraries first, not postgreSQL ones.

Regards;
---
Koichi Suzuki

2014/03/06 15:07、Juned Khan <jkh...@gm...<mailto:jkh...@gm...>> のメール：

Hi Koichi,

I have installed pgxc by configure, make and make install but
the difference is i haven't specified the prefix.

then i have created postgres user and given permission to this user.

set key-based authentication for this servers.

then configured the script according to my need and followed the commands
which you have shown in that demo.

did i miss something ?

Please suggest.

On Thu, Mar 6, 2014 at 11:26 AM, Koichi Suzuki <koi...@gm...<mailto:koi...@gm...>> wrote:
It seems that you need to follow the following steps.

1) You build and install pgxc binary by configure, make and make
install command.
2) pgxc_ctl will take installation binary from the installation target
specified in pgxc_ctl configuration file.
3) pgxc_ctl need write privilege to this target directory at all the servers.
4) You need to setup proper PATH and LD_LIBRARY_PATH at all the
servers in advance (pgxc_ctl will not take care of them).

You need to specify the same value of If you don't specify
--prefix=/usr/local/pgsql/include/server/pgxc option at configure.
After the build is done, run "make install".   All the material will
go to specified directory.

If you did all these, could you please let me know the steps you've
done since you get Postgres-XC material?

Regards;
---
Koichi Suzuki

2014-03-04 20:25 GMT+09:00 Juned Khan <jkh...@gm...<mailto:jkh...@gm...>>:
> Hi Koichi,
>
> No there are not other process which uses this socket.
> and this file is not exists even"/tmp/.s.PGSQL.5432"
>
> I think there is some problem with stating this components
> Please see below log for the output of "start all" and "monitor all"
> commands.
>
> PGXC start all
> Start GTM master
> waiting for server to shut down... done
> server stopped
> server starting
> Starting coordinator master.
> Starting coordinator master coord1
> ERROR: target coordinator master coord1 is already running now.   Skip
> initilialization.
> Starting coordinator master coord2
> LOG:  could not bind IPv4 socket: Address already in use
> HINT:  Is another postmaster already running on port 20005? If not, wait a
> few seconds and retry.
> LOG:  could not bind IPv6 socket: Address already in use
> HINT:  Is another postmaster already running on port 20005? If not, wait a
> few seconds and retry.
> WARNING:  could not create listen socket for "*"
> FATAL:  could not create any TCP/IP sockets
> Done.
> Starting all the datanode masters.
> Starting datanode master datanode1.
> Starting datanode master datanode2.
> LOG:  could not bind IPv4 socket: Address already in use
> HINT:  Is another postmaster already running on port 20008? If not, wait a
> few seconds and retry.
> LOG:  could not bind IPv6 socket: Address already in use
> HINT:  Is another postmaster already running on port 20008? If not, wait a
> few seconds and retry.
> WARNING:  could not create listen socket for "*"
> FATAL:  could not create any TCP/IP sockets
> LOG:  could not bind IPv4 socket: Address already in use
> HINT:  Is another postmaster already running on port 20009? If not, wait a
> few seconds and retry.
> LOG:  could not bind IPv6 socket: Address already in use
> HINT:  Is another postmaster already running on port 20009? If not, wait a
> few seconds and retry.
> WARNING:  could not create listen socket for "*"
> FATAL:  could not create any TCP/IP sockets
> Done.
> PGXC
> PGXC monitor all
> Running: gtm master
> Running: coordinator master coord1
> Not running: coordinator master coord2
> Not running: datanode master datanode1
> Not running: datanode master datanode2
> PGXC
>
> Please suggest what could be the issue, i am using three machines
> And i have confirmed the script, i have used different ports for each
> components.
>
> Attached configuration script as well.
>
>
>
> On Tue, Mar 4, 2014 at 3:53 PM, Koichi Suzuki <koi...@gm...<mailto:koi...@gm...>> wrote:
>>
>> Are there any other process which are using the socket?  Probably
>> another postgreSQL or postgres-xc instance?
>>
>> If not, it seems that unix domain socket is left.   If you're sure
>> that no such process is alive, you can just remove this file to fix
>> the issue.
>>
>> If you're running both coordinator and datanode or more than one of
>> them at the same server, you must assign different port number to them
>> to avoid resource conflict.
>>
>> Regards;
>> ---
>> Koichi Suzuki
>>
>>
>> 2014-03-03 23:01 GMT+09:00 Juned Khan <jkh...@gm...<mailto:jkh...@gm...>>:
>> > Hi Koichi,
>> >
>> > I fixed all that configuration issue.
>> > Executed deploy all command and installation went well.
>> > Lots of password prompt was there but that will be fixed
>> > if i set key-based authentication.
>> >
>> > But problem with creating database its giving below error.
>> >
>> > PGXC createdb koichi;
>> > createdb: could not connect to database template1: could not connect to
>> > server: No such file or directory
>> >         Is the server running locally and accepting
>> >         connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
>> >
>> > verified the /home/postgres/pgxc/nodes/coord/pg_hba.conf file below line
>> > was
>> > there
>> > host all postgres 192.168.1.0/24<http://192.168.1.0/24> trust, so i think it should work ?
>> >
>> > My another question is where do i get the documentation where all the
>> > parameters
>> > (coordNames,coordMasterDirs etc) is explained, which is used in that
>> > configuration script ?
>> >
>> > And is it necessary to install postgreSQL with pgxc or pgxc only is fine
>> > ?
>> >
>> > Please suggest.
>> >
>> >
>> >
>> > On Mon, Mar 3, 2014 at 4:03 PM, Koichi Suzuki <koi...@gm...<mailto:koi...@gm...>>
>> > wrote:
>> >>
>> >> The error message says that the number of array element is incorrect
>> >> in your configuration file.    coordNames and coordMasterServers must
>> >> have the same number of array member, and vise versa.
>> >>
>> >> Regards;
>> >> ---
>> >> Koichi Suzuki
>> >>
>> >>
>> >> 2014-03-03 19:13 GMT+09:00 Juned Khan <jkh...@gm...<mailto:jkh...@gm...>>:
>> >> > Hi Koichi,
>> >> >
>> >> > I have set that conf file and getting below in console.
>> >> >
>> >> > [postgres@localhost pgxc_ctl]$ pgxc_ctl
>> >> > Installing pgxc_ctl_bash script as
>> >> > /home/postgres/pgxc_ctl/pgxc_ctl_bash.
>> >> > ERROR: File "/home/postgres/pgxc_ctl/pgxc_ctl.conf" not found or not
>> >> > a
>> >> > regular file. No such file or directory
>> >> > Installing pgxc_ctl_bash script as
>> >> > /home/postgres/pgxc_ctl/pgxc_ctl_bash.
>> >> > Reading configuration using /home/postgres/pgxc_ctl/pgxc_ctl_bash
>> >> > --home
>> >> > /home/postgres/pgxc_ctl --configuration
>> >> > /home/postgres/pgxc_ctl/pgxc_ctl.conf
>> >> > Finished to read configuration.
>> >> > PGXC_CTL START ***************
>> >> >
>> >> > Current directory: /home/postgres/pgxc_ctl
>> >> > PGXC pgxc_ctl --configuration /home/postgres/pgxc_ctl/pgxc_ctl.ctl
>> >> > Installing pgxc_ctl_bash script as
>> >> > /home/postgres/pgxc_ctl/pgxc_ctl_bash.
>> >> > Installing pgxc_ctl_bash script as
>> >> > /home/postgres/pgxc_ctl/pgxc_ctl_bash.
>> >> > Reading configuration using /home/postgres/pgxc_ctl/pgxc_ctl_bash
>> >> > --home
>> >> > /home/postgres/pgxc_ctl --configuration
>> >> > /home/postgres/pgxc_ctl/pgxc_ctl.ctl
>> >> > Finished to read configuration.
>> >> > ERROR: Number of elements in coordinator master definitions are
>> >> > different
>> >> > coordNames and coordMasterServers. Check your configuration
>> >> > ERROR: Number of elements in coordinator master definitions are
>> >> > different
>> >> > coordNames and coordMasterDirs. Check your configuration
>> >> > ERROR: Number of elements in coordinator master definitions are
>> >> > different
>> >> > coordNames and coordMaxWALSenders. Check your configuration
>> >> > ERROR: Number of elements in datanode master definitions are
>> >> > different
>> >> > datanodeNames and datanodeMasterServers. Check your configuration
>> >> > ERROR: Number of elements in datanode master definitions are
>> >> > different
>> >> > datanodeNames and datanodeMasterDirs. Check your configuration
>> >> > ERROR: Number of elements in datanode master definitions are
>> >> > different
>> >> > datanodeNames and datanodeMaxWALSenders. Check your configuration
>> >> > ERROR: Found fundamental configuration error.
>> >> > ******** PGXC_CTL START ***************
>> >> >
>> >> > please suggest
>> >> >
>> >> >
>> >> >
>> >> > On Mon, Mar 3, 2014 at 2:11 PM, 鈴木 幸市 <ko...@in...<mailto:ko...@in...>>
>> >> > wrote:
>> >> >>
>> >> >> Yes and pgxc user must have write privilege to this directory on all
>> >> >> the
>> >> >> servers you are installing.
>> >> >>
>> >> >> Are you running pgxc_ctl as pgxc user?   It need this and you should
>> >> >> place
>> >> >> your configuration file (default pgxc_ctl.conf) at $HOME/pgxc_ctl...
>> >> >>
>> >> >> Does it work?
>> >> >> ---
>> >> >> Koichi Suzuki
>> >> >>
>> >> >> 2014/03/03 16:27、Juned Khan <jkh...@gm...<mailto:jkh...@gm...>> のメール：
>> >> >>
>> >> >> Hi Koichi,
>> >> >>
>> >> >> I didn't provide any path for configure script.
>> >> >> And now i am using postgres user to deploy that configuration file..
>> >> >> But its seems that its not reading that file, having same errors.
>> >> >>
>> >> >> my postgre-xc setup is under /usr/local/pgsql can i set this as
>> >> >> install
>> >> >> directory ?
>> >> >>
>> >> >> But the problem is, its not reading my modified configuration file..
>> >> >>
>> >> >> Please advice.
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Mon, Mar 3, 2014 at 6:37 AM, 鈴木 幸市 <ko...@in...<mailto:ko...@in...>>
>> >> >> wrote:
>> >> >>>
>> >> >>> You should specify each name such as node06 the host name you use
>> >> >>> to
>> >> >>> connect to the server.
>> >> >>>
>> >> >>> Also, the directory /root/pgxc, as specified pgxcInstallDir looks
>> >> >>> wrong.
>> >> >>> From the value, I’m afraid you’re trying to run pgxc_ctl as root.
>> >> >>> Please
>> >> >>> avoid this.   You should assign different linux user name as the
>> >> >>> owner
>> >> >>> of
>> >> >>> postgres-xc cluster.   From the configuration file, the owner and
>> >> >>> the
>> >> >>> user
>> >> >>> of postgres-xc cluster is postgres.   So you should run pgxc_ctl as
>> >> >>> the user
>> >> >>> postgres.
>> >> >>>
>> >> >>> Please make sure to assign pgxcInstallDir the same as your make
>> >> >>> install
>> >> >>> target of postgres-xc build.   This is exactly --prefix you should
>> >> >>> give to
>> >> >>> configure.   It will reduce the confusion if you don’t give any
>> >> >>> more
>> >> >>> target
>> >> >>> directory in configure script.
>> >> >>>
>> >> >>> Regards;
>> >> >>> ---
>> >> >>> Koichi Suzuki
>> >> >>>
>> >> >>> 2014/02/28 23:12、Juned Khan <jkh...@gm...<mailto:jkh...@gm...>> のメール：
>> >> >>>
>> >> >>> Hi All,
>> >> >>>
>> >> >>> I just took my first step to configure postgre-xc using pgxc_ctl.
>> >> >>> I have follow some steps and prepared configuration file according
>> >> >>> to
>> >> >>> my
>> >> >>> need.
>> >> >>>
>> >> >>> But when i am trying to deploy this configuration getting erros :
>> >> >>>
>> >> >>> PGXC deploy all
>> >> >>> Deploying Postgres-XC materials to all the target servers.
>> >> >>> Prepare tarball to deploy ...
>> >> >>> tar: /root/pgxc: Cannot chdir: No such file or directory
>> >> >>> tar: Error is not recoverable: exiting now
>> >> >>> Deploying to the server node13.
>> >> >>> Deploying to the server node12.
>> >> >>> Deploying to the server node06.
>> >> >>> Deploying to the server node07.
>> >> >>> Deploying to the server node08.
>> >> >>> Deploying to the server node09.
>> >> >>> ssh: Could not resolve hostname node06: Name or service not known
>> >> >>> ssh: Could not resolve hostname node07: Name or service not known
>> >> >>> ssh: Could not resolve hostname node12: Name or service not known
>> >> >>> ssh: Could not resolve hostname node13: Name or service not known
>> >> >>> ssh: Could not resolve hostname node06: Name or service not known
>> >> >>> ssh: Could not resolve hostname node08: Name or service not known
>> >> >>> ssh: Could not resolve hostname node09: Name or service not known
>> >> >>> ssh: Could not resolve hostname node07: Name or service not known
>> >> >>> ssh: Could not resolve hostname node12: Name or service not known
>> >> >>> ssh: Could not resolve hostname node13: Name or service not known
>> >> >>> ssh: Could not resolve hostname node09: Name or service not known
>> >> >>> ssh: Could not resolve hostname node08: Name or service not known
>> >> >>> ssh: Could not resolve hostname node06: Name or service not known
>> >> >>> ssh: Could not resolve hostname node12: Name or service not known
>> >> >>> ssh: Could not resolve hostname node07: Name or service not known
>> >> >>> ssh: Could not resolve hostname node13: Name or service not known
>> >> >>> ssh: Could not resolve hostname node06: Name or service not known
>> >> >>> ssh: Could not resolve hostname node08: Name or service not known
>> >> >>> ssh: Could not resolve hostname node09: Name or service not known
>> >> >>> ssh: Could not resolve hostname node07: Name or service not known
>> >> >>> ssh: Could not resolve hostname node13: Name or service not known
>> >> >>> ssh: Could not resolve hostname node12: Name or service not known
>> >> >>> ssh: Could not resolve hostname node13: Name or service not known
>> >> >>> lost connection
>> >> >>> ssh: Could not resolve hostname node08: Name or service not known
>> >> >>> ssh: Could not resolve hostname node09: Name or service not known
>> >> >>> ssh: Could not resolve hostname node12: Name or service not known
>> >> >>> lost connection
>> >> >>> ssh: Could not resolve hostname node06: Name or service not known
>> >> >>> lost connection
>> >> >>> ssh: Could not resolve hostname node07: Name or service not known
>> >> >>> lost connection
>> >> >>> ssh: Could not resolve hostname node08: Name or service not known
>> >> >>> lost connection
>> >> >>> ssh: Could not resolve hostname node09: Name or service not known
>> >> >>> lost connection
>> >> >>> ssh: Could not resolve hostname node13: Name or service not known
>> >> >>> ssh: Could not resolve hostname node12: Name or service not known
>> >> >>> ssh: Could not resolve hostname node06: Name or service not known
>> >> >>> ssh: Could not resolve hostname node07: Name or service not known
>> >> >>> ssh: Could not resolve hostname node08: Name or service not known
>> >> >>> ssh: Could not resolve hostname node09: Name or service not known
>> >> >>> Deployment done.
>> >> >>>
>> >> >>>
>> >> >>> Thing which is confusing me is, even if i have removed some nodes
>> >> >>> from
>> >> >>> this file
>> >> >>> but still its trying to read it don't know where.
>> >> >>>
>> >> >>> Still i am trying to find out the issue, but if anyone give some
>> >> >>> suggestion or idea
>> >> >>> it will be appreciable.
>> >> >>>
>> >> >>> I have attached my configuration file.
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>> Thanks,
>> >> >>> Juned Khan
>> >> >>> iNextrix Technologies Pvt Ltd.
>> >> >>> www.inextrix.com<http://www.inextrix.com/>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> <pgxc_ctl_demo.ctl>------------------------------------------------------------------------------
>> >> >>> Flow-based real-time traffic analytics software. Cisco certified
>> >> >>> tool.
>> >> >>> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow
>> >> >>> Analyzer
>> >> >>> Customize your own dashboards, set traffic alerts and generate
>> >> >>> reports.
>> >> >>> Network behavioral analysis & security monitoring. All-in-one tool.
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk_______________________________________________
>> >> >>> Postgres-xc-general mailing list
>> >> >>> Pos...@li...<mailto:Pos...@li...>
>> >> >>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>> >> >>>
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Thanks,
>> >> >> Juned Khan
>> >> >> iNextrix Technologies Pvt Ltd.
>> >> >> www.inextrix.com<http://www.inextrix.com/>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Thanks,
>> >> > Juned Khan
>> >> > iNextrix Technologies Pvt Ltd.
>> >> > www.inextrix.com<http://www.inextrix.com/>
>> >> >
>> >> >
>> >> >
>> >> > ------------------------------------------------------------------------------
>> >> > Subversion Kills Productivity. Get off Subversion & Make the Move to
>> >> > Perforce.
>> >> > With Perforce, you get hassle-free workflows. Merge that actually
>> >> > works.
>> >> > Faster operations. Version large binaries.  Built-in WAN optimization
>> >> > and
>> >> > the
>> >> > freedom to use Git, Perforce or both. Make the move to Perforce.
>> >> >
>> >> >
>> >> > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>> >> > _______________________________________________
>> >> > Postgres-xc-general mailing list
>> >> > Pos...@li...<mailto:Pos...@li...>
>> >> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>> >> >
>> >
>> >
>> >
>> >
>> > --
>> > Thanks,
>> > Juned Khan
>> > iNextrix Technologies Pvt Ltd.
>> > www.inextrix.com<http://www.inextrix.com/>
>
>
>
>
> --
> Thanks,
> Juned Khan
> iNextrix Technologies Pvt Ltd.
> www.inextrix.com<http://www.inextrix.com/>

--
Thanks,
Juned Khan
iNextrix Technologies Pvt Ltd.
www.inextrix.com<http://www.inextrix.com/>