Hmm, I wrote the original version of that script - it's just designed to 
determine whether active slon subscribers are keeping up.

I also use the separate check_slon on each node to determine whether the 
slon process is actually running or not.

In other words you need to use the check_slony_cluster against the 
master database, and the check_slon for each node.

I don't know enough about slon to determine whether you can check the 
whole replication array and nodes using the (master) database alone.

If you discover that you can, please could you post any ammendments for 
  either script.

Thanks

John

Marc G. Fournier wrote:
> 
> # ./check_slony_cluster.sh dns ams localhost
> Password for user pgsql:
> OK - 3 nodes in sync
> 
> 2 of the 3 nodes weren't even running, nor have been for >24 hours ...
> 
> ----
> Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy at hub.org           Yahoo!: yscrappy              ICQ: 7615664
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general