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. 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 (On postgresql.conf, see tcp_keepalives_(idle|interval|count), and on slon.conf, see tcp_keepalive, tcp_keepalive_(idle|interval|count).) On Tue, Jul 23, 2013 at 3:07 PM, Christopher Browne <[email protected]>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. > > 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 > > (On postgresql.conf, see tcp_keepalives_(idle|interval|count), and on > slon.conf, see tcp_keepalive, tcp_keepalive_(idle|interval|count).) >
_______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
