librarian 500s during read-only mode

Bug #702188 reported by Michael Hudson-Doyle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Critical
Unassigned

Bug Description

During the 11.01 rollout, the librarian as accessed from appservers failed, e.g. OOPS-1838H5865

Restarting the librarians made it work again, so it's likely something to do with the librarians not being happy when the database config changes or something.

three sets of errors on the librarian:
first
OOPS-1838LIBRARIANA100, OOPS-1838LIBRARIANA1000, OOPS-1838LIBRARIANA1001, OOPS-1838LIBRARIANA1002, OOPS-1838LIBRARIANA1003
second
OOPS-1838LIBRARIANA1, OOPS-1838LIBRARIANA10, OOPS-1838LIBRARIANA11, OOPS-1838LIBRARIANA13, OOPS-1838LIBRARIANA2
third
OOPS-1838LIBRARIANA897, OOPS-1838LIBRARIANA902

Tags: librarian oops
description: updated
Changed in launchpad:
status: New → Triaged
importance: Undecided → Critical
tags: added: librarian oops
Revision history for this message
Robert Collins (lifeless) wrote :

We should have librarian OOPSes reflecting this.

description: updated
Revision history for this message
Steve Kowalik (stevenk) wrote :

We no longer make use of read-only mode.

Changed in launchpad:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.