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
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
1
(6) |
2
|
|
3
|
4
|
5
|
6
|
7
(5) |
8
(1) |
9
|
|
10
|
11
(2) |
12
|
13
(7) |
14
|
15
(6) |
16
(1) |
|
17
|
18
(9) |
19
(10) |
20
(3) |
21
(6) |
22
(6) |
23
|
|
24
|
25
(20) |
26
(1) |
27
(1) |
28
(2) |
|
|
|
From: kushal <kus...@gm...> - 2013-02-21 12:08:35
|
Thanks guys. Issue is resolved. On 21 February 2013 04:04, Michael Paquier <mic...@gm...>wrote: > > > On Thu, Feb 21, 2013 at 8:47 PM, kushal <kus...@gm...> wrote: > >> LOG: database system was interrupted; last known up at 2013-02-21 >> 02:50:33 PST >> FATAL: lock file "/tmp/.s.PGPOOL.6667.lock" already exists >> HINT: Is another postmaster (PID 12892) using socket file >> "/tmp/.s.PGPOOL.6667"? >> LOG: database system was not properly shut down; automatic recovery in >> progress >> LOG: pool manager process (PID 12907) exited with exit code 1 >> LOG: terminating any other active server processes >> LOG: startup process (PID 12906) exited with exit code 2 >> LOG: aborting startup due to startup process failure >> >> >> Can anyone please help? >> > Simply set pooler_port to different values in each Coordinator's > postgresql.conf. As 6667 is the default value, this error is encountered > each time a second Coordiantor comes up. > -- > Michael > |
|
From: Michael P. <mic...@gm...> - 2013-02-21 12:04:34
|
On Thu, Feb 21, 2013 at 8:47 PM, kushal <kus...@gm...> wrote: > LOG: database system was interrupted; last known up at 2013-02-21 > 02:50:33 PST > FATAL: lock file "/tmp/.s.PGPOOL.6667.lock" already exists > HINT: Is another postmaster (PID 12892) using socket file > "/tmp/.s.PGPOOL.6667"? > LOG: database system was not properly shut down; automatic recovery in > progress > LOG: pool manager process (PID 12907) exited with exit code 1 > LOG: terminating any other active server processes > LOG: startup process (PID 12906) exited with exit code 2 > LOG: aborting startup due to startup process failure > > > Can anyone please help? > Simply set pooler_port to different values in each Coordinator's postgresql.conf. As 6667 is the default value, this error is encountered each time a second Coordiantor comes up. -- Michael |
|
From: Nikhil S. <ni...@st...> - 2013-02-21 12:03:22
|
Hi Kushal, Please ensure that the pooler_port value is different for both the coordinators. Regards, Nikhils On Thu, Feb 21, 2013 at 5:29 PM, Mason Sharp <ma...@st...> wrote: > > > On Thu, Feb 21, 2013 at 6:49 AM, kushal <kus...@gm...> wrote: >> >> Forgot to add. This whole setup is tried on one single server. >> >> >> On 21 February 2013 03:47, kushal <kus...@gm...> wrote: >>> >>> Hi >>> >>> I am using XC 1.0.2. I am trying to create the whole setup including gtm, >>> 2 gtm proxies, 2 coordinators and 2 datanodes. >>> >>> Ports Configured: >>> GTM: 16666 >>> GTM Proxy 1: 16667 >>> GTM Proxy 1: 16668 >>> Data Node 1: 15442 >>> Data Node 2: 15443 >>> Coordinator 1: 15432 >>> Coordinator 1: 15433 >>> >>> Coordinator 1 has gtm port configured to 16667 and Coordinator 2 to >>> 16668. >>> >>> Next I try to start all the nodes. >>> gtm_ctl start -Z gtm -D /var/lib/pgsql/gtm >>> gtm_ctl start -Z gtm_proxy -D /var/lib/pgsql/gtm_proxy1 >>> gtm_ctl start -Z gtm_proxy -D /var/lib/pgsql/gtm_proxy2 >>> pg_ctl start -Z datanode -D /var/lib/pgsql/data1 >>> pg_ctl start -Z datanode -D /var/lib/pgsql/data2 >>> pg_ctl start -Z coordinator -D /var/lib/pgsql/coord1 >>> pg_ctl start -Z coordinator -D /var/lib/pgsql/coord2 >>> >>> Everything works fine till coord1. In the last step while starting >>> coord2, I get this error: >>> >>> LOG: database system was interrupted; last known up at 2013-02-21 >>> 02:50:33 PST >>> FATAL: lock file "/tmp/.s.PGPOOL.6667.lock" already exists > > > Are you using the same port number in the coordinators for each one's > connection pool? > >>> >>> HINT: Is another postmaster (PID 12892) using socket file >>> "/tmp/.s.PGPOOL.6667"? >>> LOG: database system was not properly shut down; automatic recovery in >>> progress >>> LOG: pool manager process (PID 12907) exited with exit code 1 >>> LOG: terminating any other active server processes >>> LOG: startup process (PID 12906) exited with exit code 2 >>> LOG: aborting startup due to startup process failure >>> >>> >>> Can anyone please help? >>> >>> >>> >> >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_feb >> _______________________________________________ >> Postgres-xc-general mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> > > > > -- > Mason Sharp > > StormDB - http://www.stormdb.com > The Database Cloud > Postgres-XC Support and Services > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > -- StormDB - http://www.stormdb.com The Database Cloud Postgres-XC Support and Service |
|
From: Mason S. <ma...@st...> - 2013-02-21 12:00:02
|
On Thu, Feb 21, 2013 at 6:49 AM, kushal <kus...@gm...> wrote: > Forgot to add. This whole setup is tried on one single server. > > > On 21 February 2013 03:47, kushal <kus...@gm...> wrote: > >> Hi >> >> I am using XC 1.0.2. I am trying to create the whole setup including gtm, >> 2 gtm proxies, 2 coordinators and 2 datanodes. >> >> Ports Configured: >> GTM: 16666 >> GTM Proxy 1: 16667 >> GTM Proxy 1: 16668 >> Data Node 1: 15442 >> Data Node 2: 15443 >> Coordinator 1: 15432 >> Coordinator 1: 15433 >> >> Coordinator 1 has gtm port configured to 16667 and Coordinator 2 to 16668. >> >> Next I try to start all the nodes. >> gtm_ctl start -Z gtm -D /var/lib/pgsql/gtm >> gtm_ctl start -Z gtm_proxy -D /var/lib/pgsql/gtm_proxy1 >> gtm_ctl start -Z gtm_proxy -D /var/lib/pgsql/gtm_proxy2 >> pg_ctl start -Z datanode -D /var/lib/pgsql/data1 >> pg_ctl start -Z datanode -D /var/lib/pgsql/data2 >> pg_ctl start -Z coordinator -D /var/lib/pgsql/coord1 >> pg_ctl start -Z coordinator -D /var/lib/pgsql/coord2 >> >> Everything works fine till coord1. In the last step while starting >> coord2, I get this error: >> >> LOG: database system was interrupted; last known up at 2013-02-21 >> 02:50:33 PST >> FATAL: lock file "/tmp/.s.PGPOOL.6667.lock" already exists >> > Are you using the same port number in the coordinators for each one's connection pool? > HINT: Is another postmaster (PID 12892) using socket file >> "/tmp/.s.PGPOOL.6667"? >> LOG: database system was not properly shut down; automatic recovery in >> progress >> LOG: pool manager process (PID 12907) exited with exit code 1 >> LOG: terminating any other active server processes >> LOG: startup process (PID 12906) exited with exit code 2 >> LOG: aborting startup due to startup process failure >> >> >> Can anyone please help? >> >> >> >> > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > -- Mason Sharp StormDB - http://www.stormdb.com The Database Cloud Postgres-XC Support and Services |
|
From: kushal <kus...@gm...> - 2013-02-21 11:50:07
|
Forgot to add. This whole setup is tried on one single server. On 21 February 2013 03:47, kushal <kus...@gm...> wrote: > Hi > > I am using XC 1.0.2. I am trying to create the whole setup including gtm, > 2 gtm proxies, 2 coordinators and 2 datanodes. > > Ports Configured: > GTM: 16666 > GTM Proxy 1: 16667 > GTM Proxy 1: 16668 > Data Node 1: 15442 > Data Node 2: 15443 > Coordinator 1: 15432 > Coordinator 1: 15433 > > Coordinator 1 has gtm port configured to 16667 and Coordinator 2 to 16668. > > Next I try to start all the nodes. > gtm_ctl start -Z gtm -D /var/lib/pgsql/gtm > gtm_ctl start -Z gtm_proxy -D /var/lib/pgsql/gtm_proxy1 > gtm_ctl start -Z gtm_proxy -D /var/lib/pgsql/gtm_proxy2 > pg_ctl start -Z datanode -D /var/lib/pgsql/data1 > pg_ctl start -Z datanode -D /var/lib/pgsql/data2 > pg_ctl start -Z coordinator -D /var/lib/pgsql/coord1 > pg_ctl start -Z coordinator -D /var/lib/pgsql/coord2 > > Everything works fine till coord1. In the last step while starting coord2, > I get this error: > > LOG: database system was interrupted; last known up at 2013-02-21 > 02:50:33 PST > FATAL: lock file "/tmp/.s.PGPOOL.6667.lock" already exists > HINT: Is another postmaster (PID 12892) using socket file > "/tmp/.s.PGPOOL.6667"? > LOG: database system was not properly shut down; automatic recovery in > progress > LOG: pool manager process (PID 12907) exited with exit code 1 > LOG: terminating any other active server processes > LOG: startup process (PID 12906) exited with exit code 2 > LOG: aborting startup due to startup process failure > > > Can anyone please help? > > > > |
|
From: kushal <kus...@gm...> - 2013-02-21 11:47:49
|
Hi I am using XC 1.0.2. I am trying to create the whole setup including gtm, 2 gtm proxies, 2 coordinators and 2 datanodes. Ports Configured: GTM: 16666 GTM Proxy 1: 16667 GTM Proxy 1: 16668 Data Node 1: 15442 Data Node 2: 15443 Coordinator 1: 15432 Coordinator 1: 15433 Coordinator 1 has gtm port configured to 16667 and Coordinator 2 to 16668. Next I try to start all the nodes. gtm_ctl start -Z gtm -D /var/lib/pgsql/gtm gtm_ctl start -Z gtm_proxy -D /var/lib/pgsql/gtm_proxy1 gtm_ctl start -Z gtm_proxy -D /var/lib/pgsql/gtm_proxy2 pg_ctl start -Z datanode -D /var/lib/pgsql/data1 pg_ctl start -Z datanode -D /var/lib/pgsql/data2 pg_ctl start -Z coordinator -D /var/lib/pgsql/coord1 pg_ctl start -Z coordinator -D /var/lib/pgsql/coord2 Everything works fine till coord1. In the last step while starting coord2, I get this error: LOG: database system was interrupted; last known up at 2013-02-21 02:50:33 PST FATAL: lock file "/tmp/.s.PGPOOL.6667.lock" already exists HINT: Is another postmaster (PID 12892) using socket file "/tmp/.s.PGPOOL.6667"? LOG: database system was not properly shut down; automatic recovery in progress LOG: pool manager process (PID 12907) exited with exit code 1 LOG: terminating any other active server processes LOG: startup process (PID 12906) exited with exit code 2 LOG: aborting startup due to startup process failure Can anyone please help? |
