Tue May 30 05:04:10 PDT 2006
- Previous message: [Slony1-general] ERROR - slony_schema does not exist
- Next message: [Slony1-general] stack depth limit exceeded
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> the error occurs at > > 2006-05-29 16:48:35 PDT DEBUG2 remoteListenThread_1: start listening > for event origin 1 2006-05-29 16:48:35 PDT ERROR remoteListenThread_1: > "listen > "_cedarlane_repl_Event"; listen "_cedarlane_repl_Confirm"; select > "_cedarlane_repl".registerNodeConnection(2); " - ERROR: schema > "_cedarlane_repl" does not exist > > cluster name = cedarlane_repl; node 1 admin conninfo='host=localhost > dbname=cedarlane user=postgres port=5432'; node 2 admin > conninfo='host=10.1.0.93 dbname=cedarrep user=postgres port=5432'; init > cluster (id = 1, comment = 'Node 1 - cedarlane at localhost'); *snip* The problem here was localhost in the conninfo and the fact that the db cedarlane also exists on the slave node. > As long as they run on the same machine everything is good. That gave it away :) - Niels
- Previous message: [Slony1-general] ERROR - slony_schema does not exist
- Next message: [Slony1-general] stack depth limit exceeded
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list