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

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 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...> 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...>:
> > 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...> 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...> のメール：
> >>
> >> 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...> 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...> のメール：
> >>>
> >>> 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
> >>>
> >>>
> <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...
> >>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> Thanks,
> >> Juned Khan
> >> iNextrix Technologies Pvt Ltd.
> >> www.inextrix.com
> >>
> >>
> >
> >
> >
> > --
> > Thanks,
> > Juned Khan
> > iNextrix Technologies Pvt Ltd.
> > 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...
> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
> >
>

-- 
Thanks,
Juned Khan
iNextrix Technologies Pvt Ltd.
www.inextrix.com