|
Home > Archive > Slony1 PostgreSQL Replication > February 2006 > dying slons
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| I'm seeing slons die with done; and exit(0) a minute or two after they
start up. While they are up they seem to work correctly but they exit
pretty quickly.
Why would they exit(0)??
In the pg log file in the next second, I'm seeing "Unexpected EOF on client connection".
I think this is a result of the slons stopping rather than a cause
because of the timing. But the timing is close.
This is 7.4.x with slony 1.1.0. Slons are running on a separate machine.
Any ideas how to keep the slons alive longer or why they die so often?
--elein
elein- JkRegAVoul5BDgjK7y7T
UQ@public.gmane.org
--------------------------------------------------------------
elein- JkRegAVoul5BDgjK7y7T
UQ@public.gmane.org Varlena, LLC www.varlena.com
(510)655-2584(o) (510)543-6079(c)
PostgreSQL Consulting, Support & Training
PostgreSQL General Bits http://www.varlena.com/GeneralBits/
--------------------------------------------------------------
AIM: varlenallc Yahoo: AElein Skype: varlenallc
--------------------------------------------------------------
I have always depended on the [QA] of strangers.
| |
| Florian G. Pflug 2006-02-15, 9:25 am |
| elein wrote:
> I'm seeing slons die with done; and exit(0) a minute or two after they
> start up. While they are up they seem to work correctly but they exit
> pretty quickly.
I've seen that too, and I believe it was due to incorrect sl_listen entries.
It went away after I managed to get correct sl_listen entries - but I'm not
_entirely_ sure that this was what fixed it. Would be an odd coincidence if
not, tough.
See the discussion about the 1.1.5 release for details.
greetings, Florian Pflug
|
|
|
|
|