Menu
▾
▴
postgres-xc-general — General info and messages
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
(19) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(12) |
Feb
(1) |
Mar
(4) |
Apr
(4) |
May
(32) |
Jun
(12) |
Jul
(11) |
Aug
(1) |
Sep
(6) |
Oct
(3) |
Nov
|
Dec
(10) |
| 2012 |
Jan
(11) |
Feb
(1) |
Mar
(3) |
Apr
(25) |
May
(53) |
Jun
(38) |
Jul
(103) |
Aug
(54) |
Sep
(31) |
Oct
(66) |
Nov
(77) |
Dec
(20) |
| 2013 |
Jan
(91) |
Feb
(86) |
Mar
(103) |
Apr
(107) |
May
(25) |
Jun
(37) |
Jul
(17) |
Aug
(59) |
Sep
(38) |
Oct
(78) |
Nov
(29) |
Dec
(15) |
| 2014 |
Jan
(23) |
Feb
(82) |
Mar
(118) |
Apr
(101) |
May
(103) |
Jun
(45) |
Jul
(6) |
Aug
(10) |
Sep
|
Oct
(32) |
Nov
|
Dec
(9) |
| 2015 |
Jan
(3) |
Feb
(5) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(9) |
Aug
(4) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Juned K. <jkh...@gm...> - 2014-03-06 06:08:07
|
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...>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...>: > > 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...> > 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...>: > >> > 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 > > > > > > > > > > -- > > Thanks, > > Juned Khan > > iNextrix Technologies Pvt Ltd. > > www.inextrix.com > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
|
From: Koichi S. <koi...@gm...> - 2014-03-06 05:56:43
|
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...>: > 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...> 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...>: >> > 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 > > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com |
|
From: Juned K. <jkh...@gm...> - 2014-03-06 05:55:42
|
Hi Koichi, My install directory is */home/postgres/* > > [postgres@localhost ~]$ 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 > However i am able to connect using psql PGXC psql -p 20004 -h node2 > psql (PGXC 1.1, based on PG 9.2.4) > Type "help" for help. > > postgres=# createdb koichi > but database is not being created. > PGXC psql -p 20004 -h node2 -d koichi > psql: FATAL: database "koichi" does not exist > what could be the problem ? On Thu, Mar 6, 2014 at 11:14 AM, 鈴木 幸市 <ko...@in...> wrote: > You should not use createdb from postgrereSQL. What is your > installation target of PGXC? > > You can also login to the database using psql and issue create database > command. > > Regards; > --- > Koichi Suzuki > > 2014/03/06 14:30、Juned Khan <jkh...@gm...> のメール： > > Hi Koichi, > > Specified port and host but now getting below error: > > PGXC createdb koichi -h node2 -p 20004 >> createdb: database creation failed: ERROR: Failed to get pooled >> connections >> PGXC >> > > And which createdb command i should use which will select coordinator > automatically. > > [root@localhost ~]# find / -name createdb >> /usr/src/postgres-xc/src/bin/scripts/createdb >> /usr/local/pgsql/bin/createdb >> /usr/local/bin/createdb >> > > Please suggest. > > > > > On Thu, Mar 6, 2014 at 10:50 AM, 鈴木 幸市 <ko...@in...> wrote: > >> Is your coordinator running locally? You may have to specify -h option >> to tell where to go. >> >> Or, you can issue Createdb command, which is embedded pgxc_ctl command. >> Createdb will chose one of the available coordinators and go there. >> >> Regards; >> --- >> Koichi Suzuki >> >> 2014/03/06 14:16、Juned Khan <jkh...@gm...> のメール： >> >> Hi Lin , >> >> Still its not working, same issue >> >> PGXC createdb astpp -p 20004 >>> 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.20004"? >>> PGXC >>> >> >> >> >> >> On Wed, Mar 5, 2014 at 9:01 PM, Lin Wang <lin...@gm...> wrote: >> >>> I think you need point out one port of the coordinators when you >>> create a database, for example as below: >>> >>> [wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/createdb db1 >>> createdb: could not connect to database template1: could not connect to >>> server: no that file or folder >>> Is the server running locally and accepting >>> connections on Unix domain socket "/tmp/.s.PGSQL.5432"? >>> >>> [wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/createdb db1 -p >>> 5300 >>> [wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/psql -d postgres >>> -p 5300 -c "\l" >>> List of databases >>> Name | Owner | Encoding | Collate | Ctype | Access >>> privileges >>> >>> -----------+-------+----------+-------------+-------------+------------------- >>> db1 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | >>> postgres | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | >>> template0 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/wln >>> + >>> | | | | | wln=CTc/wln >>> template1 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/wln >>> + >>> | | | | | wln=CTc/wln >>> (4 rows) >>> >>> >>> Good Luck >>> --------- >>> waln >>> >>> >>> 2014-03-05 22:11 GMT+08:00 Juned Khan <jkh...@gm...>: >>> >>>> Hi All, >>>> >>>> Since last few days i am trying to setup postgre-xc with 3 local >>>> systems. >>>> I have done with basic setup, but having issue with database creation. >>>> >>>> Below is the output of monitor all >>>> >>>> PGXC monitor all >>>>> Running: gtm master >>>>> Running: coordinator master coord1 >>>>> Running: coordinator master coord2 >>>>> Running: datanode master datanode1 >>>>> Running: datanode master datanode2 >>>>> >>>> >>>> But when i am trying to create database its giving me below error. >>>> >>>> PGXC createdb astpp; >>>>> 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"? >>>>> PGXC >>>>> >>>> >>>> I am just one step away to done with my postgre-xc setup. >>>> Please suggest me, how to get it fixed . >>>> >>>> >>>> >>>> -- >>>> 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 >> ------------------------------------------------------------------------------ >> 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 > > > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
|
From: 鈴木 幸市 <ko...@in...> - 2014-03-06 05:44:37
|
You should not use createdb from postgrereSQL. What is your installation target of PGXC?
You can also login to the database using psql and issue create database command.
Regards;
---
Koichi Suzuki
2014/03/06 14:30、Juned Khan <jkh...@gm...<mailto:jkh...@gm...>> のメール：
Hi Koichi,
Specified port and host but now getting below error:
PGXC createdb koichi -h node2 -p 20004
createdb: database creation failed: ERROR: Failed to get pooled connections
PGXC
And which createdb command i should use which will select coordinator automatically.
[root@localhost ~]# find / -name createdb
/usr/src/postgres-xc/src/bin/scripts/createdb
/usr/local/pgsql/bin/createdb
/usr/local/bin/createdb
Please suggest.
On Thu, Mar 6, 2014 at 10:50 AM, 鈴木 幸市 <ko...@in...<mailto:ko...@in...>> wrote:
Is your coordinator running locally? You may have to specify -h option to tell where to go.
Or, you can issue Createdb command, which is embedded pgxc_ctl command. Createdb will chose one of the available coordinators and go there.
Regards;
---
Koichi Suzuki
2014/03/06 14:16、Juned Khan <jkh...@gm...<mailto:jkh...@gm...>> のメール：
Hi Lin ,
Still its not working, same issue
PGXC createdb astpp -p 20004
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.20004"?
PGXC
On Wed, Mar 5, 2014 at 9:01 PM, Lin Wang <lin...@gm...<mailto:lin...@gm...>> wrote:
I think you need point out one port of the coordinators when you create a database, for example as below:
[wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/createdb db1
createdb: could not connect to database template1: could not connect to server: no that file or folder
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
[wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/createdb db1 -p 5300
[wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/psql -d postgres -p 5300 -c "\l"
List of databases
Name | Owner | Encoding | Collate | Ctype | Access privileges
-----------+-------+----------+-------------+-------------+-------------------
db1 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 |
postgres | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 |
template0 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/wln +
| | | | | wln=CTc/wln
template1 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/wln +
| | | | | wln=CTc/wln
(4 rows)
Good Luck
---------
waln
2014-03-05 22:11 GMT+08:00 Juned Khan <jkh...@gm...<mailto:jkh...@gm...>>:
Hi All,
Since last few days i am trying to setup postgre-xc with 3 local systems.
I have done with basic setup, but having issue with database creation.
Below is the output of monitor all
PGXC monitor all
Running: gtm master
Running: coordinator master coord1
Running: coordinator master coord2
Running: datanode master datanode1
Running: datanode master datanode2
But when i am trying to create database its giving me below error.
PGXC createdb astpp;
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"?
PGXC
I am just one step away to done with my postgre-xc setup.
Please suggest me, how to get it fixed .
--
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/>
------------------------------------------------------------------------------
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/>
|
|
From: Juned K. <jkh...@gm...> - 2014-03-06 05:30:12
|
Hi Koichi, Specified port and host but now getting below error: PGXC createdb koichi -h node2 -p 20004 > createdb: database creation failed: ERROR: Failed to get pooled > connections > PGXC > And which createdb command i should use which will select coordinator automatically. [root@localhost ~]# find / -name createdb > /usr/src/postgres-xc/src/bin/scripts/createdb > /usr/local/pgsql/bin/createdb > /usr/local/bin/createdb > Please suggest. On Thu, Mar 6, 2014 at 10:50 AM, 鈴木 幸市 <ko...@in...> wrote: > Is your coordinator running locally? You may have to specify -h option > to tell where to go. > > Or, you can issue Createdb command, which is embedded pgxc_ctl command. > Createdb will chose one of the available coordinators and go there. > > Regards; > --- > Koichi Suzuki > > 2014/03/06 14:16、Juned Khan <jkh...@gm...> のメール： > > Hi Lin , > > Still its not working, same issue > > PGXC createdb astpp -p 20004 >> 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.20004"? >> PGXC >> > > > > > On Wed, Mar 5, 2014 at 9:01 PM, Lin Wang <lin...@gm...> wrote: > >> I think you need point out one port of the coordinators when you create >> a database, for example as below: >> >> [wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/createdb db1 >> createdb: could not connect to database template1: could not connect to >> server: no that file or folder >> Is the server running locally and accepting >> connections on Unix domain socket "/tmp/.s.PGSQL.5432"? >> >> [wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/createdb db1 -p >> 5300 >> [wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/psql -d postgres -p >> 5300 -c "\l" >> List of databases >> Name | Owner | Encoding | Collate | Ctype | Access >> privileges >> >> -----------+-------+----------+-------------+-------------+------------------- >> db1 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | >> postgres | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | >> template0 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/wln >> + >> | | | | | wln=CTc/wln >> template1 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/wln >> + >> | | | | | wln=CTc/wln >> (4 rows) >> >> >> Good Luck >> --------- >> waln >> >> >> 2014-03-05 22:11 GMT+08:00 Juned Khan <jkh...@gm...>: >> >>> Hi All, >>> >>> Since last few days i am trying to setup postgre-xc with 3 local >>> systems. >>> I have done with basic setup, but having issue with database creation. >>> >>> Below is the output of monitor all >>> >>> PGXC monitor all >>>> Running: gtm master >>>> Running: coordinator master coord1 >>>> Running: coordinator master coord2 >>>> Running: datanode master datanode1 >>>> Running: datanode master datanode2 >>>> >>> >>> But when i am trying to create database its giving me below error. >>> >>> PGXC createdb astpp; >>>> 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"? >>>> PGXC >>>> >>> >>> I am just one step away to done with my postgre-xc setup. >>> Please suggest me, how to get it fixed . >>> >>> >>> >>> -- >>> 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 > ------------------------------------------------------------------------------ > 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 |
|
From: 鈴木 幸市 <ko...@in...> - 2014-03-06 05:21:07
|
Is your coordinator running locally? You may have to specify -h option to tell where to go.
Or, you can issue Createdb command, which is embedded pgxc_ctl command. Createdb will chose one of the available coordinators and go there.
Regards;
---
Koichi Suzuki
2014/03/06 14:16、Juned Khan <jkh...@gm...<mailto:jkh...@gm...>> のメール：
Hi Lin ,
Still its not working, same issue
PGXC createdb astpp -p 20004
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.20004"?
PGXC
On Wed, Mar 5, 2014 at 9:01 PM, Lin Wang <lin...@gm...<mailto:lin...@gm...>> wrote:
I think you need point out one port of the coordinators when you create a database, for example as below:
[wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/createdb db1
createdb: could not connect to database template1: could not connect to server: no that file or folder
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
[wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/createdb db1 -p 5300
[wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/psql -d postgres -p 5300 -c "\l"
List of databases
Name | Owner | Encoding | Collate | Ctype | Access privileges
-----------+-------+----------+-------------+-------------+-------------------
db1 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 |
postgres | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 |
template0 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/wln +
| | | | | wln=CTc/wln
template1 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/wln +
| | | | | wln=CTc/wln
(4 rows)
Good Luck
---------
waln
2014-03-05 22:11 GMT+08:00 Juned Khan <jkh...@gm...<mailto:jkh...@gm...>>:
Hi All,
Since last few days i am trying to setup postgre-xc with 3 local systems.
I have done with basic setup, but having issue with database creation.
Below is the output of monitor all
PGXC monitor all
Running: gtm master
Running: coordinator master coord1
Running: coordinator master coord2
Running: datanode master datanode1
Running: datanode master datanode2
But when i am trying to create database its giving me below error.
PGXC createdb astpp;
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"?
PGXC
I am just one step away to done with my postgre-xc setup.
Please suggest me, how to get it fixed .
--
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/>
------------------------------------------------------------------------------
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
|
|
From: Juned K. <jkh...@gm...> - 2014-03-06 05:16:48
|
Hi Lin , Still its not working, same issue PGXC createdb astpp -p 20004 > 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.20004"? > PGXC > On Wed, Mar 5, 2014 at 9:01 PM, Lin Wang <lin...@gm...> wrote: > I think you need point out one port of the coordinators when you create a > database, for example as below: > > [wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/createdb db1 > createdb: could not connect to database template1: could not connect to > server: no that file or folder > Is the server running locally and accepting > connections on Unix domain socket "/tmp/.s.PGSQL.5432"? > > [wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/createdb db1 -p 5300 > [wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/psql -d postgres -p > 5300 -c "\l" > List of databases > Name | Owner | Encoding | Collate | Ctype | Access > privileges > > -----------+-------+----------+-------------+-------------+------------------- > db1 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | > postgres | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | > template0 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/wln > + > | | | | | wln=CTc/wln > template1 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/wln > + > | | | | | wln=CTc/wln > (4 rows) > > > Good Luck > --------- > waln > > > 2014-03-05 22:11 GMT+08:00 Juned Khan <jkh...@gm...>: > >> Hi All, >> >> Since last few days i am trying to setup postgre-xc with 3 local systems. >> I have done with basic setup, but having issue with database creation. >> >> Below is the output of monitor all >> >> PGXC monitor all >>> Running: gtm master >>> Running: coordinator master coord1 >>> Running: coordinator master coord2 >>> Running: datanode master datanode1 >>> Running: datanode master datanode2 >>> >> >> But when i am trying to create database its giving me below error. >> >> PGXC createdb astpp; >>> 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"? >>> PGXC >>> >> >> I am just one step away to done with my postgre-xc setup. >> Please suggest me, how to get it fixed . >> >> >> >> -- >> 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 |
|
From: Lin W. <lin...@gm...> - 2014-03-05 15:31:35
|
I think you need point out one port of the coordinators when you create a
database, for example as below:
[wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/createdb db1
createdb: could not connect to database template1: could not connect to
server: no that file or folder
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
[wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/createdb db1 -p 5300
[wln@localhost pgxc]$ /home/wln/pgxc/install_1_1/bin/psql -d postgres -p
5300 -c "\l"
List of databases
Name | Owner | Encoding | Collate | Ctype | Access
privileges
-----------+-------+----------+-------------+-------------+-------------------
db1 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 |
postgres | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 |
template0 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/wln
+
| | | | | wln=CTc/wln
template1 | wln | UTF8 | zh_CN.UTF-8 | zh_CN.UTF-8 | =c/wln
+
| | | | | wln=CTc/wln
(4 rows)
Good Luck
---------
waln
2014-03-05 22:11 GMT+08:00 Juned Khan <jkh...@gm...>:
> Hi All,
>
> Since last few days i am trying to setup postgre-xc with 3 local systems.
> I have done with basic setup, but having issue with database creation.
>
> Below is the output of monitor all
>
> PGXC monitor all
>> Running: gtm master
>> Running: coordinator master coord1
>> Running: coordinator master coord2
>> Running: datanode master datanode1
>> Running: datanode master datanode2
>>
>
> But when i am trying to create database its giving me below error.
>
> PGXC createdb astpp;
>> 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"?
>> PGXC
>>
>
> I am just one step away to done with my postgre-xc setup.
> Please suggest me, how to get it fixed .
>
>
>
> --
> 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
>
>
|
|
From: Juned K. <jkh...@gm...> - 2014-03-05 14:11:16
|
Hi All, Since last few days i am trying to setup postgre-xc with 3 local systems. I have done with basic setup, but having issue with database creation. Below is the output of monitor all PGXC monitor all > Running: gtm master > Running: coordinator master coord1 > Running: coordinator master coord2 > Running: datanode master datanode1 > Running: datanode master datanode2 > But when i am trying to create database its giving me below error. PGXC createdb astpp; > 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"? > PGXC > I am just one step away to done with my postgre-xc setup. Please suggest me, how to get it fixed . -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
|
From: Koichi S. <koi...@gm...> - 2014-03-04 10:24:00
|
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...>: > 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 |
|
From: Koichi S. <koi...@gm...> - 2014-03-03 16:22:52
|
Thank you for pointing out. The document looks to need some improvement on the node management. You're correct that you need to issue pgxc_pool_reload(). Before this, you need to create new node ready to this step. --- Koichi Suzuki 2014-03-04 1:17 GMT+09:00 Lin Wang <lin...@gm...>: > > Thank you very much,Koichi Suzuki. From postgres-xc 1.1 Documentation > "Chapter 30. Adding a New Node", I learn it how to add a new node to the > cluster. I find it: when I create node 'node100' in the session of A, the > node100 is not efficient for the cluster untile execute 'select > pgxc_pool_reload()' or I open a new session B, in the session B the node100 > is efficient. as the reason of this, when I create node node100, then > use'\c postgres' ,the session shows"psql (9.3beta2, server 9.2.4)" , so I > know it open a new session, the node100 is efficient, but I don't initdb the > node of node100, so it gets wrong. just like as below: > > [wln@localhost pgxc]$ psql -d postgres -p 5300 > psql (9.3beta2, server 9.2.4) > Type "help" for help. > > postgres=# select * from pgxc_node; > node_name | node_type | node_port | node_host | nodeis_primary | > nodeis_preferred | node_id > --------------+-----------+-----------+-----------+----------------+------------------+------------ > datanode1 | D | 5302 | localhost | f | f > | 888802358 > datanode2 | D | 5304 | localhost | f | f > | -905831925 > coordinator1 | C | 5300 | localhost | f | f > | 1938253334 > (3 rows) > > postgres=# create node node100 > with(type='datanode',host=localhost,port=7809); > CREATE NODE > postgres=# create table t1(id int); > CREATE TABLE > postgres=# insert into t1 values(1); > INSERT 0 1 > postgres=# explain select * from t1; > QUERY PLAN > ---------------------------------------------------------------------------- > Data Node Scan on "__REMOTE_FQS_QUERY__" (cost=0.00..0.00 rows=0 width=0) > Node/s: datanode1, datanode2 > (2 rows) > > postgres=# create user user1 with SUPERUSER; > CREATE ROLE > postgres=# set role user1; > SET > postgres=# \c postgres > psql (9.3beta2, server 9.2.4) > You are now connected to database "postgres" as user "wln". > postgres=# create table t2 (id int); > ERROR: Failed to get pooled connections > > > > 2014-03-03 12:27 GMT+08:00 Koichi Suzuki <koi...@gm...>: > >> > Did you run initdb for node100 before you run CREATE NODE node100? >> > Because you already have created database, you need to run initdb and >> > copy catalog from other datanode to node100. >> >> > If you're adding new datanode to the cluster, you should do the >> > following: >> > 1. Run initdb to initialize new datanode resources, >> > 2. Prepare at least postgresql.conf and pg_hba.conf for the new >> > datanode. >> > 3. Fun pg_dumpall on an existing datanode to dump all the catalog >> > info. You should specify --include-nodes and --dump-nodes option to >> > dump everything in the catalog. >> > 4. Start the new datanode using pg_ctl with -Z restoremode option. >> > 5. Restore the backed up catalog you build at the step 3 by running >> > psql against the new datanode. >> > 6. Stop the new datanode and restart it with -Z datanode option >> > (without -Z restoremode option). >> > 7. Issue CREATE NODE statement at all the coordinators. >> >> > You seem to do only the step 7. >> >> > If you're not sure what to do, plase take a look at the function >> > add_datanodeMaster() in datanode_cmd.c at contrib/pgxc_ctl directory. >> > Of course, the simplest way is to configure your cluster with >> > pgxc_ctl. Documentation will be available at >> > http://postgres-xc.sourceforge.net/docs/1_1/pgxc-ctl.html >> >> > Pgxc_ctl also locks the entire cluster while you're adding new node to >> > maintain cluster consistent. >> >> > Good Luck; >> > --- >> > Koichi Suzuki >> >> >> > 2014-03-02 14:19 GMT+09:00 Lin Wang <lin...@gm...>: >> > Hi, >> > first I create user1 then use user1 create a node; seceond, I >> > use >> > 'set role wln' to return the user of the superuser of cluster; last , I >> > want to use 'drop user user1;' to drop the user1, but it shows "Failed >> > to >> > get pooled connections". (use postgres-xc1.1). >> > the detailed content as below: >> > [wln@localhost pgxc]$ psql -d postgres -p 5300 >> > psql (9.3beta2, server 9.2.4) >> > Type "help" for help. >> > >> > postgres=# create user user1 with SUPERUSER; >> > CREATE ROLE >> > postgres=# set role user1; >> > SET >> > postgres=# create node node100 >> > with(type='datanode',host=localhost,port=7809); >> > CREATE NODE >> > postgres=# set role wln; >> > SET >> > postgres=# drop user user1; >> > DROP ROLE >> > postgres=# create user user1 with SUPERUSER; >> > CREATE ROLE >> > postgres=# set role user1; >> > SET >> > postgres=# \c postgres >> > psql (9.3beta2, server 9.2.4) >> > You are now connected to database "postgres" as user "wln". >> > postgres=# drop user user1; >> > ERROR: Failed to get pooled connections >> > postgres=# select oid, * from pgxc_node; >> > oid | node_name | node_type | node_port | node_host | >> > nodeis_primary | >> > nodeis_preferred | node_id >> > >> > -------+--------------+-----------+-----------+-----------+----------------+------------------+------------ >> > 16384 | datanode1 | D | 5302 | localhost | f >> > | >> > f | 888802358 >> > 16385 | datanode2 | D | 5304 | localhost | f >> > | >> > f | -905831925 >> > 16386 | coordinator1 | C | 5300 | localhost | f >> > | >> > f | 1938253334 >> > 16388 | node100 | D | 7809 | localhost | f >> > | >> > f | 1668042070 >> > (4 rows) >> > >> > log: >> > 2014-03-01 06:39:18.543 CST 53111016.6fe0 postgres 28640 psql 0 >> > 00000DEBUG: >> > [re]setting xid = 0, old_value = 0 >> > 2014-03-01 06:39:18.545 CST 53110fe1.6fd1 postgres 28625 psql 0 >> > 00000DEBUG: >> > Postmaster child: connection to GTM closed >> > 2014-03-01 06:39:25.370 CST 53111016.6fe0 postgres 28640 psql 0 >> > 00000DEBUG: >> > Postmaster child: connection established to GTM with string >> > host=localhost >> > port=5307 node_name=coordinator1 >> > 2014-03-01 06:39:25.371 CST 53111016.6fe0 postgres 28640 psql 0 >> > 00000DEBUG: >> > Assigned new transaction ID from GTM = 10014 >> > 2014-03-01 06:39:25.371 CST 53111016.6fe0 postgres 28640 psql 10014 >> > 00000DEBUG: Getting snapshot. Current XID = 10014 >> > 2014-03-01 06:39:25.372 CST 53111016.6fe0 postgres 28640 psql 10014 >> > 00000DEBUG: from GTM: xmin = 10014, xmax = 10014, xcnt = 0, RecGlobXmin >> > = >> > 10014 >> > 2014-03-01 06:39:25.394 CST 53110fd8.6fac 28588 0 08006LOG: failed to >> > connect to Datanode >> > 2014-03-01 06:39:25.394 CST 53110fd8.6fac 28588 0 01000WARNING: can >> > not >> > connect to node 16388 >> > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014 >> > 53000LOG: failed to acquire connections >> > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014 >> > 53000STATEMENT: drop user user1; >> > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014 >> > 53000ERROR: Failed to get pooled connections >> > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014 >> > 53000STATEMENT: drop user user1; >> > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014 >> > 00000DEBUG: Record transaction abort 10014 >> > 2014-03-01 06:39:25.395 CST 53111016.6fe0 postgres 28640 psql 10014 >> > 00000DEBUG: [re]setting xid = 0, old_value = 0 >> > 2014-03-01 06:40:16.315 CST 53110fd8.6fba 28602 0 00000DEBUG: >> > Autovacuum >> > launcher: connection established to GTM with string host=localhost >> > port=5307 >> > node_name=coordinator1 >> > >> > >> > Thanks >> > waln >> > >> > >> > ------------------------------------------------------------------------------ >> > 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 >> > |
|
From: Lin W. <lin...@gm...> - 2014-03-03 16:17:23
|
Thank you very much,Koichi Suzuki. From postgres-xc 1.1 Documentation
"Chapter 30. Adding a New Node", I learn it how to add a new node to the
cluster. I find it: when I create node 'node100' in the session of A, the
node100 is not efficient for the cluster untile execute 'select
pgxc_pool_reload()' or I open a new session B, in the session B the
node100 is efficient. as the reason of this, when I create node node100,
then use'\c postgres' ,the session shows"psql (9.3beta2, server 9.2.4)" ,
so I know it open a new session, the node100 is efficient, but I don't
initdb the node of node100, so it gets wrong. just like as below:
[wln@localhost pgxc]$ psql -d postgres -p 5300
psql (9.3beta2, server 9.2.4)
Type "help" for help.
postgres=# select * from pgxc_node;
node_name | node_type | node_port | node_host | nodeis_primary |
nodeis_preferred | node_id
--------------+-----------+-----------+-----------+----------------+------------------+------------
datanode1 | D | 5302 | localhost | f | f
| 888802358
datanode2 | D | 5304 | localhost | f | f
| -905831925
coordinator1 | C | 5300 | localhost | f | f
| 1938253334
(3 rows)
postgres=# create node node100
with(type='datanode',host=localhost,port=7809);
CREATE NODE
postgres=# create table t1(id int);
CREATE TABLE
postgres=# insert into t1 values(1);
INSERT 0 1
postgres=# explain select * from t1;
QUERY PLAN
----------------------------------------------------------------------------
Data Node Scan on "__REMOTE_FQS_QUERY__" (cost=0.00..0.00 rows=0 width=0)
Node/s: datanode1, datanode2
(2 rows)
postgres=# create user user1 with SUPERUSER;
CREATE ROLE
postgres=# set role user1;
SET
postgres=# \c postgres
psql (9.3beta2, server 9.2.4)
You are now connected to database "postgres" as user "wln".
postgres=# create table t2 (id int);
ERROR: Failed to get pooled connections
> 2014-03-03 12:27 GMT+08:00 Koichi Suzuki <koi...@gm...>:
> > Did you run initdb for node100 before you run CREATE NODE node100?
> > Because you already have created database, you need to run initdb and
> > copy catalog from other datanode to node100.
>
> > If you're adding new datanode to the cluster, you should do the
> following:
> > 1. Run initdb to initialize new datanode resources,
> > 2. Prepare at least postgresql.conf and pg_hba.conf for the new datanode.
> > 3. Fun pg_dumpall on an existing datanode to dump all the catalog
> > info. You should specify --include-nodes and --dump-nodes option to
> > dump everything in the catalog.
> > 4. Start the new datanode using pg_ctl with -Z restoremode option.
> > 5. Restore the backed up catalog you build at the step 3 by running
> > psql against the new datanode.
> > 6. Stop the new datanode and restart it with -Z datanode option
> > (without -Z restoremode option).
> > 7. Issue CREATE NODE statement at all the coordinators.
>
> > You seem to do only the step 7.
>
> > If you're not sure what to do, plase take a look at the function
> > add_datanodeMaster() in datanode_cmd.c at contrib/pgxc_ctl directory.
> > Of course, the simplest way is to configure your cluster with
> > pgxc_ctl. Documentation will be available at
> > http://postgres-xc.sourceforge.net/docs/1_1/pgxc-ctl.html
>
> > Pgxc_ctl also locks the entire cluster while you're adding new node to
> > maintain cluster consistent.
>
> > Good Luck;
> > ---
> > Koichi Suzuki
>
>
> > 2014-03-02 14:19 GMT+09:00 Lin Wang <lin...@gm...>:
> > Hi,
> > first I create user1 then use user1 create a node; seceond, I use
> > 'set role wln' to return the user of the superuser of cluster; last , I
> > want to use 'drop user user1;' to drop the user1, but it shows "Failed to
> > get pooled connections". (use postgres-xc1.1).
> > the detailed content as below:
> > [wln@localhost pgxc]$ psql -d postgres -p 5300
> > psql (9.3beta2, server 9.2.4)
> > Type "help" for help.
> >
> > postgres=# create user user1 with SUPERUSER;
> > CREATE ROLE
> > postgres=# set role user1;
> > SET
> > postgres=# create node node100
> > with(type='datanode',host=localhost,port=7809);
> > CREATE NODE
> > postgres=# set role wln;
> > SET
> > postgres=# drop user user1;
> > DROP ROLE
> > postgres=# create user user1 with SUPERUSER;
> > CREATE ROLE
> > postgres=# set role user1;
> > SET
> > postgres=# \c postgres
> > psql (9.3beta2, server 9.2.4)
> > You are now connected to database "postgres" as user "wln".
> > postgres=# drop user user1;
> > ERROR: Failed to get pooled connections
> > postgres=# select oid, * from pgxc_node;
> > oid | node_name | node_type | node_port | node_host |
> nodeis_primary |
> > nodeis_preferred | node_id
> >
> -------+--------------+-----------+-----------+-----------+----------------+------------------+------------
> > 16384 | datanode1 | D | 5302 | localhost | f
> |
> > f | 888802358
> > 16385 | datanode2 | D | 5304 | localhost | f
> |
> > f | -905831925
> > 16386 | coordinator1 | C | 5300 | localhost | f
> |
> > f | 1938253334
> > 16388 | node100 | D | 7809 | localhost | f
> |
> > f | 1668042070
> > (4 rows)
> >
> > log:
> > 2014-03-01 06:39:18.543 CST 53111016.6fe0 postgres 28640 psql 0
> 00000DEBUG:
> > [re]setting xid = 0, old_value = 0
> > 2014-03-01 06:39:18.545 CST 53110fe1.6fd1 postgres 28625 psql 0
> 00000DEBUG:
> > Postmaster child: connection to GTM closed
> > 2014-03-01 06:39:25.370 CST 53111016.6fe0 postgres 28640 psql 0
> 00000DEBUG:
> > Postmaster child: connection established to GTM with string
> host=localhost
> > port=5307 node_name=coordinator1
> > 2014-03-01 06:39:25.371 CST 53111016.6fe0 postgres 28640 psql 0
> 00000DEBUG:
> > Assigned new transaction ID from GTM = 10014
> > 2014-03-01 06:39:25.371 CST 53111016.6fe0 postgres 28640 psql 10014
> > 00000DEBUG: Getting snapshot. Current XID = 10014
> > 2014-03-01 06:39:25.372 CST 53111016.6fe0 postgres 28640 psql 10014
> > 00000DEBUG: from GTM: xmin = 10014, xmax = 10014, xcnt = 0, RecGlobXmin
> =
> > 10014
> > 2014-03-01 06:39:25.394 CST 53110fd8.6fac 28588 0 08006LOG: failed to
> > connect to Datanode
> > 2014-03-01 06:39:25.394 CST 53110fd8.6fac 28588 0 01000WARNING: can
> not
> > connect to node 16388
> > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014
> > 53000LOG: failed to acquire connections
> > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014
> > 53000STATEMENT: drop user user1;
> > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014
> > 53000ERROR: Failed to get pooled connections
> > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014
> > 53000STATEMENT: drop user user1;
> > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014
> > 00000DEBUG: Record transaction abort 10014
> > 2014-03-01 06:39:25.395 CST 53111016.6fe0 postgres 28640 psql 10014
> > 00000DEBUG: [re]setting xid = 0, old_value = 0
> > 2014-03-01 06:40:16.315 CST 53110fd8.6fba 28602 0 00000DEBUG:
> Autovacuum
> > launcher: connection established to GTM with string host=localhost
> port=5307
> > node_name=coordinator1
> >
> >
> > Thanks
> > waln
> >
> >
> ------------------------------------------------------------------------------
> > 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
> >
|
|
From: Juned K. <jkh...@gm...> - 2014-03-03 14:01:33
|
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
|
|
From: Mason S. <ms...@tr...> - 2014-03-03 12:36:33
|
On Mon, Mar 3, 2014 at 1:19 AM, Juned Khan <jkh...@gm...> wrote: > Hi Mason, > > Thanks for your suggestions. > So in short as of now postgre-xc is the only solution for me right ? > > Again, from my earlier email, it depends on your requirements, if it is acceptable if there is a node or network outage at one location, all locations may be impacted and what kind of latency is ok. -- Mason Sharp TransLattice - http://www.translattice.com Distributed and Clustered Database Solutions |
|
From: Koichi S. <koi...@gm...> - 2014-03-03 10:34:06
|
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 > |
|
From: Juned K. <jkh...@gm...> - 2014-03-03 10:13:25
|
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 |
|
From: 鈴木 幸市 <ko...@in...> - 2014-03-03 08:41:17
|
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/> |
|
From: Juned K. <jkh...@gm...> - 2014-03-03 07:30:10
|
I want to setup simple configuration with three VMs for testing, And after few days i have to setup same on live servers, but i have to test this out in locally first. On Mon, Mar 3, 2014 at 12:57 PM, Juned Khan <jkh...@gm...> wrote: > 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 |
|
From: Juned K. <jkh...@gm...> - 2014-03-03 07:27:51
|
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 |
|
From: Juned K. <jkh...@gm...> - 2014-03-03 06:20:02
|
Hi Mason, Thanks for your suggestions. So in short as of now postgre-xc is the only solution for me right ? On Fri, Feb 28, 2014 at 6:54 PM, Mason Sharp <ms...@tr...>wrote: > > > On Thu, Feb 27, 2014 at 10:16 PM, Juned Khan <jkh...@gm...> wrote: > >> Hi Mason, >> >> What alternatives i have for my requirements ? >> >> > Hi Juned, > > In the PostgreSQL community, there are a couple of open source > multi-master solutions, Bucardo and RubyRep, but they currently only allow > for two database nodes. I have heard of hacking together a Slony-based > solution to with triggers calling custom functions to roll your own > solution. > > There are other solutions in the greater PostgreSQL ecosystem. The case > you are describing is really the case that the company I work for addresses > with their flagship product, TED, but it is closed source. I believe > EnterpriseDB also offers a proprietary solution. > > Coincidentally, we may provide a special custom version of XC for a > customer with some distributed requirements that are similar to your own. > If this code gets open sourced, I can let you know, but that would be a > ways out in the future. > > > -- > Mason Sharp > > TransLattice - http://www.translattice.com > Distributed and Clustered Database Solutions > > > -- Thanks, Juned Khan iNextrix Technologies Pvt Ltd. www.inextrix.com |
|
From: Koichi S. <koi...@gm...> - 2014-03-03 04:27:40
|
Did you run initdb for node100 before you run CREATE NODE node100? Because you already have created database, you need to run initdb and copy catalog from other datanode to node100. If you're adding new datanode to the cluster, you should do the following: 1. Run initdb to initialize new datanode resources, 2. Prepare at least postgresql.conf and pg_hba.conf for the new datanode. 3. Fun pg_dumpall on an existing datanode to dump all the catalog info. You should specify --include-nodes and --dump-nodes option to dump everything in the catalog. 4. Start the new datanode using pg_ctl with -Z restoremode option. 5. Restore the backed up catalog you build at the step 3 by running psql against the new datanode. 6. Stop the new datanode and restart it with -Z datanode option (without -Z restoremode option). 7. Issue CREATE NODE statement at all the coordinators. You seem to do only the step 7. If you're not sure what to do, plase take a look at the function add_datanodeMaster() in datanode_cmd.c at contrib/pgxc_ctl directory. Of course, the simplest way is to configure your cluster with pgxc_ctl. Documentation will be available at http://postgres-xc.sourceforge.net/docs/1_1/pgxc-ctl.html Pgxc_ctl also locks the entire cluster while you're adding new node to maintain cluster consistent. Good Luck; --- Koichi Suzuki 2014-03-02 14:19 GMT+09:00 Lin Wang <lin...@gm...>: > Hi, > first I create user1 then use user1 create a node; seceond, I use > 'set role wln' to return the user of the superuser of cluster; last , I > want to use 'drop user user1;' to drop the user1, but it shows "Failed to > get pooled connections". (use postgres-xc1.1). > the detailed content as below: > [wln@localhost pgxc]$ psql -d postgres -p 5300 > psql (9.3beta2, server 9.2.4) > Type "help" for help. > > postgres=# create user user1 with SUPERUSER; > CREATE ROLE > postgres=# set role user1; > SET > postgres=# create node node100 > with(type='datanode',host=localhost,port=7809); > CREATE NODE > postgres=# set role wln; > SET > postgres=# drop user user1; > DROP ROLE > postgres=# create user user1 with SUPERUSER; > CREATE ROLE > postgres=# set role user1; > SET > postgres=# \c postgres > psql (9.3beta2, server 9.2.4) > You are now connected to database "postgres" as user "wln". > postgres=# drop user user1; > ERROR: Failed to get pooled connections > postgres=# select oid, * from pgxc_node; > oid | node_name | node_type | node_port | node_host | nodeis_primary | > nodeis_preferred | node_id > -------+--------------+-----------+-----------+-----------+----------------+------------------+------------ > 16384 | datanode1 | D | 5302 | localhost | f | > f | 888802358 > 16385 | datanode2 | D | 5304 | localhost | f | > f | -905831925 > 16386 | coordinator1 | C | 5300 | localhost | f | > f | 1938253334 > 16388 | node100 | D | 7809 | localhost | f | > f | 1668042070 > (4 rows) > > log: > 2014-03-01 06:39:18.543 CST 53111016.6fe0 postgres 28640 psql 0 00000DEBUG: > [re]setting xid = 0, old_value = 0 > 2014-03-01 06:39:18.545 CST 53110fe1.6fd1 postgres 28625 psql 0 00000DEBUG: > Postmaster child: connection to GTM closed > 2014-03-01 06:39:25.370 CST 53111016.6fe0 postgres 28640 psql 0 00000DEBUG: > Postmaster child: connection established to GTM with string host=localhost > port=5307 node_name=coordinator1 > 2014-03-01 06:39:25.371 CST 53111016.6fe0 postgres 28640 psql 0 00000DEBUG: > Assigned new transaction ID from GTM = 10014 > 2014-03-01 06:39:25.371 CST 53111016.6fe0 postgres 28640 psql 10014 > 00000DEBUG: Getting snapshot. Current XID = 10014 > 2014-03-01 06:39:25.372 CST 53111016.6fe0 postgres 28640 psql 10014 > 00000DEBUG: from GTM: xmin = 10014, xmax = 10014, xcnt = 0, RecGlobXmin = > 10014 > 2014-03-01 06:39:25.394 CST 53110fd8.6fac 28588 0 08006LOG: failed to > connect to Datanode > 2014-03-01 06:39:25.394 CST 53110fd8.6fac 28588 0 01000WARNING: can not > connect to node 16388 > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014 > 53000LOG: failed to acquire connections > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014 > 53000STATEMENT: drop user user1; > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014 > 53000ERROR: Failed to get pooled connections > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014 > 53000STATEMENT: drop user user1; > 2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014 > 00000DEBUG: Record transaction abort 10014 > 2014-03-01 06:39:25.395 CST 53111016.6fe0 postgres 28640 psql 10014 > 00000DEBUG: [re]setting xid = 0, old_value = 0 > 2014-03-01 06:40:16.315 CST 53110fd8.6fba 28602 0 00000DEBUG: Autovacuum > launcher: connection established to GTM with string host=localhost port=5307 > node_name=coordinator1 > > > Thanks > waln > > ------------------------------------------------------------------------------ > 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 > |
|
From: 鈴木 幸市 <ko...@in...> - 2014-03-03 01:07:23
|
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... https://lists.sourceforge.net/lists/listinfo/postgres-xc-general |
|
From: Lin W. <lin...@gm...> - 2014-03-02 05:19:56
|
Hi,
first I create user1 then use user1 create a node; seceond, I use
'set role wln' to return the user of the superuser of cluster; last , I
want to use 'drop user user1;' to drop the user1, but it shows "Failed to
get pooled connections". (use postgres-xc1.1).
the detailed content as below:
[wln@localhost pgxc]$ psql -d postgres -p 5300
psql (9.3beta2, server 9.2.4)
Type "help" for help.
postgres=# create user user1 with SUPERUSER;
CREATE ROLE
postgres=# set role user1;
SET
postgres=# create node node100
with(type='datanode',host=localhost,port=7809);
CREATE NODE
postgres=# set role wln;
SET
postgres=# drop user user1;
DROP ROLE
postgres=# create user user1 with SUPERUSER;
CREATE ROLE
postgres=# set role user1;
SET
postgres=# \c postgres
psql (9.3beta2, server 9.2.4)
You are now connected to database "postgres" as user "wln".
postgres=# drop user user1;
ERROR: Failed to get pooled connections
postgres=# select oid, * from pgxc_node;
oid | node_name | node_type | node_port | node_host | nodeis_primary
| nodeis_preferred | node_id
-------+--------------+-----------+-----------+-----------+----------------+------------------+------------
16384 | datanode1 | D | 5302 | localhost | f
| f | 888802358
16385 | datanode2 | D | 5304 | localhost | f
| f | -905831925
16386 | coordinator1 | C | 5300 | localhost | f
| f | 1938253334
16388 | node100 | D | 7809 | localhost | f
| f | 1668042070
(4 rows)
log:
2014-03-01 06:39:18.543 CST 53111016.6fe0 postgres 28640 psql 0 00000DEBUG:
[re]setting xid = 0, old_value = 0
2014-03-01 06:39:18.545 CST 53110fe1.6fd1 postgres 28625 psql 0 00000DEBUG:
Postmaster child: connection to GTM closed
2014-03-01 06:39:25.370 CST 53111016.6fe0 postgres 28640 psql 0 00000DEBUG:
Postmaster child: connection established to GTM with string host=localhost
port=5307 node_name=coordinator1
2014-03-01 06:39:25.371 CST 53111016.6fe0 postgres 28640 psql 0 00000DEBUG:
Assigned new transaction ID from GTM = 10014
2014-03-01 06:39:25.371 CST 53111016.6fe0 postgres 28640 psql 10014
00000DEBUG: Getting snapshot. Current XID = 10014
2014-03-01 06:39:25.372 CST 53111016.6fe0 postgres 28640 psql 10014
00000DEBUG: from GTM: xmin = 10014, xmax = 10014, xcnt = 0, RecGlobXmin =
10014
2014-03-01 06:39:25.394 CST 53110fd8.6fac 28588 0 08006LOG: failed to
connect to Datanode
2014-03-01 06:39:25.394 CST 53110fd8.6fac 28588 0 01000WARNING: can not
connect to node 16388
2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014
53000LOG: failed to acquire connections
2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014
53000STATEMENT: drop user user1;
2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014
53000ERROR: Failed to get pooled connections
2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014
53000STATEMENT: drop user user1;
2014-03-01 06:39:25.394 CST 53111016.6fe0 postgres 28640 psql 10014
00000DEBUG: Record transaction abort 10014
2014-03-01 06:39:25.395 CST 53111016.6fe0 postgres 28640 psql 10014
00000DEBUG: [re]setting xid = 0, old_value = 0
2014-03-01 06:40:16.315 CST 53110fd8.6fba 28602 0 00000DEBUG: Autovacuum
launcher: connection established to GTM with string host=localhost
port=5307 node_name=coordinator1
Thanks
waln
|
|
From: Mason S. <ms...@tr...> - 2014-02-28 13:24:20
|
On Thu, Feb 27, 2014 at 10:16 PM, Juned Khan <jkh...@gm...> wrote: > Hi Mason, > > What alternatives i have for my requirements ? > > Hi Juned, In the PostgreSQL community, there are a couple of open source multi-master solutions, Bucardo and RubyRep, but they currently only allow for two database nodes. I have heard of hacking together a Slony-based solution to with triggers calling custom functions to roll your own solution. There are other solutions in the greater PostgreSQL ecosystem. The case you are describing is really the case that the company I work for addresses with their flagship product, TED, but it is closed source. I believe EnterpriseDB also offers a proprietary solution. Coincidentally, we may provide a special custom version of XC for a customer with some distributed requirements that are similar to your own. If this code gets open sourced, I can let you know, but that would be a ways out in the future. -- Mason Sharp TransLattice - http://www.translattice.com Distributed and Clustered Database Solutions |
|
From: 鈴木 幸市 <ko...@in...> - 2014-02-28 06:28:25
|
Sorry for the inconvenience. Please remove src/interfaces/ecpg/preproc/preproc.c before the build. If your environment has appropriate bison, this will solve the problem.
Best;
---
Koichi Suzuki
2014/02/28 0:57、Lin Wang <lin...@gm...<mailto:lin...@gm...>> のメール：
hi all,
when I compile the pgxc1.2 source code and execute the command "make", something wrong occures, as beblow:
make[5]: Leaving directory `/home/wln/pgxc/postgres-xc-1.2.0_beta/src/common'
gcc -DPGXC -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -DECPG_COMPILE -I../include -I../../../../src/interfaces/ecpg/include -I. -I. -DMAJOR_VERSION=4 -DMINOR_VERSION=9 -DPATCHLEVEL=0 -I../../../../src/include -D_GNU_SOURCE -c -o parser.o parser.c
parser.c:25:21: error：preproc.h：no such file or folder
parser.c:30: error：expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘lookahead_yylval’
parser.c:31: error：expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘lookahead_yylloc’
in the file "src/interfaces/ecpg/preproc/parser.c", I can get it:
#include "postgres_fe.h"
#include "extern.h"
#include "preproc.h"
but I can't find the file "preproc.h" in the folder of source code. at the same time, I find the file of "src/interfaces/ecpg/preproc/parser.c" in pgxc1.1 has also include the head file of "preproc.h", and I also don't find the file "preproc.h" in source code of pgxc1.1, but it is ok to run command "make" on source code of pgxc1.1.
I expect someone can explain it.
Thanks,
waln
------------------------------------------------------------------------------
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
|
43 messages has been excluded from this view by a project administrator.
