This is the result from test_slony_state-dbi.pl

DSN: dbi:Pg:dbname=MONSOON;host=localhost;port=5432
===========================
Rummage for DSNs
=============================
Query:

   select p.pa_server, p.pa_conninfo
   from "_MONSOONCLUSTER".sl_path p
   where exists (select * from "_MONSOONCLUSTER".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=MONSOON host=192.168.1.151 port=5432
user=postgres
========================================
pg_listener info:
Pages: 165
Tuples: 5

Size Tests
================================================
       sl_log_1     17597 591832.000000
       sl_log_2         0  0.000000
      sl_seqlog         7 12.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      6872      6879     00:00:00     00:14:00    0
      1     13934     13947     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      13934      13946      00:01:00      00:13:00    0
        2          1       6872       6879      00:00:00      00:14:00    0


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

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


Tests for node 2 - DSN = dbname=MONSOON host=192.168.1.152 port=5432
user=postgres
========================================
pg_listener info:
Pages: 165
Tuples: 5

Size Tests
================================================
       sl_log_1     17597 591832.000000
       sl_log_2         0  0.000000
      sl_seqlog         7 12.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      6872      6879     00:00:00     00:14:00    0
      1     13934     13947     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      13934      13946      00:01:00      00:13:00    0
        2          1       6872       6879      00:00:00      00:14:00    0


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

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

sh: -s: not found


Sending message thus - | -s "Slony State Test Warning - Cluster
MONSOONCLUSTER"
Message:


Node: 1 sl_log_1 tuples = 591832 > 200000
================================================
Number of tuples in Slony-I table sl_log_1 is 591832 which
exceeds 200000.

You may wish to investigate whether or not a node is down, or perhaps
if sl_confirm entries have not been propagating properly.


Node: 2 sl_log_1 tuples = 591832 > 200000
================================================
Number of tuples in Slony-I table sl_log_1 is 591832 which
exceeds 200000.

You may wish to investigate whether or not a node is down, or perhaps
if sl_confirm entries have not been propagating properly.
any idea?

Thanks in advance for your reply.

J



On 10/16/06, Christopher Browne <cbbrowne at ca.afilias.info> wrote:
>
> "Junaili Lie" <junaili at gmail.com> writes:
> > I am wondering if anyone has any sight as to why this is happening,
> > how to solve this issue and how to prevent this issue from happening
> > again in the future.
>
> What you have provided as information is not particularly helpful to
> diagnose the problem.
>
> What you need to do is to run one of the scripts in /tools/ for
> testing system state:
> test_slony_state.pl
> test_slony_state-dbi.pl
>
> (One uses Pg; the other uses DBI...)
>
> Running them should give some better clue as to where the problem
> lies.
> --
> output = reverse("ofni.sailifa.ac" "@" "enworbbc")
> <http://dba2.int.libertyrms.com/>
> Christopher Browne
> (416) 673-4124 (land)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://gborg.postgresql.org/pipermail/slony1-general/attachments/20061016/c60f7da1/attachment.html