|
Home > Archive > Slony1 PostgreSQL Replication > July 2005 > slon exits on RESET_CONFIG event
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]
| Author |
slon exits on RESET_CONFIG event
|
|
| Radim Kolar 2005-07-18, 11:24 am |
| after backup and restore slony1 stops working. i have used repair config command, but this command shutdowns slon every time. How can get replication
running?
2005-07-18 17:19:26 CEST DEBUG2 remoteListenThread_2
: queue event 2,481 RESET_CO
NFIG
2005-07-18 17:19:26 CEST DEBUG2 remoteWorkerThread_2
: Received event 2,481 RESET
_CONFIG
2005-07-18 17:19:27 CEST DEBUG1 slon: done
2005-07-18 17:19:27 CEST DEBUG2 slon: exit(0)
| |
| cbbrowne-swQf4SbcV9C7WVzo/KQ3Mw@public.gmane.org 2005-07-18, 1:24 pm |
| > after backup and restore slony1 stops working. i have used repair conf=
ig
> command, but this command shutdowns slon every time. How can get
> replication
> running?
>
> 2005-07-18 17:19:26 CEST DEBUG2 remoteListenThread_2
: queue event 2,481
> RESET_CO
> NFIG
> 2005-07-18 17:19:26 CEST DEBUG2 remoteWorkerThread_2
: Received event 2,=
481
> RESET
> _CONFIG
> 2005-07-18 17:19:27 CEST DEBUG1 slon: done
> 2005-07-18 17:19:27 CEST DEBUG2 slon: exit(0)
This sort of thing is "typical" when there's something missing in the
parameters being submitted to one of the database connections.
slon *tries* to generate the query to submit; something's left null, and
the slon thread crashes. Unfortunately, since it's a thread, you don't
get a full report of what busted :-(.
I think you'll need to directly trouble Darcy Buskermolen; he's the one
that added this feature.
| |
| Darcy Buskermolen 2005-07-18, 1:24 pm |
| On Monday 18 July 2005 11:13, cbbrowne-swQf4SbcV9C7WVzo/KQ3Mw@public.gmane.org wrote:
>
> This sort of thing is "typical" when there's something missing in the
> parameters being submitted to one of the database connections.
>
> slon *tries* to generate the query to submit; something's left null, and
> the slon thread crashes. Unfortunately, since it's a thread, you don't
> get a full report of what busted :-(.
>
> I think you'll need to directly trouble Darcy Buskermolen; he's the one
> that added this feature.
I'll look into this in more depth later on this afternoon.
>
> ____________________
____________________
_______
> Slony1-general mailing list
> Slony1-general- AuKwsB3Fm+ugFIWk8tvy
RWD2FQJk+8+b@public.gmane.org
> http://gborg.postgresql.org/mailman.../slony1-general
--
Darcy Buskermolen
Wavefire Technologies Corp.
http://www.wavefire.com
ph: 250.717.0200
fx: 250.763.1759
| |
| Radim Kolar 2005-07-18, 8:24 pm |
| > I'll look into this in more depth later on this afternoon.
thank you. do you need more informations?
| |
| Darcy Buskermolen 2005-07-20, 8:25 pm |
| On Monday 18 July 2005 13:37, Radim Kolar wrote:
>
> thank you. do you need more informations?
How exactly were you running this command ?
> ____________________
____________________
_______
> Slony1-general mailing list
> Slony1-general- AuKwsB3Fm+ugFIWk8tvy
RWD2FQJk+8+b@public.gmane.org
> http://gborg.postgresql.org/mailman.../slony1-general
--
Darcy Buskermolen
Wavefire Technologies Corp.
http://www.wavefire.com
ph: 250.717.0200
fx: 250.763.1759
|
|
|
|
|