Thu Jun 24 12:53:39 PDT 2004
- Previous message: [Slony1-general] Another slon daemon is serving this node already
- Next message: [Slony1-general] Another slon daemon is serving this node already
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thomas Draband (madcow) schrieb:
> After an immediate stop of postgresql (simulation of system crash) in
> pg_catalog.pg_listener a tupel with relname='_${cluster_name}_Restart'
> exists. slon doesn't start cause it thinks another process is serving
> the cluster on this node.
> What can I do? The tupels can't be droped from this relation.
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general
I've found an anwser my self.
Befor I start slon, I do a 'restart node'. PostgreSQL tries to nothify
the listeners and drop those are not anwsering. Slon then starts cleanly.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: madcow.vcf
Type: text/x-vcard
Size: 150 bytes
Desc: not available
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20040624/7a103f53/madcow.vcf
- Previous message: [Slony1-general] Another slon daemon is serving this node already
- Next message: [Slony1-general] Another slon daemon is serving this node already
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list