Thu Jul 5 12:03:00 PDT 2007
- Previous message: [Slony1-general] Re: Backslashes inside an update statement for slonik are stripped
- Next message: [Slony1-general] New master failing; still trying to see old master?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Crisis today. Complete power failure leaves a corrupt table on old master. I did moveset() and dropnode() to reconfigure the cluster. The old master was node 2. New master is node 1. There are now just 2 slaves 3 and 4. For some reason however, when I try to fire up the slon on the master, it complains of node #2 does not exist right after reporting having init'd node 4. I have no clue what's going wrong here and hope not to have to undo and reconfig the cluster from scratch. These DBs are too large now for easy subscription during live processing. Any help much appreciated. ----------------------------------------- 2007-07-05 18:19:18 GMT CONFIG main: edb-replication version 1.1.5 starting up 2007-07-05 18:19:19 GMT CONFIG main: local node id = 1 2007-07-05 18:19:19 GMT CONFIG main: launching sched_start_mainloop 2007-07-05 18:19:19 GMT CONFIG main: loading current cluster configuration 2007-07-05 18:19:19 GMT CONFIG storeNode: no_id=3 no_comment='slave node 3' 2007-07-05 18:19:19 GMT CONFIG storeNode: no_id=4 no_comment='slave node 4' 2007-07-05 18:19:19 GMT CONFIG storePath: pa_server=3 pa_client=1 pa_conninfo="dbname=rt3_01 host=192.168.30.172 user=slonik password=foo.j1MiTikGop0rytQuedPid8 port=5432" pa_connretry=5 2007-07-05 18:19:19 GMT CONFIG storePath: pa_server=4 pa_client=1 pa_conninfo="dbname=rt3_01 host=192.168.30.173 user=slonik password=foo.j1MiTikGop0rytQuedPid8 port=5432" pa_connretry=5 2007-07-05 18:19:19 GMT CONFIG storeListen: li_origin=3 li_receiver=1 li_provider=3 2007-07-05 18:19:19 GMT CONFIG storeListen: li_origin=4 li_receiver=1 li_provider=4 2007-07-05 18:19:19 GMT CONFIG storeSet: set_id=1 set_origin=1 set_comment='RT3/VCASE replication set' 2007-07-05 18:19:19 GMT CONFIG storeSet: set_id=2 set_origin=1 set_comment='new set for adding tables' 2007-07-05 18:19:19 GMT CONFIG main: configuration complete - starting threads NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=12520 2007-07-05 18:19:19 GMT CONFIG enableNode: no_id=3 2007-07-05 18:19:19 GMT CONFIG enableNode: no_id=4 2007-07-05 18:19:19 GMT FATAL enableNode: unknown node ID 2 2007-07-05 18:19:19 GMT INFO remoteListenThread_4: disconnecting from 'dbname=rt3_01 host=192.168.30.173 user=slonik password=foo.j1MiTikGop0rytQuedPid8 port=5432' 2007-07-05 18:19:20 GMT INFO remoteListenThread_3: disconnecting from 'dbname=rt3_01 host=192.168.30.172 user=slonik password=foo.j1MiTikGop0rytQuedPid8 port=5432' -- ------------------------------------------------------------------------------- Jerry Sievers 732 365-2844 (work) Production Database Administrator 305 321-1144 (mobil WWW E-Commerce Consultant
- Previous message: [Slony1-general] Re: Backslashes inside an update statement for slonik are stripped
- Next message: [Slony1-general] New master failing; still trying to see old master?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list