bugzilla-daemon at main.slony.info bugzilla-daemon at main.slony.info
Tue Oct 6 08:32:31 PDT 2015
http://www.slony.info/bugzilla/show_bug.cgi?id=361

           Summary: resubscribe node flat out doesn't work
           Product: Slony-I
           Version: 2.0
          Platform: PC
        OS/Version: Mac OS
            Status: NEW
          Severity: enhancement
          Priority: low
         Component: stored procedures
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: ttignor at akamai.com
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


I am developing with slony1-2.2.4. I have setup two nodes replicating from a
single producer and I'm simply trying to make one of the current subscribers
replicate from the other. I understand the single purpose of the RESUBSCRIBE
NODE operation is to make this happen. So I have created a resubscribe node
script but everywhere I run it returns the error "subscribeSet() must be called
on origin." Eventually I discovered that even while running on the origin host,
slonik reaches out to the new provider host to generate the error (See the
session below. I recreated the function on the new provider with "YYY" markup.)
I am completely blocked with the resubscribe operation now. Thanks in advance
for any insights.

root at ams9.nss1.tn:/tmp# cat doresub-2.slk 
cluster name = ams_cluster;
node 1 admin
      conninfo='dbname=ams
      host=198.18.102.35
      user=ams_slony
      sslmode=verify-ca
      sslcert=/usr/local/akamai/.ams_certs/complete-ams_slony.crt
      sslkey=/usr/local/akamai/.ams_certs/ams_slony.private_key
      sslrootcert=/usr/local/akamai/etc/ssl_ca/canonical_ca_roots.pem';
node 3 admin
      conninfo='dbname=ams
      host=198.18.102.35
      user=ams_slony
      sslmode=verify-ca
      sslcert=/usr/local/akamai/.ams_certs/complete-ams_slony.crt
      sslkey=/usr/local/akamai/.ams_certs/ams_slony.private_key
      sslrootcert=/usr/local/akamai/etc/ssl_ca/canonical_ca_roots.pem';

resubscribe node (origin = 1, provider = 3, receiver = 2);
root at ams9.nss1.tn:/tmp# 
root at ams9.nss1.tn:/tmp# slonik doresub-2.slk      
doresub-2.slk:19: PGRES_FATAL_ERROR lock table "_ams_cluster".sl_event_lock,
"_ams_cluster".sl_config_lock;select "_ams_cluster".resubscribeNode(1, 3, 2); 
- ERROR:  Slony-I: subscribeSet() YYY must be called on origin
root at ams9.nss1.tn:/tmp# 
root at ams9.nss1.tn:/tmp# emacs doresub-2.slk 
root at ams9.nss1.tn:/tmp# cat doresub-2.slk 
cluster name = ams_cluster;
node 1 admin
      conninfo='dbname=ams
      host=198.18.102.35
      user=ams_slony
      sslmode=verify-ca
      sslcert=/usr/local/akamai/.ams_certs/complete-ams_slony.crt
      sslkey=/usr/local/akamai/.ams_certs/ams_slony.private_key
      sslrootcert=/usr/local/akamai/etc/ssl_ca/canonical_ca_roots.pem';

resubscribe node (origin = 1, provider = 3, receiver = 2);
root at ams9.nss1.tn:/tmp# 
root at ams9.nss1.tn:/tmp# slonik doresub-2.slk      
doresub-2.slk:11: ERROR: no admin conninfo for node 3
root at ams9.nss1.tn:/tmp#

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Slony1-bugs mailing list