On 06/12/13 07:14, Sridevi R wrote:
> Hello,
> 
> The slony logs are consistently posting this error:
> 
> 2013-06-12 10:01:05 GMT FATAL  cleanupThread: "begin;lock table
> "_xx_cluster".sl_config_lock;select "_xx_cluster".cleanupEvent('10
> minutes'::interval);commit;" - server closed the connection unexpectedly
> 2013-06-12 10:12:24 GMT FATAL  cleanupThread: "begin;lock table
> "_xx_cluster".sl_config_lock;select "_xx_cluster".cleanupEvent('10
> minutes'::interval);commit;" - server closed the connection unexpectedly
> 
> checked and found that sl_confirm table is not cleaned up. cleanup event
> never succeeds.
> Additionally, the child processes terminates and restarts after each
> such cleanup failure.
> 
> 2013-06-11 11:20:04 GMT CONFIG slon: child terminated signal: 9; pid:
> 20172, current worker pid: 20172
> 2013-06-11 11:20:04 GMT CONFIG slon: restart of worker in 10 seconds
> 
> When cleanup is run manually, on the psql prompt it runs to completion
> without any issues and cleans up sl_event and sl_confirm tables
> "begin;lock table "_xx_cluster".sl_config_lock;select
> "_xx_cluster".cleanupEvent('10 minutes'::interval);commit;"
> 
> Soln version: 2.1.2
> 
> Any help/insight would be greatly appreciated.

Slon kills its worker(s) with signal 9 (SIGKILL) when it needs to
restart, like when there are errors in event processing or if it
receives certain signals. Are there any other errors in the slon log or
is something on the machine sending signals to slon?


Jan

> 
> Thanks,
> Sridevi
> 
> 
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
> 


-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin