Hello,

I have problem with sporadic slony crashing on our Linux box
(kernel 2.4.28, glibc-2.2.5.so, 2.95.3, postgresql 8.01+ssl, slony 1.05)
Yes, this is rather old box, but it's in production and we couldn't upgrade
glibc (if it's the problem). I didn't setup slony, so I have no information
besides slony log file.

CONFIG enableNode: no_id=2
ERROR  remoteWorkerThread_2: "notify "_astronet_Event"; notify "_astronet_Confirm"; insert into "_astronet".sl_event     (ev_origin, ev_seqno, ev_timestamp,      ev_minxid, ev_maxxid, ev_xip, ev_type     ) values ('2', '15145', '2005-03-25 20:52:48.172386', '663650', '663651', '', 'SYNC'); insert into "_astronet".sl_confirm   (con_origin, con_received, con_seqno, con_timestamp)    values (2, 1, '15145', CURRENT_TIMESTAMP); commit transaction;" PGRES_FATAL_ERROR server closed the connection unexpectedly
         This probably means the server terminated abnormally
         before or while processing the request.


slon didn't restart and I don't want to start it manually because I don't
know if slony setup is in working condition. 
So, I'm asking if it's safe just restart slony and forget or if there are
problems with our setup.


 	Regards,
 		Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg at sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83