← Back to team overview

launchpad-dev team mailing list archive

Re: Issues with the puller script

 

Tim Penhey wrote:
> Hi Michael, 
> 
> We've had a few issues with the branch puller today.  It seems to get itself 
> wedged, where it has no workers, but the main script doesn't die.

This has happened at least a few times today.

> We restarted today and it worked but we don't know why it stopped working.

I still don't really have a clue.  The logging in the branch you landed
and one of mine below should give us a better idea what's going on.

> jml added to the logging, but couldn't get it working on his karmic laptop so 
> I committed it:
> 	lp:~thumper/launchpad/fix-puller-logging
> 
> And I'm running it through ec2 now with -s.

It landed fine.

> Here are some others for you to look at :-)
> 
> https://bugs.edge.launchpad.net/launchpad-code/+bug/438287

https://code.edge.launchpad.net/~mwhudson/launchpad/requestMirror-shouldnt-demote-branch/+merge/12561

> https://bugs.edge.launchpad.net/launchpad-code/+bug/438290

https://code.edge.launchpad.net/~mwhudson/launchpad/puller-more-useful-xmlrpc-logs/+merge/12562

> https://bugs.edge.launchpad.net/launchpad-code/+bug/438292

https://code.edge.launchpad.net/~mwhudson/launchpad/puller-doesnt-call-startMirroring/+merge/12563

The above 3 branches are being ec2 tested.  Please review and, if you
approve, land them.

> https://bugs.edge.launchpad.net/launchpad-code/+bug/438298

I think it would be a bit dishonest to change how the script records its
entries in the ScriptActivity table, so we should monitor the puller's
health in a different way.  I suggest one in the report

Cheers,
mwh



Follow ups

References