Andrew,

[note: I love that domain name on your email address, btw]

Not much, honestly. Just prior to invoking slony, I see this (after an =

earlier slony-induced restart, after which I did confirm that I could =

connect via psql and execute queries normally):

May 12 00:42:41 srv3 postgres[8694]: [87-1] LOG:  database system was =

not properly shut down; automatic recovery in progress
May 12 00:42:41 srv3 postgres[8694]: [88-1] LOG:  redo starts at 28/25DB3B6C
May 12 00:42:41 srv3 postgres[8694]: [89-1] LOG:  record with zero =

length at 28/25DB6AE8
May 12 00:42:41 srv3 postgres[8694]: [90-1] LOG:  redo done at 28/25DB6AC0
May 12 00:42:41 srv3 postgres[8694]: [91-1] LOG:  database system is ready
May 12 00:42:41 srv3 postgres[8694]: [92-1] LOG:  transaction ID wrap =

limit is 2147484146, limited by database "postgres"
May 12 00:42:51 srv3 slon[8571]: [1-1] 2007-05-12 00:42:51 CDT CONFIG =

main: slon version 1.2.9 starting up
May 12 00:42:51 srv3 slon[8698]: [2-1] 2007-05-12 00:42:51 CDT CONFIG =

main: local node id =3D 3

[... then, all heck breaks loose, and then the restart ...]

May 12 00:42:53 srv3 slon[8698]: [54-1] 2007-05-12 00:42:53 CDT FATAL  =

syncThread: "select =

"_srv1_srv2_cluster".createEvent('_srv1_srv2_cluster', 'SYNC', NULL);" -
May 12 00:42:53 srv3 slon[8698]: [54-2]  server closed the connection =

unexpectedly
May 12 00:42:53 srv3 slon[8698]: [54-3]         This probably means the =

server terminated abnormally
May 12 00:42:53 srv3 slon[8698]: [54-4]         before or while =

processing the request.
May 12 00:42:53 srv3 postgres[7320]: [82-1] LOG:  server process (PID =

8714) was terminated by signal 11
May 12 00:42:53 srv3 postgres[7320]: [83-1] LOG:  terminating any other =

active server processes
May 12 00:42:53 srv3 postgres[8704]: [83-1] WARNING:  terminating =

connection because of crash of another server process
May 12 00:42:53 srv3 postgres[8704]: [83-2] DETAIL:  The postmaster has =

commanded this server process to roll back the current transaction and
exit, because another server
May 12 00:42:53 srv3 postgres[8704]: [83-3]  process exited abnormally =

and possibly corrupted shared memory.
May 12 00:42:53 srv3 postgres[8704]: [83-4] HINT:  In a moment you =

should be able to reconnect to the database and repeat your command.
May 12 00:42:53 srv3 postgres[8713]: [82-1] WARNING:  terminating =

connection because of crash of another server process
May 12 00:42:53 srv3 slon[8698]: [56-1] 2007-05-12 00:42:53 CDT INFO   =

remoteListenThread_1: disconnecting from 'dbname=3Daltos_research port=3D54=
33
May 12 00:42:53 srv3 postgres[8712]: [82-1] WARNING:  terminating =

connection because of crash of another server process
May 12 00:42:53 srv3 postgres[8713]: [82-2] DETAIL:  The postmaster has =

commanded this server process to roll back the current transaction and
exit, because another server
May 12 00:42:53 srv3 postgres[8713]: [82-3]  process exited abnormally =

and possibly corrupted shared memory.
May 12 00:42:53 srv3 postgres[8710]: [82-1] WARNING:  terminating =

connection because of crash of another server process
May 12 00:42:53 srv3 postgres[8712]: [82-2] DETAIL:  The postmaster has =

commanded this server process to roll back the current transaction and
exit, because another server
May 12 00:42:53 srv3 postgres[8713]: [82-4] HINT:  In a moment you =

should be able to reconnect to the database and repeat your command.
May 12 00:42:53 srv3 slon[8698]: [56-2]  host=3Dsrv1.altosresearch.com =

user=3Dpostgres'
May 12 00:42:53 srv3 postgres[8710]: [82-2] DETAIL:  The postmaster has =

commanded this server process to roll back the current transaction and
exit, because another server
May 12 00:42:53 srv3 postgres[8712]: [82-3]  process exited abnormally =

and possibly corrupted shared memory.
May 12 00:42:53 srv3 postgres[8710]: [82-3]  process exited abnormally =

and possibly corrupted shared memory.
May 12 00:42:53 srv3 postgres[8712]: [82-4] HINT:  In a moment you =

should be able to reconnect to the database and repeat your command.
May 12 00:42:53 srv3 postgres[8710]: [82-4] HINT:  In a moment you =

should be able to reconnect to the database and repeat your command.
May 12 00:42:53 srv3 postgres[7320]: [84-1] LOG:  all server processes =

terminated; reinitializing
May 12 00:42:53 srv3 postgres[8715]: [85-1] LOG:  database system was =

interrupted at 2007-05-12 00:42:41 CDT


Andrew Sullivan wrote:
> It may not be an error on Slony's part.  Slony seems to think the
> back end crashed.  What do your postgres logs say?
>   =

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070512/=
413dd044/attachment-0001.htm