Peter Geoghegan <peter.geoghegan86 at gmail.com> writes:
> --------------------------------------------------------------------------------
> Summary of event info
>  Origin  Min SYNC  Max SYNC Min SYNC Age Max SYNC Age
> ================================================================================
>       1     28741     29914     00:00:00     02:58:00    0
>       2        18        18 1 day 01:24:00 1 day 01:24:00    1
>       3        26        26 1 day 01:19:00 1 day 01:19:00    1
>
>
> ---------------------------------------------------------------------------------
> Summary of sl_confirm aging
>    Origin   Receiver   Min SYNC   Max SYNC  Age of latest SYNC  Age of
> eldest SYNC
> =================================================================================
>         1          2      28741      28741      03:03:00      03:03:00    1
>         1          3      29800      29913      00:00:00      00:18:00    0
>         2          1         18         18  1 day 01:19:00  1 day 01:19:00    1
>         2          3         18         18  1 day 01:19:00  1 day 01:19:00    1
>         3          1         26         26  1 day 01:19:00  1 day 01:19:00    1
>         3          2         26         26  1 day 01:24:00  1 day 01:24:00    1

This points us towards the problem...  Apparently node #1 isn't
getting events from nodes 2 and 3, and 2&3 aren't getting events from
each other.

> Tests for node 3 - DSN = dbi:Pg:dbname=lustre_slave host=10.0.0.82
> user=postgres password=my_password
> ========================================
> DBI connect('dbname=lustre_slave host=10.0.0.82 user=postgres
> password=my_password','',...) failed: FATAL:  database "lustre_slave"
> does not exist at ./test_slony_state-dbi.pl line 79
>
> Tests for node 2 - DSN = dbi:Pg:dbname=lustre_slave host=10.0.0.81
> user=postgres password=my_password
> ========================================
> DBI connect('dbname=lustre_slave host=10.0.0.81 user=postgres
> password=my_password','',...) failed: FATAL:  database "lustre_slave"
> does not exist at ./test_slony_state-dbi.pl line 79

... And this contributes towards telling us something about why ...

> I have no idea why test_slony_state-dbi.pl cannot connect to the two
> slave nodes's DBs - the databases are plainly present on the nodes -
> I can connect directly to them from the machine that I'm running the
> test on, and see everything is in order.
>
> Why might this problem occur?

This is the point at which it ceases to be analyzed as a "Slony-I
problem," and as a "what's busted with PostgreSQL connections?" 
problem.

Apparently the configuration that you've set up, e.g.

   dbname=lustre_slave host=10.0.0.81 user=postgres password=my_password
   dbname=lustre_slave host=10.0.0.82 user=postgres password=my_password

*isn't* working.

Figure out the difference between that and the legitimate
configuration and then you can run slonik "STORE PATH" requests with
the fixed connection info which should resolve the problem.
-- 
output = ("cbbrowne" "@" "ca.afilias.info")
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"