launchpad-dev team mailing list archive

["Francis J. Lacoste" <francis.lacoste@xxxxxxxxxxxxx>]

After a Slony-1 restart and another attempt. It failed again but at a 
different place this time around:

https://pastebin.canonical.com/38407/

The warnings in Slony Node 5 log file are:
lpslon_node5_node_staging.log:2010-10-08 19:31:49 UTCWARN   
remoteWorkerThread_4: transactions earlier than XID 16168895 are still in 
progress
lpslon_node5_node_staging.log:2010-10-08 19:31:49 UTCWARN   
remoteWorkerThread_4: data copy for set 666 failed 174 times - sleep 60 
seconds

The transactions earlier than XID 16168895 first appeared at 16:40:01 and 
continued until that time.

The warning just before is:

lpslon_node5_node_staging.log:2010-10-08 16:40:01 UTCWARN   
remoteWorker_wakeup:
 node 4 - no worker thread

What this means, and how to recover from this... I have no idea.

In the monkey-pushes-button-until-it-works fashion, I've asked Chex to restart 
Pg/Slony and re-attempt the restore...

-- 
Francis J. Lacoste
francis.lacoste@xxxxxxxxxxxxx

On October 8, 2010, Francis J. Lacoste wrote:
> Hi,
> 
> On October 8, 2010, Curtis Hovey wrote:
> > DDL submission to initial node - PGRES_TUPLES_OK
> > 2010-10-07 23:26:05 INFO    New stuff needs replicating:
> > public.persontransferjob, public.persontransferjob_id_seq, public.quest
> > ionjob, public.questionjob_id_seq
> 
> That's output by the upgrade.py script when it notices new tables that
> aren't part of the replication set. Its next action is to add it to the
> replication set. If there is no output after that, that's probably where
> it hungs. As to why, this will require some Slony-I psychoanalysis, and I
> don't have my degree in that field.
> 
> I suggest we restart Slony-I on staging and try again. If it still hangs,
> let's revert the DB patch that adds those.
> 
> Cheers

Attachment: signature.asc
Description: This is a digitally signed message part.