Fri Jun 1 06:27:54 PDT 2007
- Previous message: [Slony1-general] if the slon daemon stop at all (on master and slaves) SL_NODELOCK must be empty ???
- Next message: [Slony1-general] Error Condition Found with DDL/EXECUTE SCRIPT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sorry for your spending time, we find trouble. the _multimedia.sl_local_node_id (on the ) have a start value 2 (!!!!!!!!!!!!!!) but this Node 6, on other node all OK and sl_local_node_id = node identificator why nobody of us don't know... all nodes was prepared with slonik_store_node..... good weekend all Andrew Hammond wrote: > On 5/31/07, *Jan Wieck* <JanWieck at yahoo.com > <mailto:JanWieck at yahoo.com>> wrote: > > On 5/31/2007 9:44 AM, open wrote: > >> Check the output of the sl_status view over a couple of minutes. If > >> the column st_last_event for any of your subscribers is not > advancing, > >> the event confirmations from that node still don't make it back > to the > >> origin and your engineer has more to fix. > > .....bad news, sl_status looks nornally.... > > st_last_event increases normally.... > > have you any ideas ? > > Ooops ... my fault ... I meant the column st_received. As it looks to > me, node 6 is either not replicating, or the confirmations don't > make it > back to the origin. The origin thinks it is stuck on event 69838. > > > I wonder if that has anything to do with the following. > > "I'm manually deleting 5-6 rows from sl_event on slave and data > replication OK," > > Did you delete these rows on node 6 and not on any other node? > Did you keep a copy of the rows you deleted, or at least note their > event number? > > Andrew
- Previous message: [Slony1-general] if the slon daemon stop at all (on master and slaves) SL_NODELOCK must be empty ???
- Next message: [Slony1-general] Error Condition Found with DDL/EXECUTE SCRIPT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list