Alexander Kolodziej wrote:
> Hello!
> ...
> 2010-05-25 11:16:00 UTC DEBUG2 remoteListenThread_1: queue event 1,2533 SYNC
> 2010-05-25 11:16:00 UTC DEBUG2 slon: child terminated status: 11; pid:
> 29027, current worker pid: 29027
> 2010-05-25 11:16:00 UTC DEBUG1 slon: restart of worker in 10 seconds
> --------------------------
> 
> In syslog i see this on the slave (slon segfault errors every 10s):
> --------------------------
> May 25 11:16:30 semc-sh62 kernel: [20053518.436336] slon[29076]:
> segfault at 273936 ip 00007fd69e8bac40 sp 00007fd69ad48698 error 4 in
> libc-2.9.so[7fd69e83a000+168000]
> May 25 11:16:40 semc-sh62 kernel: [20053528.548794] slon[29104]:
> segfault at 273936 ip 00007f359f4f4c40 sp 00007f359b982698 error 4 in
> libc-2.9.so[7f359f474000+168000]
> --------------------------
>

Can you rub gdb against a core file, or start slony up inside of gdb, so 
we can get a stack trace of what slon was doing went it died?

(from a build with debugging symbols would be even more useful)


> What could cause this?
> Looking at the size of /var/lib/postgresql/8.3/ i can see that it has
> almost succeeded in replicating the DB, but something is going boink.
> 
> Slon loglevel is set to 4.
> Are there any slon sl_* tables i can look in for info?
> Tried google but only get 8 results on: "child terminated status: 11" +
> "restart of worker", and none of those provide a solution.
> 
>   wbr / Alexander
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general


-- 
Steve Singer
Afilias Canada
Data Services Developer
416-673-1142