Tue Jul 23 12:21:14 PDT 2013
- Previous message: [Slony1-general] Slony Watchdog failed starting up the child process
- Next message: [Slony1-general] Slony Watchdog failed starting up the child process
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Chris, On 13-07-23 03:07 PM, Christopher Browne wrote: > My intuition from seeing it say "FATAL" is that that's indicating > "death of process," and that there's not much coming back from it. > > This behaviour is pretty consistent with what happens with a Postgres > postmaster; if the attempt to start up fails due to seeming already to > have a postmaster, it doesn't retry, pg_ctl immediately gives up. In my case the slons are running in a separate server which I rebooted. > > By the way, is this possibly because of a zombied old connection that > got disconnected due to firewall glitch or such? If so, you should > probably see about lowering the TCP keepalive parameters both in the > slon.conf file and in postgresql.conf You're right, the duplicated key error was caused by a zombie old connection that got disconnected due to the slony server reboot. Thanks. -- Rose Nancy DBA - Afilias Canada Corp. Office: 416-673-4082 Mobile: 647-669-3295.
- Previous message: [Slony1-general] Slony Watchdog failed starting up the child process
- Next message: [Slony1-general] Slony Watchdog failed starting up the child process
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list