Karl Denninger wrote: > I had posted a compatibility question related to Slony 2.0.2 and > Postgres 8.4 previous, and got back that there were some warnings at > issue, but no other particular problems. > > The current configuration has 1 master (node 2) and two slaves (1 and > 3); I attempted to add a node #4 with 8.4.0 running on the same machine > as the master. > > The server is in its own directory, on its own port (55432) and all the > tables are present. > > I've got the following config: > > In <slonik.preamble> > CLUSTER NAME = tickerforum; > node 1 admin conninfo='dbname=ticker host=genesis.denninger.net > user=slony port=55432 password=xxxx'; > node 2 admin conninfo='dbname=ticker host=colo1.denninger.net user=slony > password=xxxx port=5432'; > node 3 admin conninfo='dbname=ticker host=genesis.denninger.net > user=slony password=xxxx port=5432'; > node 4 admin conninfo='dbname=ticker host=colo1.denninger.net user=slony > password=xxxx port=55432'; > > > Then I use (which has worked to set up the other two) > > > include <slonik.preamble>; > store node (id=4, comment='Client #1, Node #4', event node=2); > > > followed by: > > include <slonik.preamble>; > store path (server=4, client=2, conninfo='dbname=ticker > host=colo1.denninger.net user=slony port=55432 password=xxxx'); > store path (server=2, client=4, conninfo='dbname=ticker > host=colo1.denninger.net user=slony port=5432 password=xxxx'); > > To store the client and server paths > > Then to start replication: > > include <slonik.preamble>; > subscribe set (id=1, provider=2, receiver=4, forward=false); > > The logfile, however, shows this: > Aug 21 23:50:24 tickerforum slon[61661]: [400-1] INFO about to > monitor_subscriber_query - pulling big actionid list 17933184 > Aug 21 23:50:26 tickerforum slon[61661]: [401-1] INFO about to > monitor_subscriber_query - pulling big actionid list 17933184 > Aug 21 23:50:28 tickerforum slon[61661]: [402-1] INFO about to > monitor_subscriber_query - pulling big actionid list 17933184 > Aug 21 23:50:30 tickerforum slon[61661]: [403-1] INFO about to > monitor_subscriber_query - pulling big actionid list 17933184 > Aug 21 23:50:32 tickerforum slon[61661]: [404-1] INFO about to > monitor_subscriber_query - pulling big actionid list 17933184 > > Aug 21 23:50:34 tickerforum slon[61661]: [405-1] INFO about to > monitor_subscriber_query - pulling big actionid list 17933184 > Aug 21 23:50:36 tickerforum slon[61661]: [406-1] INFO > cleanupThread: 0.036 seconds for cleanupEvent() > Aug 21 23:50:36 tickerforum slon[61661]: [407-1] INFO about to > monitor_subscriber_query - pulling big actionid list 17933184 > Aug 21 23:50:38 tickerforum slon[61661]: [408-1] INFO about to > monitor_subscriber_query - pulling big actionid list 17933184 > Aug 21 23:50:40 tickerforum slon[61661]: [409-1] INFO about to > monitor_subscriber_query - pulling big actionid list 17933184 > Aug 21 23:50:42 tickerforum slon[61661]: [410-1] INFO about to > monitor_subscriber_query - pulling big actionid list 17933184 > > Over and over again - but the COPY is never run so it never goes into > normal monitoring mode. > > The other two clients are running normally - no problems. > > Any ideas why this is looping on that particular message and never > actually cranks up? > > An attempt to upgrade to 2.0.3-rc2 failed with a complaint during the > function upgrade about incompatible typing - since I do not want to kill > replication and rebuild it from scratch, I stopped there and backed out > back to 2.0.2. > > A run of the Perl "monitoring" script elucidates the following: > > $ perl /usr/local/pgsql/bin/test_slony_state-dbi.pl --database=ticker > --cluster=tickerforum > DSN: dbi:Pg:dbname=ticker; > =========================== > Rummage for DSNs > ============================= > Query: > > select p.pa_server, p.pa_conninfo > from "_tickerforum".sl_path p > -- where exists (select * from "_tickerforum".sl_subscribe s where > -- (s.sub_provider = p.pa_server or > s.sub_receiver = p.pa_server) and > -- sub_active = 't') > group by pa_server, pa_conninfo; > > > Tests for node 1 - DSN = dbi:Pg:dbname=ticker host=genesis.denninger.net > user=slony port=55432 password=orishaoku > ======================================== > pg_listener info: > Pages: 1 > Tuples: 1 > > Size Tests > ================================================ > sl_log_1 0 0.000000 > sl_log_2 0 0.000000 > sl_seqlog 5 743.000000 > > Listen Path Analysis > =================================================== > No problems found with sl_listen > > > -------------------------------------------------------------------------------- > Summary of event info > Origin Min SYNC Max SYNC Min SYNC Age Max SYNC Age > ================================================================================ > 2 6274244 6274967 -00:59:00 -00:19:00 0 > 4 1 2 -00:46:00 -00:45:00 0 > 1 25 27 00:29:00 1 day 23:18:00 0 > 3 25 26 00:21:00 1 day 23:18:00 0 > > > --------------------------------------------------------------------------------- > Summary of sl_confirm aging > Origin Receiver Min SYNC Max SYNC Age of latest SYNC Age of > eldest SYNC > ================================================================================= > 1 2 25 27 -00:35:00 1 day > 22:18:00 0 > 1 3 27 27 00:21:00 00:21:00 0 > 1 4 0 27 -00:45:00 00:14:00 0 > 2 1 6274455 6274967 00:00:00 00:17:00 0 > 2 3 6274455 6274965 00:00:00 00:17:00 0 > 2 4 0 6274963 -00:59:00 00:14:00 0 > 3 1 26 26 00:21:00 00:21:00 0 > 3 2 25 26 -00:38:00 1 day > 22:18:00 0 > 3 4 0 26 -00:45:00 00:14:00 0 > 4 1 0 2 00:13:00 00:14:00 0 > 4 2 0 2 -00:46:00 00:14:00 0 > 4 3 0 2 -00:45:00 00:14:00 0 > > > ------------------------------------------------------------------------------ > > Listing of old open connections on node 1 > Database PID User Query > Age Query > ================================================================================ > > > Tests for node 4 - DSN = dbi:Pg:dbname=ticker host=colo1.denninger.net > user=slony port=55432 password=orishaoku > ======================================== > pg_listener info: > Pages: 0 > Tuples: 0 > > Size Tests > ================================================ > sl_log_1 0 0.000000 > sl_log_2 0 0.000000 > sl_seqlog 0 0.000000 > > Listen Path Analysis > =================================================== > No problems found with sl_listen > > -------------------------------------------------------------------------------- > Summary of event info > Origin Min SYNC Max SYNC Min SYNC Age Max SYNC Age > ================================================================================ > 4 2 2 00:13:00 00:13:00 0 > 2 6274595 6274967 00:00:00 00:13:00 0 > > > --------------------------------------------------------------------------------- > Summary of sl_confirm aging > Origin Receiver Min SYNC Max SYNC Age of latest SYNC Age of > eldest SYNC > ================================================================================= > 1 2 27 27 00:24:00 00:24:00 0 > 1 3 27 27 01:21:00 01:21:00 1 > 1 4 27 27 00:14:00 00:14:00 0 > 2 1 6274868 6274964 01:00:00 01:03:00 1 > 2 3 6274870 6274965 01:00:00 01:03:00 1 > 2 4 6274595 6274967 00:00:00 00:13:00 0 > 3 1 26 26 01:21:00 01:21:00 1 > 3 2 26 26 00:21:00 00:21:00 0 > 3 4 26 26 00:14:00 00:14:00 0 > 4 1 2 2 00:14:00 00:14:00 0 > 4 2 2 2 00:13:00 00:13:00 0 > 4 3 2 2 00:14:00 00:14:00 0 > > > ------------------------------------------------------------------------------ > > Listing of old open connections on node 4 > Database PID User Query > Age Query > ================================================================================ > > > Tests for node 3 - DSN = dbi:Pg:dbname=ticker host=genesis.denninger.net > user=slony port=5432 password=orishaoku > ======================================== > pg_listener info: > Pages: 1 > Tuples: 1 > > Size Tests > ================================================ > sl_log_1 0 0.000000 > sl_log_2 0 0.000000 > sl_seqlog 8 1113.000000 > > Listen Path Analysis > =================================================== > No problems found with sl_listen > > -------------------------------------------------------------------------------- > Summary of event info > Origin Min SYNC Max SYNC Min SYNC Age Max SYNC Age > ================================================================================ > 2 6273791 6274967 -00:59:00 -00:03:00 0 > 1 25 27 00:29:00 1 day 23:18:00 0 > 4 1 2 -00:46:00 -00:45:00 0 > 3 25 26 00:21:00 1 day 23:18:00 0 > > > --------------------------------------------------------------------------------- > Summary of sl_confirm aging > Origin Receiver Min SYNC Max SYNC Age of latest SYNC Age of > eldest SYNC > ================================================================================= > 1 2 25 27 -00:35:00 1 day > 22:18:00 0 > 1 3 27 27 00:21:00 00:21:00 0 > 1 4 0 27 -00:45:00 00:14:00 0 > 2 1 6274662 6274964 00:00:00 00:10:00 0 > 2 3 6274665 6274967 00:00:00 00:10:00 0 > 2 4 0 6274963 -00:59:00 00:14:00 0 > 3 1 26 26 00:21:00 00:21:00 0 > 3 2 25 26 -00:38:00 1 day > 22:18:00 0 > 3 4 0 26 -00:45:00 00:14:00 0 > 4 1 0 2 -00:45:00 00:14:00 0 > 4 2 0 2 -00:46:00 00:14:00 0 > 4 3 2 2 00:13:00 00:13:00 0 > > > ------------------------------------------------------------------------------ > > Listing of old open connections on node 3 > Database PID User Query > Age Query > ================================================================================ > > > Tests for node 2 - DSN = dbi:Pg:dbname=ticker host=colo1.denninger.net > user=slony port=5432 password=orishaoku > ======================================== > pg_listener info: > Pages: 1 > Tuples: 1 > > Size Tests > ================================================ > sl_log_1 334 9884.000000 > sl_log_2 0 0.000000 > sl_seqlog 4 173.000000 > > Listen Path Analysis > =================================================== > No problems found with sl_listen > > -------------------------------------------------------------------------------- > Summary of event info > Origin Min SYNC Max SYNC Min SYNC Age Max SYNC Age > ================================================================================ > 2 6274650 6274968 00:00:00 00:10:00 0 > 4 2 2 00:13:00 00:13:00 0 > 1 27 27 01:29:00 01:29:00 1 > 3 26 26 01:21:00 01:21:00 1 > > > --------------------------------------------------------------------------------- > Summary of sl_confirm aging > Origin Receiver Min SYNC Max SYNC Age of latest SYNC Age of > eldest SYNC > ================================================================================= > 1 2 27 27 00:24:00 00:24:00 0 > 1 3 27 27 01:21:00 01:21:00 1 > 1 4 27 27 00:14:00 00:14:00 0 > 2 1 6274948 6274964 01:00:00 01:00:00 1 > 2 3 6274945 6274965 01:00:00 01:00:00 1 > 2 4 6274650 6274963 00:00:00 00:10:00 0 > 3 1 26 26 01:21:00 01:21:00 1 > 3 2 26 26 00:21:00 00:21:00 0 > 3 4 26 26 00:14:00 00:14:00 0 > 4 1 2 2 01:13:00 01:13:00 1 > 4 2 2 2 00:13:00 00:13:00 0 > 4 3 2 2 01:13:00 01:13:00 1 > > > ------------------------------------------------------------------------------ > > Listing of old open connections on node 2 > Database PID User Query > Age Query > ================================================================================ > > > This looks ok - nothing that appears hung, but no replication starts..... > > What am I doing wrong here? This same set of setup files (with the > appropriate names) worked to add the third node... > > -- Karl > > > > _______________________________________________ > Slony1-general mailing list > [email protected] > http://lists.slony.info/mailman/listinfo/slony1-general > Following up on this, I did a "DROP NODE" with the slons running, then re-ran the config scripts. Now I'm getting this - the same thing I was getting last night:
Aug 22 00:04:11 tickerforum slon[66032]: [129-1] INFO copy_set 1 Aug 22 00:04:11 tickerforum slon[66032]: [130-1] CONFIG version for "dbname=ticker host=colo1.denninger.net user=slony port=5432 password=xxxxx" is 80306 Aug 22 00:04:11 tickerforum slon[66032]: [131-1] CONFIG remoteWorkerThread_2: connected to provider DB Aug 22 00:04:11 tickerforum slon[66032]: [132-1] CONFIG remoteWorkerThread_2: prepare to copy table "public"."banned_ip" Aug 22 00:04:11 tickerforum slon[66032]: [133-1] ERROR remoteWorkerThread_2: Could not lock table "public"."banned_ip" on subscriber Aug 22 00:04:11 tickerforum slon[66032]: [134-1] WARN remoteWorkerThread_2: data copy for set 1 failed - sleep 60 seconds And then this repeats every 60 seconds. This is the lock error I was seeing before; I don't get it..... -- Karl
begin:vcard fn:Karl Denninger n:Denninger;Karl org:Cuda Systems LLC adr;dom:;;314 Olde Post Road;Niceville;FL;32578 email;internet:[email protected] tel;work:850-376-9364 tel;fax:850-897-9364 x-mozilla-html:TRUE url:http://market-ticker.org version:2.1 end:vcard
_______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
