This configuration is running latest 1.2.11 slon on 8.2.4. After running =

a pg_bulkload command and starting slony back up, something that slony =

tried to do triggered the postmaster to restart suddenly. The listener =

for node 2 of a 3-node cluster starting up following the use of =

pg_bulkload to import 600k records:

Sep 14 09:26:40 srv2 postgres-8.2[13372]: [3-2] STATEMENT:  SELECT =

pg_bulkload($1)
Sep 14 09:26:57 srv2 sshd(pam_unix)[13389]: session opened for user =

jason by (uid=3D0)
Sep 14 09:27:07 srv2 sshd(pam_unix)[13389]: session closed for user jason
Sep 14 09:27:18 srv2 postgres-8.2[13490]: [2-1] NOTICE:  BULK LOAD START
Sep 14 09:40:37 srv2 postgres-8.2[13490]: [3-1] NOTICE:  BULK LOAD END  =

(632832 records)
Sep 14 09:40:37 srv2 postgres-8.2[13490]: [4-1] LOG:  duration: =

799245.160 ms  execute <unnamed>: SELECT pg_bulkload($1)
Sep 14 09:40:37 srv2 postgres-8.2[13490]: [4-2] DETAIL:  parameters: $1 =

=3D '/pgdata/8.2/sample_csv.ctl'

then:

Sep 14 10:48:18 srv2 slon[13841]: [27-1] 2007-09-14 10:48:18 CDT CONFIG =

main: configuration complete - starting threads
Sep 14 10:48:18 srv2 postgres-8.2[13852]: [2-1] NOTICE:  Slony-I: =

cleanup stale sl_nodelock entry for pid=3D23070
Sep 14 10:48:18 srv2 postgres-8.2[13852]: [3-1] NOTICE:  Slony-I: =

cleanup stale sl_nodelock entry for pid=3D1288
Sep 14 10:48:18 srv2 postgres-8.2[13852]: [4-1] NOTICE:  Slony-I: =

cleanup stale sl_nodelock entry for pid=3D1292
Sep 14 10:48:18 srv2 slon[13841]: [29-1] 2007-09-14 10:48:18 CDT CONFIG =

enableNode: no_id=3D1
Sep 14 10:48:18 srv2 slon[13841]: [30-1] 2007-09-14 10:48:18 CDT CONFIG =

enableNode: no_id=3D3

followed by:

Sep 14 10:59:26 srv2 slon[13841]: [45-1] 2007-09-14 10:59:26 CDT WARN   =

cleanupThread: "select "_ar_primary".logswitch_weekly(); " - server =

closed the connection
Sep 14 10:59:26 srv2 slon[13841]: [45-2]  unexpectedly
Sep 14 10:59:26 srv2 slon[13841]: [45-3]        This probably means the =

server terminated abnormally
Sep 14 10:59:26 srv2 slon[13841]: [45-4]        before or while =

processing the request.
Sep 14 10:59:26 srv2 slon[13841]: [46-1] 2007-09-14 10:59:26 CDT FATAL  =

cleanupThread: "delete from "_ar_primary".sl_log_1 where log_origin =3D =

'2' and log_xid <
Sep 14 10:59:26 srv2 slon[13841]: [46-2]  '151706861'; delete from =

"_ar_primary".sl_log_2 where log_origin =3D '2' and log_xid < '151706861'; =

delete from
Sep 14 10:59:26 srv2 slon[13841]: [46-3]  "_ar_primary".sl_seqlog where =

seql_origin =3D '2' and seql_ev_seqno < '1686420'; select =

"_ar_primary".logswitch_finish(); " -
Sep 14 10:59:26 srv2 postgres-8.2[25487]: [2-1] LOG:  server process =

(PID 13861) was terminated by signal 11
Sep 14 10:59:26 srv2 postgres-8.2[25487]: [3-1] LOG:  terminating any =

other active server processes
Sep 14 10:59:26 srv2 postgres-8.2[14136]: [5-1] WARNING:  terminating =

connection because of crash of another server process

The postmaster is now running again, but I am afraid to restart slony =

again. Anything I can do to verify the integrity of the slon =

configuration that will not crash the postmaster?

Thanks,
jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070914/=
8aa2face/attachment.htm