Sat Sep 18 21:39:26 PDT 2004
- Previous message: [Slony1-general] Help regarding Slony Code
- Next message: [Slony1-general] update after alter table crashing...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I am replicating a database on the same installation. 8.0gb replicates to 7.4gb and 8.0gb_replica. gb ---> gb_replica both on an 8.0b2 installation. | +--> gb on an 7.4 installation. This set up may be somewhat strange, but it *should* work. IMHO. When I start the three slon processes, the ones against 8.0 report that there is already a listener on the port. The logs are at the bottom of this message. Also when I try to kill -TERM the slon processes one set does not respond. This may be the cause of my problem? Can someone point out a configuration mistake? Or is this a bug? Starting up slon processes -------------------------- slon gb "dbname=gb user=postgres port=5434 host=localhost" > slon_gb_74.out 2>&1 & slon gb "dbname=gb user=postgres port=5430 host=localhost" > slon_gb_80.out 2>&1 & slon gb "dbname=gb_replica user=postgres port=5430 host=localhost" > slon_gbREP_80.out 2>&1 & This is my setup: ------------------ node | comment | active --------+---------------------+------------- Node 1 | gb 7.4 5434 | Is Active Node 2 | gb 8.0 5430 | Is Active Node 3 | gb_replica 8.0 5430 | Is Active (3 rows) Client Node | Connects to Server Node | Via connection -------------+-------------------------+---------------------------------------------------------- Node 1 | Node 2 | dbname=gb host=localhost port=5430 user=postgres Node 1 | Node 3 | dbname=gb_replica host=localhost port=5430 user=postgres Node 2 | Node 1 | dbname=gb host=localhost port=5434 user=postgres Node 2 | Node 3 | dbname=gb_replica host=localhost port=5430 user=postgres Node 3 | Node 1 | dbname=gb host=localhost port=5434 user=postgres Node 3 | Node 2 | dbname=gb host=localhost port=5430 user=postgres (6 rows) Node | Listens to | Via --------+-------------+-------- Node 1 | Node 2 | Node 2 Node 1 | Node 3 | Node 3 Node 2 | Node 1 | Node 1 Node 2 | Node 3 | Node 3 Node 3 | Node 1 | Node 1 Node 3 | Node 2 | Node 2 (6 rows) Set | Provider Node | Receiver Node | Forwardable | Active -----+---------------+---------------+-------------+-------- 1 | 2 | 3 | t | t 1 | 2 | 1 | t | t (2 rows) Logs on Start up: ------------------ $ cat slon_gb_80.out CONFIG main: local node id = 2 CONFIG main: loading current cluster configuration CONFIG storeNode: no_id=1 no_comment='gb 7.4 5434' CONFIG storeNode: no_id=3 no_comment='gb_replica 8.0 5430' CONFIG storePath: pa_server=1 pa_client=2 pa_conninfo="dbname=gb host=localhost port=5434 user=postgres " pa_connretry=10 CONFIG storePath: pa_server=3 pa_client=2 pa_conninfo="dbname=gb_replica host=localhost port=5430 user= postgres" pa_connretry=10 CONFIG storeListen: li_origin=1 li_receiver=2 li_provider=1 CONFIG storeListen: li_origin=3 li_receiver=2 li_provider=3 CONFIG storeSet: set_id=1 set_origin=2 set_comment='gb tables' CONFIG main: configuration complete - starting threads FATAL localListenThread: Another slon daemon is serving this node already cat slon_gbREP_80.out CONFIG main: local node id = 3 CONFIG main: loading current cluster configuration CONFIG storeNode: no_id=1 no_comment='gb 7.4 5434' CONFIG storeNode: no_id=2 no_comment='gb 8.0 5430' CONFIG storePath: pa_server=1 pa_client=3 pa_conninfo="dbname=gb host=localhost port=5434 user=postgres" pa_connretry=10 CONFIG storePath: pa_server=2 pa_client=3 pa_conninfo="dbname=gb host=localhost port=5430 user=postgres" pa_connretry=10 CONFIG storeListen: li_origin=1 li_receiver=3 li_provider=1 CONFIG storeListen: li_origin=2 li_receiver=3 li_provider=2 CONFIG storeSet: set_id=1 set_origin=2 set_comment='gb tables' WARN remoteWorker_wakeup: node 2 - no worker thread CONFIG storeSubscribe: sub_set=1 sub_provider=2 sub_forward='t' WARN remoteWorker_wakeup: node 2 - no worker thread CONFIG enableSubscription: sub_set=1 WARN remoteWorker_wakeup: node 2 - no worker thread CONFIG main: configuration complete - starting threads FATAL localListenThread: Another slon daemon is serving this node already cat slon_gb_74.out CONFIG main: local node id = 1 CONFIG main: loading current cluster configuration CONFIG storeNode: no_id=2 no_comment='gb 8.0 5430' CONFIG storeNode: no_id=3 no_comment='gb_replica 8.0 5430' CONFIG storePath: pa_server=2 pa_client=1 pa_conninfo="dbname=gb host=localhost port=5430 user=postgre s" pa_connretry=10 CONFIG storePath: pa_server=3 pa_client=1 pa_conninfo="dbname=gb_replica host=localhost port=5430 user =postgres" pa_connretry=10 CONFIG storeListen: li_origin=2 li_receiver=1 li_provider=2 CONFIG storeListen: li_origin=3 li_receiver=1 li_provider=3 CONFIG storeSet: set_id=1 set_origin=2 set_comment='gb tables' WARN remoteWorker_wakeup: node 2 - no worker thread CONFIG storeSubscribe: sub_set=1 sub_provider=2 sub_forward='t' WARN remoteWorker_wakeup: node 2 - no worker thread CONFIG enableSubscription: sub_set=1 WARN remoteWorker_wakeup: node 2 - no worker thread CONFIG main: configuration complete - starting threads CONFIG enableNode: no_id=2 CONFIG enableNode: no_id=3
- Previous message: [Slony1-general] Help regarding Slony Code
- Next message: [Slony1-general] update after alter table crashing...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list