I have a slony pair that I just started the initial copy. It hit a table set where it encountered a fatal postgres error due to an encoding issue. After encountering the error, I unsubscribed the table set to see if I could get slony to continue with the rest of the sets. slony now says:
remoteWorkerThread_1: node -1 not found in runtime configuration data copy for set 75 failed - sleep 30 seconds I restarted the slon processes on both servers, and cannot seem to clear this state. Its syncing all the table sets subscribed so far (1 - 74), but I cannot get slony to move beyond 75, even though its been unsubscribed. Does anyone know how to get out of this state? I don't know why it would say there's a node -1 either, as my nodes are 1 and 2. I'm looking into the encoding error separately, and will provide more information if that turns out to be an issue. Doug Knight
_______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
