Fri Mar 10 06:41:54 PST 2006
- Previous message: [Slony1-general] problem with "no worker thread"
- Next message: [Slony1-general] 5. Re: What is left for 1.2??? (Christopher Browne)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Folks, I'm having a problem getting a test replication going between two machines running PostgreSQL 8.1.3 and Slony 1.1.5. What's happening is that slon on both boxes is bombing out within seconds of startup when the localListenThread aborts with FATAL error that complains about an event having an Unknown event type. Inspection of the sl_event table shows events that have ev_type set to NULL, whose origin is the master. It appears to be slon itself that is creating these. If I zap them and restart slon, it will bomb out again leaving another one of these events in the table. It's quite possible that I've messed something up during my setup, but even when I blow away the databases on both boxes and recreate from pristine copies (full on master, schema-only on slave), the problem re-occurs. Anybody have any idea what's causing the problem? Thanks, Regards, Tony. -- Tony Byrne
- Previous message: [Slony1-general] problem with "no worker thread"
- Next message: [Slony1-general] 5. Re: What is left for 1.2??? (Christopher Browne)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list