"LINHART Felix" <Felix.LINHART at frequentis.com> writes:
> I have just noticed that my postgres logfile receives continuously messages from slony listed below::p>
>
> :p> 
>
> 2008-07-16 12:37:50 CEST NOTICE:  Slony-I: cleanup stale sl_nodelock entry for pid=5810:p>
>
> 2008-07-16 12:37:50 CEST CONTEXT:  SQL statement "SELECT  "_slony1".cleanupNodelock()":p>
>
>         PL/pgSQL function "cleanupevent" line 77 at PERFORM:p>
>
> 2008-07-16 12:51:35 CEST LOG:  could not receive data from client: Connection timed out:p>
>
> 2008-07-16 12:51:35 CEST LOG:  unexpected EOF on client connection:p>

Since these are "NOTICE" log records, it does not indicate any error
as far as Slony-I is concerned.

When the slon falls over, and another starts up, the new one has to
clean up after the old one.  It's not a real big deal, though it
suggests that you have some sort of network problem or something that
is causing slon processes to fall over so they need to be restarted.

That falls outside what Slony-I is, itself, doing.
-- 
select 'cbbrowne' || '@' || 'linuxfinances.info';
http://cbbrowne.com/info/lsf.html
Rules  of the  Evil Overlord  #145. "My  dungeon cell  decor  will not
feature exposed pipes.  While they add to the  gloomy atmosphere, they
are good  conductors of vibrations and  a lot of  prisoners know Morse
code." <http://www.eviloverlord.com/>