Hi Chaps,

I've got a test setup with slony replicating two databases on the same postgres instance, e.g. I've a table "price" in database SEE and SEE_REP on the same host and I'm replicating it with slony from SEE to SEE_REP.

What I've tried to do is pg_dumpall then re-initdb the server, reload the dump back in and then run REPAIR CONFIG.

I was hoping I could restart slony and it'd work. No luck.

The slon that runs against the subscriber database "SEE_REP" starts up and appears to be running OK as far as I can tell, however the slon on the origin database "SEE" never connects and constantly logs:

2008-09-16_191105 BST DEBUG2 remoteListenThread_2: queue event 2,297599 SYNC
2008-09-16_191105 BST DEBUG2 remoteListenThread_2: queue event 2,297600 SYNC
2008-09-16_191105 BST DEBUG2 remoteListenThread_2: queue event 2,297601 SYNC
2008-09-16_191105 BST DEBUG2 remoteListenThread_2: queue event 2,297602 SYNC
2008-09-16_191105 BST DEBUG2 remoteListenThread_2: queue event 2,297603 SYNC
2008-09-16_191105 BST DEBUG2 remoteWorkerThread_2: Received event 2,297347 RESET_CONFIG
2008-09-16_191105 BST DEBUG2 slon: child terminated status: 11; pid: 1956, current worker pid: 1956
2008-09-16_191105 BST DEBUG1 slon: restart of worker in 10 seconds


I know we've seen this before and the error is not informative at all, but does anyone have any idea what could be going off here?

I've seen the "queue event", "RESET_CONFIG" and "child terminated status: 11" quite often when I mess something up and I can never find any documentation on the slony site about them (I looked here: http://www.slony.info/documentation/loganalysis.html)

The output of test_slony_state-dbi.pl is below, to my uneducated eye it doesn't show anything wrong?

To be honest I knew doing this would be asking for trouble, but does anyone have any pointers? If not could someone explain what the last four lines in the log mean? From what I can gather 11 is some sort of unknown error?

Ta
Glyn


DSN: dbi:Pg:dbname=SEE_REP;host=192.168.1.111;user=postgres;
===========================
Rummage for DSNs
=============================
Query:

   select p.pa_server, p.pa_conninfo
   from "_test_replication".sl_path p
--   where exists (select * from "_test_replication".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 = dbname=SEE host=192.168.1.111 user=slony
========================================
pg_listener info:
Pages: 0
Tuples: 0

Size Tests
================================================
       sl_log_1         0  0.000000
       sl_log_2         0  0.000000
      sl_seqlog         8 253.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    297346    297603     00:25:00     02:48:00    0
      1    297421    297421     02:48:00     02:48:00    1


---------------------------------------------------------------------------------
Summary of sl_confirm aging
   Origin   Receiver   Min SYNC   Max SYNC  Age of latest SYNC  Age of eldest SYNC
=================================================================================
        1          2     297421     297421      02:48:00      02:48:00    1
        2          1     297346     297346      02:48:00      02:48:00    1


------------------------------------------------------------------------------

Listing of old open connections
       Database             PID            User    Query Age                Query
================================================================================


Tests for node 2 - DSN = dbname=SEE_REP host=192.168.1.111 user=slony
========================================
pg_listener info:
Pages: 0
Tuples: 0

Size Tests
================================================
       sl_log_1         0  0.000000
       sl_log_2         0  0.000000
      sl_seqlog         8 253.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    297346    297603     00:25:00     02:48:00    0
      1    297421    297421     02:48:00     02:48:00    1


---------------------------------------------------------------------------------
Summary of sl_confirm aging
   Origin   Receiver   Min SYNC   Max SYNC  Age of latest SYNC  Age of eldest SYNC
=================================================================================
        1          2     297421     297421      02:48:00      02:48:00    1
        2          1     297346     297346      02:48:00      02:48:00    1


------------------------------------------------------------------------------

Listing of old open connections
       Database             PID            User    Query Age                Query
================================================================================