http://www.slony.info/bugzilla/show_bug.cgi?id=81

           Summary: duplicate key sl_nodelock-pkey and duplicate slon(8)
                    processes not detected
           Product: Slony-I
           Version: 1.2
          Platform: PC
        OS/Version: FreeBSD
            Status: NEW
          Severity: normal
          Priority: medium
         Component: slon
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: bseklecki at collaborativefusion.com
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


First reported 08/2008 by Shahaf Abileah, then found by Bill Moran at CFI.


http://www.mail-archive.com/slony1-general@lists.slony.info/msg02754.html

http://www.nabble.com/duplicate-key-sl_nodelock-pkey-td22246434.html

--------

In both cases, the users report that duplicate running SLON processes seem to
be the cause (hence, duplicate "node locks").  

Error #1 is the PgSQL error.

In our case, during a switchover drill, the SWITCHOVER command fails silently,
eventually timing out.

No errors from Slon/PgSQL are reported back to the user, which is problem #2.

-------------------

2009 Feb 27 06:32:04 -05:00 localslavedb [slon][27776] [local2] [err] 
slon[27776]: [20-1] [27776] FATAL localListenThread: "select 
"_database_name_prod".cleanupNodelock(); insert into
2009 Feb 27 06:32:04 -05:00 localslavedb [slon][27776] [local2] [err] 
slon[27776]: [20-2] "_database_name_prod".sl_nodelock values ( 2, 0, 
"pg_catalog".pg_backend_pid()); " - ERROR: duplicate key value violates
2009 Feb 27 06:32:04 -05:00 localslavedb [slon][27776] [local2] [err] 
slon[27776]: [20-3] unique constraint "sl_nodelock-pkey"

---------------------

duplicate key sl_nodelock-pkey and suplicate slon(8) processes not detected


-- 
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.