Problem with automatic mirror of Git repository GPars

Asked by Russel Winder

The automated mirror of the GPars Git repository stopped working sometime during 2010-10-09. The log now reports:

2010-10-13 01:20:13 INFO Starting job.
2010-10-13 01:20:13 INFO Getting exising bzr branch from central store.
2010-10-13 01:20:13 INFO 35 bytes transferred
Exception AttributeError: "'NoneType' object has no attribute 'close'" in <function terminate at 0x3a0b758> ignored
Traceback (most recent call last):
  File "/srv/", line 82, in <module>
  File "/srv/", line 77, in main
  File "/srv/", line 452, in run
    return self._doImport()
  File "/srv/", line 586, in _doImport
    foreign_branch_tip = foreign_branch.last_revision()
  File "/srv/", line 353, in last_revision
    return self.lookup_foreign_revision_id(self.head)
  File "/srv/", line 367, in head
    heads = self.repository.get_refs()
  File "/srv/", line 287, in get_refs
    lambda x: None, lambda x: trace.mutter("git: %s" % x))
  File "/srv/", line 132, in fetch_pack
    raise BzrError(e)
bzrlib.errors.BzrError: [Errno 104] Connection reset by peer
Exception AttributeError: "'NoneType' object has no attribute 'close'" in <function terminate at 0x3a0bd70> ignored
Import failed:
Traceback (most recent call last):
Failure: twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 1.

I'm afraid I have no idea how to progress this so as to have a working mirror, any help greatly appreciated.


Question information

English Edit question
Launchpad itself Edit question
No assignee Edit question
Solved by:
Russel Winder
Last query:
Last reply:
Revision history for this message
Tim Penhey (thumper) said :

Hi Russel,

I'm able to reproduce the failure locally using both git and bzr-git, is not responding.


Revision history for this message
Russel Winder (russel) said :

Hummm... it seems like a really good job there is a watchdog timer involved.

There is clearly a problem at Codehaus, and I have initiated a dialogue with the person who should be able to get things moving. I guess the Launchpad mirroring will suspend again if the p[roblem isn't fixed fairly quickly, which seems fine. I guess a new question here is the right way to get things restarted once the Codehaus problem is resolved?

In the interim, I guess the issue for Launchpad is that the report in the Launchpad log, whilst comprehensive and undoubtedly correct, isn't really that helpful to users as it is a stack trace of the Python code internal to teh Launchpad/Bazaar subsystem. Is there perhaps a way of inferring a more user-oriented message that could be used -- keeping the current message as additional information?

Revision history for this message
Russel Winder (russel) said :

So the problem that caused the failure was a problem at Codehaus with their Git server. This has now been fixed and the mirror activity here at Launchpad seems to be working just fine. Apologies for incorrectly accusing Launchpad of not working -- the error message could still do with some tidying up :-)