loggerhead instance inoperative for >1 month

Bug #1859711 reported by Peter J. Mello on 2020-01-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I noticed was reporting a 503 code shortly before the holidays and thought it best to hold off filing a bug until the New Year if it was still inoperative. I'm aware that it's a duplicate resource while the codebase remains current and accessible on Launchpad, but it also makes the project appear even more moribund than it might otherwise, so it's probably worth investigating at some point.

A tangential question to this issue: Is there an official Git mirror available for Breezy that still updates? The GitHub mirror appears several months out of date and I'm not aware of any others. Ironically, it's such a venerable repo that working with it in Bazaar format is intolerably slow.

Peter J. Mello (roguescholar) wrote :

Strike the question about the git mirror; somehow I bookmarked a stale branch of the breezy-team/breezy repo and not master. I'm all squared away on that front now.

Jelmer Vernooij (jelmer) wrote :

I've restarted loggerhead and added some monitoring.

Changed in brz:
status: New → Fix Released
Jelmer Vernooij (jelmer) wrote :

Thanks for the report!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers