<div dir="ltr"><div><div><div>Jan,<br><br></div>Thanks for the reply. <br><br>The only errors in the slon log are failure of cleanupThread. <br>child process is restarting right after the cleanupThread Failure.<br></div><div>
This occurs approximately every 10 minutes since cleanup_interval is set to 10 minutes.<br></div><div><br>Here is a sample from the log again:<br><br>2013-06-06 14:23:27 GMT FATAL cleanupThread: "begin;lock table "_xx_cluster".sl_config_lock;select "_xx_cluster".cleanupEvent('10 minutes'::interval);commit;" - server closed the connection unexpectedly<br>
This probably means the server terminated abnormally<br> before or while processing the request.<br>2013-06-06 14:23:27 GMT CONFIG slon: child terminated signal: 9; pid: 16135, current worker pid: 16135<br>2013-06-06 14:23:27 GMT CONFIG slon: restart of worker in 10 seconds<br>
<br></div>Thanks ,<br></div>Sridevi<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 12, 2013 at 7:33 PM, Jan Wieck <span dir="ltr"><<a href="mailto:JanWieck@yahoo.com" target="_blank">JanWieck@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 06/12/13 07:14, Sridevi R wrote:<br>
> Hello,<br>
><br>
> The slony logs are consistently posting this error:<br>
><br>
> 2013-06-12 10:01:05 GMT FATAL cleanupThread: "begin;lock table<br>
> "_xx_cluster".sl_config_lock;select "_xx_cluster".cleanupEvent('10<br>
> minutes'::interval);commit;" - server closed the connection unexpectedly<br>
> 2013-06-12 10:12:24 GMT FATAL cleanupThread: "begin;lock table<br>
> "_xx_cluster".sl_config_lock;select "_xx_cluster".cleanupEvent('10<br>
> minutes'::interval);commit;" - server closed the connection unexpectedly<br>
><br>
> checked and found that sl_confirm table is not cleaned up. cleanup event<br>
> never succeeds.<br>
> Additionally, the child processes terminates and restarts after each<br>
> such cleanup failure.<br>
><br>
> 2013-06-11 11:20:04 GMT CONFIG slon: child terminated signal: 9; pid:<br>
> 20172, current worker pid: 20172<br>
> 2013-06-11 11:20:04 GMT CONFIG slon: restart of worker in 10 seconds<br>
><br>
> When cleanup is run manually, on the psql prompt it runs to completion<br>
> without any issues and cleans up sl_event and sl_confirm tables<br>
> "begin;lock table "_xx_cluster".sl_config_lock;select<br>
> "_xx_cluster".cleanupEvent('10 minutes'::interval);commit;"<br>
><br>
> Soln version: 2.1.2<br>
><br>
> Any help/insight would be greatly appreciated.<br>
<br>
</div></div>Slon kills its worker(s) with signal 9 (SIGKILL) when it needs to<br>
restart, like when there are errors in event processing or if it<br>
receives certain signals. Are there any other errors in the slon log or<br>
is something on the machine sending signals to slon?<br>
<br>
<br>
Jan<br>
<br>
><br>
> Thanks,<br>
> Sridevi<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Slony1-general mailing list<br>
> <a href="mailto:Slony1-general@lists.slony.info">Slony1-general@lists.slony.info</a><br>
> <a href="http://lists.slony.info/mailman/listinfo/slony1-general" target="_blank">http://lists.slony.info/mailman/listinfo/slony1-general</a><br>
><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
Anyone who trades liberty for security deserves neither<br>
liberty nor security. -- Benjamin Franklin<br>
</font></span></blockquote></div><br></div>