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

           Summary: Slony Watchdog failed starting up the child process
           Product: Slony-I
           Version: 2.0
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: low
         Component: slon
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: rnancy at afilias.info
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


At the server startup,   slony daemon crashed with the following error

FATAL localListenThread: "select "_xxxx".cleanupNodelock(); insert into
"_xxxx".sl_nodelock values ( 9151, 0,
"pg_catalog".pg_backend_pid()); " - ERROR: duplicate key value violates unique
constraint "sl_nodelock-pkey"
DETAIL: Key (nl_nodeid, nl_conncnt)=(9151, 0) already exists.
2013-07-23 07:10:16 UTC FATAL Do you already have a slon running against this
node?
2013-07-23 07:10:16 UTC FATAL Or perhaps a residual idle backend connection
from a dead slon?
2013-07-23 07:10:16 UTC DEBUG2 slon_abort() from pid=1699
2013-07-23 07:10:16 UTC FATAL main: localListenThread did not start
2013-07-23 07:10:16 UTC CONFIG slon: child terminated signal: 9; pid: 1699,
current worker pid: 1699
2013-07-23 07:10:16 UTC INFO slon: done

I know the origin of the duplicate key error, but I expected the Watchdog to
try every 10s to start the daemon again.
In my case it seems like the watchdog process died with the child process. 


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

The propose solution is to add a parameter in the slony configuration file that
set how many time the watchdog process will try before end of live.

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